March 2019 - Ccnso-council - lists.icann.org

Triage recommendations: 10, 11, 12, 13 - 2019
by Joke Braeken March 9, 2019

March 9, 2019

Dear Councillors, We have received several requests for input, that were addressed via triage recommendations. Below I have included an overview of all recommendations as formulated by the Triage Committee. The summary and background of the recommendations, the proposed action for each of them and the relevant deadlines, are included in the tables further down in this e-mail. If you do not agree with the recommendations, kindly let me know by Tuesday 12 March 2019, 23:59 UTC. Thank you! Overview triage recommendation number + topic: 10-2019: Call for EoI for Independent Financial Expert to ICANN Board and Audit Committee 11-2019: Proposal Hebrew Script Root Zone Label Generation Rules 12-2019: Call for volunteers: IGO and INGO Identifiers Protection Policy Implementation 13-2019: EoI sought for chair of GNSO EPDP on the Temporary Specification for gTLD Registration Data – phase 2 Apologies for deviating from the proposed template: all recommendations were incorporated in 1 single email, instead of sending several separate ones. Kindly let me know if there are any concerns regarding this approach. Number: 10-2019 Topic: Call for EoI for Independent Financial Expert to ICANN Board and Audit Committee Request from: ICANN Summary: ICANN's Board Audit Committee [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_s0…> is responsible for reviewing the annual financial report of ICANN's operations and financial position and overseeing ICANN's internal financial and accounting controls and procedures. To continue to improve controls and procedures, the Board Audit Committee adopts many of the best practices used by private company audit committees. One practice is the use of an external volunteer to serve as an independent consultant to the Board Audit Committee to provide financial expertise, advice and assistance on questions related to ICANN's financial statements (the "Financial Expert to Audit Committee"). Currently, the ICANN Board Audit Committee is seeking to fill this opening as soon as possible. It is not expected that the Financial Expert will attend every Audit Committee meeting but will serve at the pleasure of the Audit Committee to discuss or analyze issues as appropriate. Close date: 5 April 2019 Read more: https://www.icann.org/news/announcement-2019-02-07-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: Share with the following mailing lists: ccnso-members, broader ccTLD community, ccnso-council. Share via the ccNSO twitter account. Impact on ccNSO/ccTLDs: LOW Number: 11-2019 Topic: Proposal Hebrew Script Root Zone Label Generation Rules Request from: Global Domains Division Summary: The Hebrew community has formed the Hebrew Script Generation Panel (GP), which in turn has developed a Proposal for Hebrew Script Root Zone Label Generation Rules (Proposal [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_j1…> and Supporting Document [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_SR…>). As per the LGR procedure [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_VM…>, this proposal is being posted for public comment to allow those who have not participated in the Hebrew Script GP to make their views known to the GP. Based on the feedback, the Hebrew Script GP will finalize the proposal for submission for integration into the Label Generation Rules for the Root Zone (RZ-LGR) Close date: 18 April 2019 Read more: https://www.icann.org/public-comments/hebrew-lgr-2019-02-20-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Recommended action: Share with the following mailing lists: ccnso-members, broader ccTLD community, ccnso-council. Share via the ccNSO twitter account. Impact on ccNSO/ccTLDs: LOW Number: 12-2019 Topic: Call for volunteers: IGO and INGO Identifiers Protection Policy Implementation Request from: GNSO Summary: On 27 January 2019, the Board adopted <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> policy recommendations on Protections for Certain Red Cross and Red Crescent Names in All Generic Top-Level Domains and directed their implementation. This new consensus policy will supplement the previously-adoptedProtection of IGO and INGO Identifiers in All gTLDs Policy<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> by which the specific terms Red Cross, Red Crescent, Red Lion & Sun and Red Crystal were withheld from registration. The Implementation Review Team (IRT) supporting the implementation of the Protection of IGO and INGO Identifiers in All gTLDs Policy<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> will add these new recommendations to its scope. For this IRT, volunteers involved in the Red Cross organization, members from the Reconvened Working Group, and Registry professionals capable of implementing the reservation of labels (that will range in the thousands) in the domain registration process are particularly sought. Familiarity with the policy recommendations <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> as well as the deliberations that informed those recommendations is a minimum requirement for IRT members. Close date: 18 March 2019 Read more: Please see IGO and INGO Policy IRT wiki page<https://community.icann.org/display/IIPIRT/IGO+and+INGO+Identifiers+Protect…> Recommended action: none Impact on ccNSO/ccTLDs: LOW Number: 13-2019 Topic: EoI sought for chair of GNSO EPDP on the Temporary Specification for gTLD Registration Data – phase 2 Request from: GNSO Summary: The GNSO is looking for expressions of interest to chair Phase 2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. The EPDP Team recently completed its Phase 1 work and is expected to commence planning for Phase 2 at ICANN64 meeting in Kobe, Japan. During Phase 2, the EPDP Team will work on a system for standardized access to non-public registration data, topics identified in the annex to the Temporary Specification, as well as a number of carry over items from Phase 1.The GNSO Council is looking to appoint a neutral Chair to the EPDP Team. Close date: 22 March 2019 Read more: https://www.icann.org/news/announcement-2019-03-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: none Impact on ccNSO/ccTLDs: LOW Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Saturday, 9 March ccNSO-related session at ICANN64 Kobe
by Kimberly Carlson March 8, 2019

