Hello all,
This is to inform you about the revised end time for the joint meeting between ccNSO and ALAC, including a revision of the agenda.
Joint meeting: ALAC & ccNSO
Sunday, 10 March | 17:00 – 17:30 (revised end time) | Topaz
Participate remotely:
https://participate.icann.org/kix64-topaz
Agenda:
Read more about the ICANN64 agenda of the joint sessions between the ccNSO and the ICANN Board, and other SO/ACs here:
https://community.icann.org/download/attachments/100533721/agenda_jointmeetings_04032019.pdf?version=1&modificationDate=1551689317513&api=v2
Best regards.
Joke Braeken
ccNSO Policy Advisor
Follow @ccNSO on Twitter: https://twitter.com/ccNSO
Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/
From: cctldcommunity <cctldcommunity-bounces@lists.nic.cz> on behalf of Joke Braeken <joke.braeken@icann.org>
Date: Friday, 1 March 2019 at 15:35
To: "ccnso-members@icann.org" <ccnso-members@icann.org>, "ccTLDcommunity@cctld-managers.org" <ccTLDcommunity@cctld-managers.org>, ccnso-council <ccnso-council@icann.org>
Subject: [Ext] [cctldcommunity] Consult the agenda of the joint meetings between the ccNSO and ALAC, the GNSO Council, the ICANN Board and GAC.
Hello all,
In order to allow you to prepare for the upcoming ICANN64 Community Forum in Kobe, please find included below and in attachment an overview of the agendas for the joint sessions with other ICANN
Supporting Organisations (SO) and Advisory Committees (ACs), as well as the agenda for the joint meeting between the ccNSO and the ICANN Board.
This document has been published here as well:
https://community.icann.org/pages/viewpage.action?pageId=100533721
Joint meeting: ALAC & ccNSO
Sunday, 10 March | 17:00 – 18:00 | Topaz
Participate remotely:
https://participate.icann.org/kix64-topaz
Agenda:
1.
Introduction to ALAC and ALAC priorities for FY20 - Maureen Hilyard, ALAC Chair
2.
Introduction to ccNSO - Katrina Sataki, ccNSO Chair
3.
ccNSO Comments on the ICANN Plans and Budgets: Giovanni Seppia, ccNSO SOPC chair
4.
Summary: Commonalities and differences - Katrina Sataki, Maureen Hilyard
5.
Introduction newly appointed ccNSO liaison to ALAC
Joint meeting: ccNSO & GNSO Councils
Monday, 11 March | 12:15 – 13:15 | Ohwada C
Participate remotely:
https://participate.icann.org/kix64-ohwadac
Agenda:
1. Joint (prospective) projects
a. CSC Effectiveness review: final report. Synchronizing decision-making and next steps
b. Harmonizing Confusing Similarity review
c. CCWG Auction proceeds, next steps
2. Hot Topics and Updates
a. Comments ICANN’s 2021-2025 Strat Plan, FY 20 Operating Plan and Budget: common concerns?
b. Selecting IFRT membership: How to move IANA Function Review forward?
c. Progress Emoji Study Group: preliminary results
d. Status EPDP
Joint meeting: ccNSO & ICANN Board
Tuesday, 12 March | 11:00-12:00 | Ohwada A
Participate remotely:
https://participate.icann.org/kix64-ohwadaa
Questions from the Board to the ccNSO
This time in particular, the Board would like to listen to your suggestions in order to make ICANN’s big plans successful. What does it mean?
In 2018, besides GDPR, the Community, the Board and ICANN org have worked tirelessly on several key plans that are now or soon will be out for public comment:
- the draft Strategic Plan 2021-2025 was published a little before Christmas;
- the first consultation paper on a 2-Year budgeting process was also published before Christmas;
- and the draft FY21-25 Operating Plan & Financial Projections will be posted before this summer.
In addition, based on community feedback and discussions at ICANN 63, we will begin a consultation in Kobe on the status of ICANN’s governance model, including whether and how it should evolve to continue to serve the global ICANN community.
In the aggregate, these plans are comprehensive and address the key challenges ICANN’s faces in the future in the areas of security; governance; unique identifier systems; geopolitics; and financials.
Even great plans come with challenges, which we want to anticipate and address as a prelude to implementation. We pulled together once before, galvanized our resources effectively and achieved a successful transition. We need to do it again to address ICANN’s
future challenges. Are we ready? Do we, for example, collectively have the leadership, skills, resources, knowledge and commitment required to implement these plans successfully over the next five years? We need your help for this.
Specifically, as you prepare for Kobe, we would like your high-level input on:
1. What the Board, ICANN org, and the Community should be doing now to prepare for the successful implementation of these plans? Please make three suggestions as concrete as possible, providing one each for the Board, ICANN org, and the Community.
2. While the success of these plans lies primarily within ICANN, we all know that ICANN does not operate in a vacuum, and alliances and partnerships are important to our success. How can we increase the likelihood
that important allies and partners in the space are on the same page and working together to achieve common/agreed upon goals? Please provide one suggestion of something that could be done externally to improve trust and collaboration.
3. We are looking forward to hearing your four suggestions during our face-to-face meetings in Kobe so that we could then work jointly towards a successful implementation of ICANN’s future plans, that you have been involved in formulating.
Questions from the ccNSO to the Board
1. ICANN’s mission
As the Board adopts ICANN’s Strategic Plan, Operating Plans and related budgets, what criteria does the Board use to determine whether an activity is within ICANN’s mission?
With ICANN’s funding levelling or on the decline, do you consider all the activities as equally important or do you see some activities as of a higher priority for fulfilling ICANN’s mission?
2. Confusing similarity
The joint ccNSO -SSAC working party has provided feedback and input to ICANN Org’s proposed guideline to operationalize the amended Fast Track process (inclusion of Risk Mitigation to overcome the only pending case of confusing similarity).
In addition and overstepping the original request, the working party suggests that ICANN takes a final decision on the one and only pending case. Once the current pending case under the IDN ccTLD Fast Track Process is resolved, we propose that all processes
and procedures relating to the evaluation of confusing similarity be reviewed and evaluated, with a two-fold goal. Firstly, originally (in 2009) the process and procedures for evaluation of strings of the new gTLD round and the overall policy for IDN ccTLDs
were supposed to be consistent. However, due to the incremental changes of the ccTLD Fast Track process since 2009, the discrepancy between these processes has increased. Secondly, since the introduction of sting similarity review in 2009, the methods to evaluate
string similarity and underlying scientific insights in this area have evolved and, therefore, a review of the original approach is highly desirable.
Should we still strive to harmonize string similarity review under the two processes? If so, how could we all ensure this given both are developed under different PDPs?
3. Progress on IFR
During our Barcelona meeting we informed you that the ccNSO - despite all the efforts - has not been able to appoint to the IFRT a representative from a ccTLD manager that is not a member of the ccNSO. We suggested to appoint a representative
from a ccNSO member ccTLD on an interim basis to ensure that ccTLD community which is one of the direct customer groups of PTI, is represented on the review by 3 members. Since then ICANN Org reached out to all the appointing entities to seek support for this
solution. It is our understanding that one of the appointing entities objected, with reference to the Bylaws.
As this Review has been launched under auspices of the Board, could you provide an update on the current status? How will it be ensured that 3 members of the ccTLD community are included in the IFRT?
Looking to the future, the next IFR shall be convened in five years, measured from the date the previous was convened (September 2018). It is clear that with the growing number of ccNSO members, in five years it will be even more
difficult to find a non-member ccTLD representative. To change this, a fundamental Bylaw change is required. What is the process to introduce the change in time for the next IANA Functions review?
Joint meeting: ccNSO & GAC
Wednesday, 13 March | 10:30-11:15 | Ohwada B
Participate remotely:
https://participate.icann.org/kix64-ohwadabb
Agenda:
1.
status report ccNSO Retirement Policy Development Process (PDP) Working Group
2.
DNS over https
3.
Discussion on the future scheduling of the joint meetings between the ccNSO and GAC: The GAC meets with other SO/ACs on Sunday in Kobe and proposed to have future joint meetings
between ccNSO & GAC earlier during the ICANN-meetings week, when they meet with other SO/ACs. This means the joint meeting between ccNSO & GAC would no longer be part of the ccNSO Members Meeting days. The GAC and ccNSO will discuss this proposal in Kobe.
Other briefing documents:
Links to bookmark now:
https://community.icann.org/display/ccnsowkspc/ICANN64+-+Kobe+2019
The one-stop wiki page for all your Remote Participation queries: this wiki page covers remote participation details for all ccNSO open and public meetings.
https://community.icann.org/pages/viewpage.action?pageId=100533721
Printed copies of the agenda for the ccNSO Members Meeting will be available in the meeting room as of Tuesday 12 March (Room: Ohwada A)
https://community.icann.org/display/ccnsowkspc/TechDay+Kobe+-++Agenda
https://community.icann.org/display/ccnsowkspc/ICANN64+Google+Calendar+-+Kobe%2C+Japan (ccnso.agenda@gmail.com).
Quick guide on how to add it to your own calendar: https://ccnso.icann.org/sites/default/files/filefield_42693/google-cal-setup-28may15-en.pdf
The presentation slides will be published during or shortly after the meeting on https://64.schedule.icann.org/ (go
to the respective session) and later on https://ccnso.icann.org/en/meetings/kobe64 (click
“Presentations”)
https://64.schedule.icann.org/
https://meetings.icann.org/en/kobe64 (including info regarding transportation,
venue map etc.) Please make sure to register for the meeting
meetingapp.icann.org
Best regards.
Joke Braeken
ccNSO Policy Advisor
Follow @ccNSO on Twitter: https://twitter.com/ccNSO
[twitter.com]
Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/
[facebook.com]