March 8, 2019

Hello, Welcome to Kobe! Here are today's ccNSO-related sessions for today (all meetings are open and observers are welcome): Day 1, Saturday, 9 March * Guidelines Review Committee<https://64.schedule.icann.org/meetings/962145> | 1030-1200 (block 2) | Room 403 (KICC) | https://participate.icann.org/kix64-403/ * Study Group on use of Emoji as SLDs <https://64.schedule.icann.org/meetings/962146> | 1330-1500 (block 3) |Room 403 (KICC) | https://participate.icann.org/kix64-403/ * cc PDP on Retirement<https://64.schedule.icann.org/meetings/962147> | 1515-1830 (blocks 4 & 5) | Room 403 (KICC) | https://participate.icann.org/kix64-403/ Today's meetings are in KICC Room 403. To get there from the Portopia Hotel lobby, go up the escalators to the 2nd floor, turn left and follow the signs to access the KICC walkway. REGISTRATION LOCATION: Kobe Portopia Hotel - South Wing Ohwada Foyer ON-SITE REGISTRATION HOURS: Friday, 08 March 08:00 - 17:30 Saturday, 09 March 08:00 - 18:30 Sunday, 10 March 08:00 - 18:30 Monday, 11 March 08:00 - 18:30 Tuesday, 12 March 08:00 - 18:30 Wednesday, 13 March 08:00 - 18:30 Thursday, 14 March 08:00 - 13:00 You will need the registration code that you should have received via email and a government-issued photo identification to pick up your conference badge . Schedule is subject to change, so please continue to check the full ICANN schedule: https://64.schedule.icann.org/ And the wiki: https://participate.icann.org/p3yhxmdzn8o/ Other helpful links: Hotel & Travel<https://64.schedule.icann.org/pages/3290> Venue Map<https://64.schedule.icann.org/floor_maps/3664?per_page=30&with%5bfloor_map_…> Location Information<https://64.schedule.icann.org/pages/3291> Thank you and wishing you a successful meeting. Best, Kim _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

4 5

Draft agenda and session overview Council prep meeting: Sunday, 10 March 2019 | 12:15-13:30 | Emerald
by Bart Boswinkel March 8, 2019

March 8, 2019

Dear all, Please find included draft agenda and sessions overview for the prep meeting directly following the Council workshop Sunday 10 March. Lunch will be served In case this was not clear: all future Councillors are welcome and kindly invited to attend both the Workshop on Monday ( see Katrina’s email) and this prep session. A more detailed agenda for the regular Council meeting will follow later in the week. Kind regards, Bart

1 0

ccNSO Activity Summary | February 2019
by Kimberly Carlson March 5, 2019

March 5, 2019

ccNSO Activity Summary February 2019 ICANN64: Full Schedule: https://64.schedule.icann.org/ ccNSO-related sessions: https://community.icann.org/x/wwT_BQ (including remote participation details) TechDay agenda: https://community.icann.org/x/9Ab_BQ Working/Study Group Meeting Output: Recordings of various Working Group Meetings can be found here: http://ccnso.icann.org/calendar Comments/statements from the SOPC and Council during the month of February can be found here<https://ccnso.icann.org/en/about/statements.htm> 28 February - ccPDP on Retirement Working Group Telephone Conference - Wiki<https://community.icann.org/x/DqEWBg> 27 February - ccNSO Study Group on Use of Emoji as SLD Telephone Conference - Wiki<https://community.icann.org/x/M4ANBg> 25 February - Guidelines Review Committee Telephone Conference - Wiki<https://community.icann.org/x/yqMWBg> 19 February - ccNSO Review Working Party (RWP) Telephone Conference - Wiki<https://community.icann.org/x/NpoWBg> 14 February - ccPDP on Retirement Working Group Telephone Conference - Wiki<https://community.icann.org/x/DKEWBg> 14 February - TLD OPS Standing Committee Telephone Conference 13 February - ccNSO Study Group on Use of Emoji as SLD Telephone Conference - Wiki<https://community.icann.org/x/MYANBg> 4 February - Guidelines Review Committee Telephone Conference - Wiki<https://community.icann.org/x/95EWBg> ccNSO Council: ccNSO Council call 14 February - wiki<https://community.icann.org/x/IQn_BQ> ccNSO Council preparation material and output can be found here: http://ccnso.icann.org/about/council/minutes.htm ccNSO Council Decisions and Resolutions: http://ccnso.icann.org/about/council/decisions-resolutions.htm ccNSO Council Wiki space <https://community.icann.org/x/BiyAAw> Links and Announcements regarding the IANA Stewardship Transfer and ICANN's Accountability Process: IANA Stewardship Transition Implementation Page<https://www.icann.org/stewardship-implementation> CSC Reports and Findings<https://www.icann.org/en/csc/reports> Other Announcements: ICANN Submits Application to International Telecommunications Union for ITU-D Sector membership<https://www.icann.org/news/announcement-2-2019-02-28-en> - 28 February Successful Candidates Announced for ICANN65 Fellowship<https://www.icann.org/news/announcement-2019-02-28-en> - 28 February David Conrad to Oversee IANA Services and Public Technical Identifiers<https://www.icann.org/news/announcement-2019-02-25-en> - 25 February ICANN org publishes Charter on Government Engagement Approach<https://www.icann.org/news/blog/icann-org-publishes-charter-on-government-e…> - 25 February ICANN Calls for Full DNSSEC Deployment, Promotes Community Collaboration to Protect the Internet<https://www.icann.org/news/announcement-2019-02-22-en> - 22 February Cyrus Namazi Appointed to Senior Vice President of ICANN's Global Domains Division<https://www.icann.org/news/announcement-2019-02-21-en> - 21 February Application Deadline Extended for ICANN and PTI Leadership Positions<https://www.icann.org/news/announcement-2019-02-19-en> - 19 February Alert Regarding Published Reports of Attacks on the Domain Name System<https://www.icann.org/news/announcement-2019-02-15-en> - 15 February Second Security, Stability, and Resiliency (SSR2) Review Team Update<https://www.icann.org/news/blog/second-security-stability-and-resiliency-ss…> - 13 February ICANN Announces Selected Participants For NextGen@ICANN65<https://www.icann.org/news/announcement-2019-02-08-en> - 8 February Recommendations for Managing Internationalized Domain Name Variant Top-Level Domains Published<https://www.icann.org/news/announcement-2019-02-05-en> - 5 February ICANN's Security Stability and Resiliency (SSR) Team Responds to Public Input on Domain Abuse Activity Reporting (DAAR) Reviews<https://www.icann.org/news/announcement-2019-02-01-en> - 1 February _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 0

ICANN Calls for Full DNSSEC Deployment, Promotes Community Collaboration to Protect the Internet
by Joke Braeken March 4, 2019

March 4, 2019

Dear all, ICANN believes that there is an ongoing and significant risk to key parts of the Domain Name System (DNS) infrastructure. In the context of increasing reports of malicious activity targeting the DNS infrastructure, ICANN is calling for full deployment of the Domain Name System Security Extensions (DNSSEC) across all unsecured domain names. The organization also reaffirms its commitment to engage in collaborative efforts to ensure the security, stability and resiliency of the Internet’s global identifier systems. As one of many entities engaged in the decentralized management of the Internet, ICANN is specifically responsible for coordinating the top-most level of the DNS to ensure its stable and secure operation and universal resolvability. On 15 February 2019, in response to reports of attacks against key parts of the DNS infrastructure, ICANN offered a checklist [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_uC…> of recommended security precautions for members of the domain name industry, registries, registrars, resellers, and related others, to proactively take to protect their systems, their customers’ systems and information reachable via the DNS. Public reports [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_x0…> indicate that there is a pattern of multifaceted attacks utilizing different methodologies. Some of the attacks target the DNS, in which unauthorized changes to the delegation structure of domain names are made, replacing the addresses of intended servers with addresses of machines controlled by the attackers. This particular type of attack, which targets the DNS, only works when DNSSEC is not in use. DNSSEC is a technology developed to protect against such changes by digitally 'signing' data to assure its validity. Although DNSSEC cannot solve all forms of attack against the DNS, when it is used, unauthorized modification to DNS information can be detected, and users are blocked from being misdirected. ICANN has long recognized the importance of DNSSEC and is calling for full deployment of the technology across all domains. Although this will not solve the security problems of the Internet, it aims to assure that Internet users reach their desired online destination by helping to prevent so-called “man in the middle” attacks where a user is unknowingly re-directed to a potentially malicious site. DNSSEC complements other technologies, such as Transport Layer Security (most typically used in HTTPS) that protect the end user/domain communication. As the coordinator of the top-most level of the DNS, ICANN is in the position to help mitigate and detect DNS-related risks, and to facilitate key discussions together with its partners. The organization believes that all members of the domain name system ecosystem must work together to produce better tools and policies to secure the DNS and other critical operations of the Internet. To facilitate these efforts, ICANN is planning an event for the Internet community to address DNS protection: The first is an open session during the upcoming ICANN64 public meeting on 9-14 March 2019, in Kobe, Japan. As we learn more information, updates may be provided. For information about ICANN64, visithttps://meetings.icann.org/kobe64 [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__newsalerts.icann.org_v0…>. Read more: https://www.icann.org/news/announcement-2019-02-22-en Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Reminder: NomCom launched a call for EoI - Apply Now for ICANN and PTI Leadership Positions
by Joke Braeken March 4, 2019

March 4, 2019

Dear all, The ICANN Nominating Committee (NomCom) invites interested individuals to submit an expression of interest in key leadership positions within ICANN and Public Technical Identifiers (PTI). Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the Internet's technical coordination and policy development. The deadline to submit applications is 18 March 2019 at 23:59 Universal Coordinated Time (UTC). NomCom is also accepting recommendations of suggested candidates. The NomCom is inviting applications and recommendations for the following positions: * Three members of the ICANN Board of Directors. * One member of the PTI Board of Directors. * Three regional representatives to the At-Large Advisory Committee (ALAC) – one from the Asia, Australia, and Pacific Islands region, one from the Latin America and Caribbean Islands region, one from the Africa region. * Two members of the Generic Names Supporting Organization (GNSO) Council. * One member of the Country Code Names Supporting Organization (ccNSO) Council. Guided by the broad public interest, those selected will work to fulfill ICANN's mission to coordinate the global Internet's system of unique identifiers, and in particular, to ensure its stable and secure operation. The selected leaders will make a valuable public service contribution toward the evolution of the Domain Name System as an essential global resource. Read more about the qualifications, the application deadline and process, the Meetings, Travel, Reimbursement, and Compensation here: https://www.icann.org/news/announcement-2019-01-17-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> or learn more by visiting the 2019 NomCom website<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_nomcom20…>. If you have any questions or comments, email nomcom2019(a)icann.org<mailto:nomcom2019@icann.org>. Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 1

Recommendations for Managing Internationalized Domain Name Variant Top-Level Domains Published
by Joke Braeken March 4, 2019

March 4, 2019

Dear All, ICANN announced the release of the Recommendations for Managing Internationalized Domain Name (IDN) Variant Top-Level Domains (TLDs)<https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-0…> as a collection of six documents. These recommendations have been developed by the ICANN organization with community feedback received during the Public Comment<https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-…> period. A. IDN Variant TLD Implementation – Executive Summary<https://www.icann.org/en/system/files/files/idn-variant-tld-exec-summary-25…> [PDF, 70 KB] B. IDN Variant TLD Implementation – Motivation, Premises and Framework<https://www.icann.org/en/system/files/files/idn-variant-tld-motivation-prem…> [PDF, 391 KB] C. IDN Variant TLD Implementation – Recommendations and Analysis<https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations…> [PDF, 382 KB] D. IDN Variant TLD Implementation – Rationale for RZ-LGR<https://www.icann.org/en/system/files/files/idn-variant-tld-rationale-lgr-2…> [PDF, 497 KB] E. IDN Variant TLD Implementation – Risks and their Mitigation<https://www.icann.org/en/system/files/files/idn-variant-tld-risks-mitigatio…> [PDF, 230 KB] F. IDN Variant TLD Implementation – Appendices (A: Definitions, B: Use of ROID, C: Limiting Allocated Variant TLDs)<https://www.icann.org/en/system/files/files/idn-variant-tld-appendices-25ja…> [PDF, 530 KB] Read more: https://www.icann.org/news/announcement-2019-02-05-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

You're invited to TechDay @ ICANN64-Kobe | 11 March
by Kimberly Carlson March 4, 2019

March 4, 2019

Dear all, The TechDay @ICANN64-Kobe agenda has been finalized; please find attached and here<https://community.icann.org/x/9Ab_BQ>. Day 3, Monday, 11 March TechDay | 1030-1645 (block 2<https://64.schedule.icann.org/meetings/962022>, block 3<https://64.schedule.icann.org/meetings/962023> & block 4<https://64.schedule.icann.org/meetings/962024>) | Ohwada A Remote participation: https://participate.icann.org/kix64-ohwadaa/ Other helpful links: Full ICANN64 Schedule<https://64.schedule.icann.org/> ccNSO-related sessions at ICANN64-Kobe<https://community.icann.org/x/wwT_BQ> Google Calendar<https://community.icann.org/x/7Qb_BQ> Hotel & Travel<https://64.schedule.icann.org/pages/3290> Venue Map<https://64.schedule.icann.org/floor_maps/3664?per_page=30&with%5bfloor_map_…> Location Information<https://64.schedule.icann.org/pages/3291> As always, if you have any questions, comments or concerns, please do not hesitate contacting me or the Tech Working Group at ccNSO-techwg(a)icann.org<mailto:ccNSO-techwg@icann.org>. Thank you, safe travels and see you soon. Best, Kim _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 0

Final Report CSC Effectiveness review team
by Bart Boswinkel March 4, 2019

March 4, 2019

Dear Katrani, Please find included the Final Report of the CSC Effectiveness Review Team for consideration and adoption by the ccNSO Council. The Report has been submitted to the GNSO Council as well for their consideration and adoption. Based on the comments received on the Initial Report, no substantive changes were made. Recommendation 2 regarding then need to inform Liaison appointing organisations about the level of attendance of the liaisons was refined, following the ccNSO Councils comment. On behalf of the ERT, Bart

1 0

Re: [ccnso-council] [Ext] [cctldcommunity] Consult the agenda of the joint meetings between the ccNSO and ALAC, the GNSO Council, the ICANN Board and GAC.
by Joke Braeken March 4, 2019

March 4, 2019

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: 1. Welcome, speaker introduction and explanation of the shortened session 2. Introduction to Segun Akano, new ccNSO appointed liaison to ALAC, including thanks to Wafa Dahmani 3. Brief overview of the At-Large Organigram and priorities for At-Large in the last Public Comment on the FY20 Budget and Operating Plan. 4. ccNSO Comments on the ICANN Plans and Budgets & introduction to SOPC: Giovanni Seppia, ccNSO SOPC chair 5. Q&A and wrap-up 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_jointmeet… Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org From: cctldcommunity <cctldcommunity-bounces(a)lists.nic.cz> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Friday, 1 March 2019 at 15:35 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, ccnso-council <ccnso-council(a)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: * Read the ICANN64 ccNSO Members Meeting "Session summaries<https://community.icann.org/download/attachments/100533721/ICANN64SessionSu…>" Get prepared and learn more about the topics covered during the ICANN64 ccNSO Members Meeting * Consult the pre-ICANN64 Policy Report [go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__go.icann.org_pre64&d=D…> The purpose of this report is to summarize policy activities and meeting or session highlights across the ICANN policy development community – including the ccNSO - taking place at ICANN64. Links to bookmark now: * ccNSO Schedule & Remote Participation hub 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. * Agenda ccNSO Members Meeting 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) * Agenda Tech Day https://community.icann.org/display/ccnsowkspc/TechDay+Kobe+-++Agenda * ccNSO ICANN64 Google Calendar https://community.icann.org/display/ccnsowkspc/ICANN64+Google+Calendar+-+Ko… (ccnso.agenda(a)gmail.com<mailto: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-setu…<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…> * Presentation slides The presentation slides will be published during or shortly after the meeting on https://64.schedule.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__64.schedule.icann.org_…> (go to the respective session) and later on https://ccnso.icann.org/en/meetings/kobe64<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_mee…> (click “Presentations”) * Full ICANN64 schedule https://64.schedule.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__64.schedule.icann.org_…> * ICANN64 meeting site https://meetings.icann.org/en/kobe64 (including info regarding transportation, venue map etc.) Please make sure to register for the meeting * ICANN64 Mobile App meetingapp.icann.org Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=Dw…> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso…> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGa…>

3 2