December 2019 - Ccnso-council

IANA Customer Engagement Survey Results Available
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

Hello everyone, ICANN published the results of the Internet Assigned Numbers Authority (IANA) Customer Engagement Survey which measures customer satisfaction with the IANA functions. View Customer Survey Findings<https://www.iana.org/reports/2019/customer-survey-20191210.pdf?mkt_tok=eyJp…> In the 2019 IANA Customer Engagement Survey, customers were asked to rate the IANA team on 20 statements relating to responsiveness, transparency, fairness, and attentiveness. Each statement was rated on a 1-5 scale, with one being the lowest and five being the highest level of satisfaction. The overall score amongst all customer segments was 3.9. In the previous six years, satisfaction was measured using a percentage rating, and the team obtained results over 90 percent each year. When asked about their confidence in the IANA team's ability to achieve its objectives, customers scored the team the highest, at 4.3. Satisfaction with the transparency of the Key Signing Key ceremonies also scored a 4.3. An average score of 3.7 was given to the team on statements about innovation and sense of urgency. While the results of the survey are consistently positive, participation rates have dropped over the years. Six years ago, the team saw an average response rate of 10 percent. Over the past two years there has been a decline in participation, and after simplifying the survey, the response rate for 2019 was three percent. The IANA team has implemented additional mechanisms to receive and address customer feedback. These include the post-interaction survey launched in late 2018 that encourages customers to provide immediate feedback after receipt of service from the IANA team. The IANA team dedicates resources to reviewing and responding to that feedback in a timely manner. "The annual engagement survey will allow us to evaluate how we manage our relationship with the different customer groups and identify improvements in that area in addition to the regular operational feedback we receive through the post-interaction survey," said Kim Davies, President of PTI – the ICANN affiliate responsible for delivering the IANA functions. "These two approaches together give us a broader view of both real-time customer satisfaction and calibration of our longer-term strategy from community leaders," Davies added. ICANN commissioned Echo Research, LLC, a global reputation consultancy, to administer the annual engagement survey. Stakeholders who oversee IANA functions performance (Regional Internet Registry managers, Internet Engineering Steering Group members, and the Customer Standing Committee) and direct customers who engage with the IANA team through request changes or during industry events (DNSSEC KSK ceremony participants and Trusted Community Representatives, top-level domain operators, the IETF Community, and the ccNSO and GNSO Councils) were invited to take the survey. 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

The December 2019 edition of the ccNSO monthly newsletter is out now.
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

Dear all, The December 2019 edition of the ccNSO monthly newsletter is out now. This month’s edition includes updates on the following topics: * High-level ccNSO schedule at ICANN67 in Cancún * Closure of the recent council nominations and election round * Business continuity implementation guidance for smaller ccTLD registries: the playbook is out now * ccTLD in the spotlight: 20 years VNNIC, .vn ccTLD registry * Highlights from the ccNSO Council: overview of some of the recent decisions * Happy holidays You will be able to find this month’s edition, the ccNSO Newsletter Archive and instructions on how to subscribe here: https://community.icann.org/display/ccnsowkspc/ccNSO+Newsletter 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

High-level ccNSO schedule at ICANN67 in Cancun
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

Hello everyone, The ICANN67 Community Forum<https://meetings.icann.org/en/cancun67> will be held in Cancun (7-12 March 2020). This email is to inform you about the high-level draft ccNSO schedule in Cancun. The Country Code Names Supporting Organization (ccNSO) program begins on Saturday, 7 March, with a meeting of the Guidelines Review Committee (GRC), Internet Governance Liaison Committee (IGLC) and a three-hour meeting regarding ccPDP3 (phase 1: retirement of ccTLDs. | Phase 2: review mechanism pertaining to decision on the delegation, transfer, revocation, and retirement of ccTLDs.) On Sunday, 8 March, the ccNSO Council will hold a three-hour workshop, followed by a preparatory meeting where the ccNSO will plan for their joint meetings with the ICANN Board of Directors, the At-Large Advisory Committee (ALAC), the Governmental Advisory Committee (GAC), and the Generic Names Supporting Organization (GNSO) Council. The Strategic and Operational Planning Committee (SOPC), and the Top-Level Domain Operations (TLD-OPS) Standing Committee will also hold meetings on Sunday. Tech Day<https://community.icann.org/pages/viewpage.action?pageId=124846204>, a workshop open to all community members with an interest in technical, operational, and security topics, is scheduled for Monday, 9 March. Tuesday,10 March, and Wednesday,11 March, are dedicated to the ccNSO Members Meeting<https://community.icann.org/display/ccnsowkspc/ccNSO+Members+Meeting+%7C+IC…>, where the ccTLD community and others with an interest in ccTLD-related matters will discuss and receive updates on topics relevant to ccTLD managers. This includes a discussion on the rules of the ccNSO, sessions on DNS Abuse, governance models for ccTLD Managers, the ccNSO Policy Development Process on the Retirement of ccTLDs (ccPDP3), as well as information related to ccPDP4 on the Internationalized Domain Names (IDN) policy. The ccNSO program ends on Thursday, 12 March, with a meeting by the Meetings Program Committee (MPC). The detailed ccNSO schedule, including a summary of the topics covered and remote participation details for ICANN67, will be published on the ccNSO ICANN67 workspace<https://community.icann.org/pages/viewpage.action?pageId=124846191>, closer to the meeting. 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 | Selection Process RSS GWG
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

hello all, A reminder regarding the selection process for 2 ccNSO appointed members to the RSS GWG. As discussed during the Council meeting yesterday, your action is required by Monday, 23 December (23:59 UTC). 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: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 17 December 2019 at 10:20 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Selection Process RSS GWG Dear ccNSO Councillors, The call for volunteers for the 2 ccNSO appointed members to the Root Server System Governance Working Group (RSS GWG) closed yesterday, 16 December 2019, 23:59 UTC. The ccNSO secretariat is now initiating the selection process. In accordance with the relevant ICANN Board resolution to initiate the RSS GWG, the ccNSO Council should appoint two representatives. The Councillors eligible to vote are expected to review the applications and select members based on how well the candidates meet the set of requirements. An email was sent to the individual email addresses of the members of the ccNSO Council eligible to vote, with in attachment the application material as submitted by the 6 candidates. The 6 candidates, in alphabetical order: Akçam, Abdullah Cemil (.tr) | ACA Akinsanya, Adesola (.ng) | AA Constant, Jean Nahum (.ht) | JNC Espinoza, Luis Diego (.na) | LDE Janssen, Peter (.eu) | JP Kecic, Zarko (.rs) | ZK Your action is required by Friday, 20 December 2019 (23:59 UTC) INSTRUCTIONS: * Please review the application material and select your preferred candidate – taking into account the candidate qualification requirements – by sending an email to ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org> , no later than Friday, 20 December 2019 (23:59 UTC) , with the subject line: RSS GWG. * Your most preferred candidate should receive six (6) points, the second candidate five (5) points, etc, and the sixth and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. A kind reminder that the ccNSO Secretariat will track and publish for each council member its participation in an election process. Based on each of the individual Councillor’s rankings, the Secretariat will prepare the overall ranking of all candidates and report the ranking to the ccNSO Council on 23 December 2019. The ccNSO Council chair will inform relevant ICANN staff latest on 8 January 2020 of the ccNSO appointed members to the RSS GWG. Thank you and kind regards, Joke Braeken Selection Process After closure of the call for volunteers, the materials submitted will be sent to the ccNSO Councillors eligible to select the members of the RSS GWG. Further details on the selection criteria and the selection procedure by the ccNSO Councillors can be found here: https://ccnso.icann.org/en/workinggroups/candidate-requirements-selection-p… [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_wor…> Candidate qualification requirements In accordance with the relevant ICANN Board resolution to initiate the RSS GWG, the ccNSO Council should appoint two representatives. The Councillors eligible to vote will review the applications and select members based on how well the candidates meet the set of candidate requirements listed below: * Direct experience and in-depth knowledge of the DNS Root Server System as it relates to ccTLD registry operations * Understanding the purpose of the RSS GWG * Analytical skills, ability to interpret quantitative and qualitative evidence, and capacity to draw conclusions purely based on evidence. * Able to work and communicate in written and spoken English. * Effective communication skills to represent ccTLD interests and to keep the ccNSO Council and broader ccTLD community informed on progress. * Experience in managing and/or participating in committees (e.g. meeting coordination, reporting, and escalation) in order to contribute meaningfully to the work of the GWG. * Demonstrated ability in relationship management to support diplomatic discussion, consensus driven decision making, and productive negotiation. Further a candidate: * Should indicate why she or he is interested in becoming involved in the RSS GWG. * Indicate the ccTLD manager with whom the candidate is associated. * Should be employed or have active backing by the ccTLD manager with whom the candidate is associated. * Demonstrate the support by the ccTLD manager in respect to the required time commitment to participate actively in the RSS GWG. * Commit to abide by the rules of the RSS GWG Timeline (v2) * 20 Nov: Secretariat to send out pre-announcement to community * 20 Nov: Secretariat to send proposed candidate requirements and the proposed selection procedure to ccNSO Council * 25 Nov (23:59 UTC): Council to agree on final candidate requirements and the selection procedure * 26 Nov until 16 December (23:59 UTC): call for volunteers * 17 Dec: Secretariat to send expressions of interest and application material to the individual non-conflicted ccNSO Council members * Latest on 20 Dec (23:59 UTC): Councillors will send her/his list of preferred candidates to the ccNSO Secretariat * 23 Dec: the Secretariat will prepare the overall ranking of all candidates and report the ranking to the ccNSO Council * Latest on 8 Jan: The ccNSO Council chair will inform relevant ICANN staff of the ccNSO appointed members to the RSS GWG. Background & Links * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-26nov19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> * The GWG charter, operating procedures, and work plan as well as relevant resources are published on its workspace<https://community.icann.org/pages/viewpage.action?pageId=120820189>. * ICANN Board resolution to initiate the RSS GWG: https://www.icann.org/resources/board-material/resolutions-2019-11-07-en#2.d<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> 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…>

1 0

Selection Process RSS GWG
by Joke Braeken Dec. 19, 2019

Dec. 19, 2019

Dear ccNSO Councillors, The call for volunteers for the 2 ccNSO appointed members to the Root Server System Governance Working Group (RSS GWG) closed yesterday, 16 December 2019, 23:59 UTC. The ccNSO secretariat is now initiating the selection process. In accordance with the relevant ICANN Board resolution to initiate the RSS GWG, the ccNSO Council should appoint two representatives. The Councillors eligible to vote are expected to review the applications and select members based on how well the candidates meet the set of requirements. An email was sent to the individual email addresses of the members of the ccNSO Council eligible to vote, with in attachment the application material as submitted by the 6 candidates. The 6 candidates, in alphabetical order: Akçam, Abdullah Cemil (.tr) | ACA Akinsanya, Adesola (.ng) | AA Constant, Jean Nahum (.ht) | JNC Espinoza, Luis Diego (.na) | LDE Janssen, Peter (.eu) | JP Kecic, Zarko (.rs) | ZK Your action is required by Friday, 20 December 2019 (23:59 UTC) INSTRUCTIONS: * Please review the application material and select your preferred candidate – taking into account the candidate qualification requirements – by sending an email to ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org> , no later than Friday, 20 December 2019 (23:59 UTC) , with the subject line: RSS GWG. * Your most preferred candidate should receive six (6) points, the second candidate five (5) points, etc, and the sixth and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. A kind reminder that the ccNSO Secretariat will track and publish for each council member its participation in an election process. Based on each of the individual Councillor’s rankings, the Secretariat will prepare the overall ranking of all candidates and report the ranking to the ccNSO Council on 23 December 2019. The ccNSO Council chair will inform relevant ICANN staff latest on 8 January 2020 of the ccNSO appointed members to the RSS GWG. Thank you and kind regards, Joke Braeken Selection Process After closure of the call for volunteers, the materials submitted will be sent to the ccNSO Councillors eligible to select the members of the RSS GWG. Further details on the selection criteria and the selection procedure by the ccNSO Councillors can be found here: https://ccnso.icann.org/en/workinggroups/candidate-requirements-selection-p… Candidate qualification requirements In accordance with the relevant ICANN Board resolution to initiate the RSS GWG, the ccNSO Council should appoint two representatives. The Councillors eligible to vote will review the applications and select members based on how well the candidates meet the set of candidate requirements listed below: * Direct experience and in-depth knowledge of the DNS Root Server System as it relates to ccTLD registry operations * Understanding the purpose of the RSS GWG * Analytical skills, ability to interpret quantitative and qualitative evidence, and capacity to draw conclusions purely based on evidence. * Able to work and communicate in written and spoken English. * Effective communication skills to represent ccTLD interests and to keep the ccNSO Council and broader ccTLD community informed on progress. * Experience in managing and/or participating in committees (e.g. meeting coordination, reporting, and escalation) in order to contribute meaningfully to the work of the GWG. * Demonstrated ability in relationship management to support diplomatic discussion, consensus driven decision making, and productive negotiation. Further a candidate: * Should indicate why she or he is interested in becoming involved in the RSS GWG. * Indicate the ccTLD manager with whom the candidate is associated. * Should be employed or have active backing by the ccTLD manager with whom the candidate is associated. * Demonstrate the support by the ccTLD manager in respect to the required time commitment to participate actively in the RSS GWG. * Commit to abide by the rules of the RSS GWG Timeline (v2) * 20 Nov: Secretariat to send out pre-announcement to community * 20 Nov: Secretariat to send proposed candidate requirements and the proposed selection procedure to ccNSO Council * 25 Nov (23:59 UTC): Council to agree on final candidate requirements and the selection procedure * 26 Nov until 16 December (23:59 UTC): call for volunteers * 17 Dec: Secretariat to send expressions of interest and application material to the individual non-conflicted ccNSO Council members * Latest on 20 Dec (23:59 UTC): Councillors will send her/his list of preferred candidates to the ccNSO Secretariat * 23 Dec: the Secretariat will prepare the overall ranking of all candidates and report the ranking to the ccNSO Council * Latest on 8 Jan: The ccNSO Council chair will inform relevant ICANN staff of the ccNSO appointed members to the RSS GWG. Background & Links * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-26nov19-en.htm * The GWG charter, operating procedures, and work plan as well as relevant resources are published on its workspace<https://community.icann.org/pages/viewpage.action?pageId=120820189>. * ICANN Board resolution to initiate the RSS GWG: https://www.icann.org/resources/board-material/resolutions-2019-11-07-en#2.d<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> 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

9 11

NOTES: ccNSO Council meeting | Thu, 19 December 2019 18 UTC
by Joke Braeken Dec. 19, 2019

Dec. 19, 2019

Notes ccNSO Council Meeting 19 December 2019 These high-level notes are designed to help you navigate through the content of the meeting and are not meant as a substitute for the transcript and/or recording. The recording will be posted on Council Workspace, as well as the background material shared during today’s meeting https://community.icann.org/display/ccNSOCWS/Council+Meetings+-+2019 1. Welcome and roll call Welcome by the chair. Several apologies received Ai-Chin joined the meeting today: she joins as an observer ahead of taking her seat at ICANN67. She has been subscribed to the ccNSO Council mailing list as well, to allow her to prepare for her term start. 2. Minutes & Action Items Minutes were circulated. Some action items still ongoing: overview included in the agenda, and displayed in the zoom room. 3. Intermeeting decisions (since 6 November 2019) · Approval of membership application ccNSO of .tz (Tanzania) · Appointment Alejandra Reynoso ccNSO appointed mentor fellowship program · Approval text Approval Action to change section 18 ICANN Bylaws · Submission support SLA change creation and delegation ccTLD Public Statement 4. Adoption ccNSO Council 2020 Election report Circulated on the mailing list. Nominations, followed by elections for the AP region. Thank you all for standing for the ccNSO Council. Welcome back to those that served previously, and thank you all for your commitment. Election Manager: no abnormalities. By adopting the report, the election process is closed. (Next/First) Term start is at the end of ICANN67. ccNSO to inform the ICANN Secretary and all accordingly. Move? Hiro Seconded? Stephen No questions or comments Against? None Abstain? None All in favour 5. Update Board Seat 11 Nomination Process 3 candidates. Currently undergoing background check. ICANN legal mentioned it is not yet completed. We hope that the vetting process will end by the start of the elections, foreseen for 14 January. Good that we allocated sufficient time. No questions 6. Selection candidates Root Server System Governance Working Group (RSS GWG) Application material was distributed on 17 December. All council members invited to review the application material. Time to review the application material until Monday. 7. Call for volunteers Meeting Program Committee Move? Giovanni Seconded? Alejandra No questions or comments Against? None Abstain? None All in favour Secretariat to prepare and send out call for volunteers 8. Appointment member ICANN Ethos Award Panel 2020 2 volunteers: Margarita and Stephen Move? Alejandra Seconded? Giovanni No questions or comments Against? None Abstain? None All in favour 9. PDP 3 a. Part 1 Retirement – Update Review timeline. Stephen: meet next in early January. Additional scenarios for stress-testing. b. Amendment timeline ccPDP 3: launch Part 2 of the PDP3 See meeting in Montreal: the retirement WG asked questions around oversight and review points in their process. The community present did not see any issues. Tentative timeline was reviewed again. The point for the review mechanism have been identified. We could start with Part 2 of ccPDP3 before the retirement WG completed its work. The PDP WG retirement hopes to be able to publish its initial report around the Cancun meeting. This means we can start the second part of the PDP, starting with the formation of the WG on the review mechanism. Its charter is included in the issue report. Move? Pablo Seconded? Byron Questions or comments? None Amended timeline. Issue Manager to launch the call for volunteers based on the timeline. Against? None Abstain? None All in favour 10. IDN ccTLD related work items ccPDP 4 & Bylaw change a. Launch PDP ccPDP 4: request for Issue report, appointment Issue Manager and adoption initial timeline For decision: In order to launch ccPDP4 the Council will need to take the following decisions: * Request an Issue report * Appointment of the Issue manager. * Tentative timeline to receive the Issue Report. * Appointment an oversight committee. b. Request change Article 10 and Annex B ICANN Bylaws to include IDN ccTLD Managers in the ccNSO 11. Update ccNSO related ICANN Bylaw Change Repository a. Launch PDP ccPDP 4: request for Issue report, appointment Issue Manager and adoption initial timeline The Bylaw change repository has been updated to reflect the adoption of the Fundamental Bylaw change re IFRT and amendment of Article 10 and Annex B of the ICANN Bylaw Discussed at ICANN66 in Montreal. * Request issue report * Appoint issue manager * Timeline to receive issue report * Etc Draft resolution was circulated separately, displayed in the zoom room. Evolution since PDP2 to now. Preliminary Review Team checked what needs to be updated. That will be the core of the issue report. Exchange of letters with the ICANN Board on closing the evolution of the Fast Track Process. Not a constant shape. PDP to address the open issues, and at the same time request the change of the bylaws, to have IDN ccTLDs included in the ccNSO RFC5091: delegation, transfer and revocation of ccTLDs. PDP3: they all define the IANA procedures, also applicable to IDN ccTLDs. Out of scope for this one. That will be made clear in the issue report. Counterpart at Council level for the issue manager: council subcommittee. One from each region, and one NomCom appointed council members. B. Request change Article 10 and Annex B ICANN Bylaws to include IDN ccTLD Managers in the ccNSO ICANN bylaws change, to have the inclusion of IDN ccTLDs. For discussion today, vote via email later, to allow for sufficient time to review all materials. Members voted on those changes some time ago. Email vote on part a and b. Until mid January. Bart will circulate background doc and instructions on how to volunteer for the council committee on 20 December. Based on conversations with James Gannon, GNSO might propose to jointly review the bylaws changes with ccNSO and look into all the changes that need to be introduced, to have coordination. 12. Results Council Workshop Montreal (ICANN66) & Implementation WS2 and ccNSO Organizational Review recommendations & suggestions WS2 recommendations and organisational review recommendations sometimes overlap. We need prioritisation, and several groups are working on the same thing. Triage committee will look into the prioritization Bart explains the GANNT chart. Preliminary discussion held by Triage Committee in the meanwhile. 2 out of 3 members are also a member of the review Working Party (RWP). that group focuses on the recommendations from the review results. E.g. term limit for council. Came out of the review. There are no term limits for the ccNSO Council members in the bylaws. SSAC moved forward with a bylaw change. Expectations to be done by March 2020, that is also the expectation from the ICANN Board Organisational Effectiveness Committee. 13. Preparation Cancun meeting (ICANN67, 7-12 March 2020) a. Council Workshop Some ideas already exchanged: how to efficiently run PDPs (see intro by Jordan in montreal. For discussion in Cancun). Further suggestions are welcome. 2 blocks booked on sunday morning, followed by council prep meeting and council meeting on Wednesday. b. Council meetings c. Tech Day & Members meeting Alejandra runs through the draft block schedule and the draft members meeting agenda. The Country Code Names Supporting Organization (ccNSO) program begins on Saturday, 7 March, with a meeting of the Guidelines Review Committee (GRC), Internet Governance Liaison Committee (IGLC) and a three-hour meeting of the ccNSO Retirement of country code Top-Level Domains (ccTLD) Policy Development Process (PDP) Working Group. On Sunday, 8 March, the ccNSO Council will hold a three-hour workshop, followed by a preparatory meeting where the ccNSO will plan for their joint meetings with the ICANN Board of Directors, the At-Large Advisory Committee (ALAC), the Governmental Advisory Committee (GAC), and the Generic Names Supporting Organization (GNSO) Council. The Strategic and Operational Planning Committee (SOPC), and the Top-Level Domain Operations (TLD-OPS) Standing Committee will also hold meetings on Sunday. Tech Day<https://community.icann.org/pages/viewpage.action?pageId=124846204>, a workshop open to all community members with an interest in technical, operational, and security topics, is scheduled for Monday, 9 March. Tuesday,10 March, and Wednesday,11 March, are dedicated to the ccNSO Members Meeting<https://community.icann.org/display/ccnsowkspc/ccNSO+Members+Meeting+%7C+IC…>, where the ccTLD community and others with an interest in ccTLD-related matters will discuss and receive updates on topics relevant to ccTLD managers. This includes a panel discussion on the rules of the ccNSO, and sessions on DNS Abuse, governance models for ccTLD Managers, the ccNSO Policy Development Process on the Retirement of ccTLDs (ccPDP4), as well as information related to ccPDP4 on the Internationalized Domain Names (IDN) policy. The ccNSO program ends on Thursday, 12 March, with a meeting by the Meetings Program Committee (MPC). The detailed ccNSO schedule, including a summary of the topics covered and remote participation details for ICANN67, will be published on the ccNSO ICANN67 workspace<https://community.icann.org/pages/viewpage.action?pageId=124846191>, closer to the meeting. d. Plenary sessions 3 proposals. See overview by Alejandra 1 topic submitted past deadline, not supported by ccNSO e. WG meetings f. Joint meeting with the Board (Topics for discussion) Council members are invited to suggest topics g. Joint meeting with GAC Giovanni discussed with Paer. Coordination by ccTLDs on how to fight cybercrime. Coordination efforts to avoid overlap with DNS Abuse session 14. Update ECA & CSC a. ECA Stephen sent email on fundamental bylaw change as discussed in Montreal. Still waiting for feedback from ICANN legal, regarding the early support by ALAC. No effect on outcome of the bylaw change. ECA is quit for the moment, until adoption PTI budget etc. b. CSC. * PTI Report met 100% of the Service Level Agreements (SLAs) in November. * After the ccNSO & gNSO approved the Label Generation Rulesets metrics, they will start to be included in the December PTI report, which will be delivered in January. * The public comment period for the Proposed IANA Service Level Agreements (SLAs) for ccTLD Creation and Transfer is over and its report has been published. Next step is for the CSC and PTI to approve, prior to sending it to the ccNSO and gNSO councils for approval. * IFRT update: In Montréal they had an initial kick-off meeting to get to know the team. First call was last week and they have started to define the work to be done. * CSC monthly meetings were adjusted to a fixed day of the week (Wednesdays) always close to the 15th of the month. 15. Updates Chair, Vice-Chairs and Councillors, Regional Organisations, secretariat. none 16. Updates WGs. a. GRC GRC discussed the session in Cancun regarding the rules of the ccNSO b. IGLC The IGLC is meeting again in January. The survey is still open until the end of the year. https://ccnso.icann.org/en/announcements/announcement-08nov19-en.htm c. SOPC The SOPC had a call this week to prepare its work for the public comment period on the ICANN FY21-25 Operating Plan and Budget and FY21 Operating Plan that will open on 20 Dec. ICANN Finance participated in part of the call. We are going to implement a more interactive approach to produce the comment and focus on 3-4 key areas that will be further discussed during the SOPC meeting in Cancun. We are also going to further liaise with the gNSO Committee in charge of producing input to ICANN Strategy and Operating Plans. d. Meeting Program Committee See previous agenda item e. TLD-OPS https://ccnso.icann.org/en/announcements/announcement-17dec19-en.htm f. Auction Proceeds Draft final report out for review by CCWG. Will be published for public comments on Monday, 23 December. Deadline: 14 February. 17. Update liaisons a. Update ALAC Liaison (written update) - received b. Update GNSO Liaison (written update) 18. Next meetings 2020 proposed Council calls: · January 23 – 18:00 UTC · February 20 – 12:00 UTC (TBD) · March @ICANN67 · April 16 – 12:00 UTC · May 21 – 18:00 UTC · June @ICANN68 · August 20 – 12:00 UTC · September 17 – 18:00 UTC · October @ICANN69 · November 19 – 12:00 UTC · December 17 – 18:00 UTC Various conflicts for the 20 Febr suggested date. February meeting: have the call on the Friday, for updating and prep for ICANN67. Or the week before, and then take decisions by email. 19. AOB none 20. Closure Today’s meeting was shorter call than usual. Have a good season’s break, happy holidays and enjoy the time off. Happy New Year. 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

Notes | ccNSO Council Meeting (19 December 2019 | 18 UTC)
by Joke Braeken Dec. 19, 2019

Dec. 19, 2019

hello All, To follow the live notes during today’s ccNSO Council meeting (19 December 2019 | 18 UTC), go to : https://docs.google.com/document/d/1GN5AaYNHS-fE46VU46m_yNK6Xn1HtB9uFgj1FTs… These high-level notes are designed to help you navigate through the content of the meeting and are not meant as a substitute for the transcript and/or recording. The recording will be posted on Council Workspace, as well as the background material shared during today’s meeting https://community.icann.org/display/ccNSOCWS/Council+Meetings+-+2019 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

FW: Additional documents
by Bart Boswinkel Dec. 19, 2019

Dec. 19, 2019

Again apologies Bart From: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Tuesday, 17 December 2019 at 18:37 To: "ccNSO-Council(a)ccNSO.Org" <ccNSO-Council(a)ccNSO.Org> Subject: Additional documents Dear all, Please find included 3 additional documents for Thursdays Council call: Draft resolution launch ccPDP4 (item 10a) Draft letter to the Board on change of Article 10 (item 10b) Update Bylaw repository (item 11) Tomorrow ( Wednesday) I’ll circulate the latest version of the agenda and include the draft resolution. Kind regards, Bart

1 0

FW: Agenda and draft resolutions 19 December 2019
by Bart Boswinkel Dec. 19, 2019

Dec. 19, 2019

Dear all, Apologies for noticing before but I send the draft resolutions etc. to the wrong email address Kind regards, Bart From: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Wednesday, 18 December 2019 at 13:44 To: "ccNSO-Council(a)ccNSO.Org" <ccNSO-Council(a)ccNSO.Org> Subject: Agenda and draft resolutions 19 December 2019 Dear all, Please find included the agenda and draft resolutions Kind regards, Bart Draft Agenda ccNSO Council Meeting 19 December 2019 Welcome and roll call Minutes & Action Items Minutes Minutes of the November 2019 meeting have been circulated on 10 December 2019. Action items Action Item 156-01: The Chair of the Council is requested to inform the Chair of the Customer Standing Committee and GNSO accordingly. (approval IANA Naming Function SLA Change): Completed Action Item 156-02: The chair of the ccNSO is requested to notify the Empowered Community Administration in writing of this decision as soon as possible and forward this notice to the Secretary. Completed Action Item 156-03: Call for volunteers – PDP Working Group 2 and Issues manager update timeline/schedule. Completed, see agenda item 9. B. Action Item 156-04: The Secretariat is requested to prepare for the next meeting of Council: • The Request for the Issue Report, which is advised to include: Scope of the issues to be addressed (listed in the Final report of the Preliminary Review team) Structure of work of the PDP: Task Force or Working Group Tentative timeline for the Issue Report. Assuming the Council will decide to launch ccPDP4 at its December 2019 meeting, the timeline should allow for a Council decision on the initiation of ccPDP4 by the Cancun meeting (ICANN67). Consideration on the appointment of the Issue manager Draft a letter to inform the GAC on scope of issue to be addressed, and need for PDP(s). In addition, inform them how they will be engaged in the process, and tentative timeline. Completed See Agenda item 10 a. Action Item 156-05 The Secretariat is requested to prepare for the next Council meeting a letter to the Board requesting the change of Article 10 and Annex B of the ICANN Bylaws to enable membership of the ccNSO for IDN ccTLD Managers Include in the letter a reference to the proposed Bylaws changes under ccPDP 2 • Explain that the membership definition has been further updated to mitigate the effect of the October 2016 changes of Article 10.4(a). Completed. See agenda item 10 b Action Item 156-06: The Triage Committee is requested to prepare work plan and suggest priorities on implementation of the most relevant Areas for improvement of the ccNSO and report back to Council at February meeting. Ongoing Action Item 156-07: The Chair of the Council is requested to inform the chairs of the working groups and committees of the Council decision to request charter reviews. Ongoing Action item 156-08 Reach out to Barbara Povse on whether she is available/interested in the leadership training (along with Pablo Rodriguez). Completed Intermeeting decisions (since 6 November 2019) Approval of membership application ccNSO of .tz (Tanzania) Appointment Alejandra Reynoso ccNSO appointed mentor fellowship program Approval text Approval Action to change section 18 ICANN Bylaws Submission support SLA change creation and delegation ccTLD Public Statement Adoption ccNSO Council 2020 Election report For adoption Adoption closes the Election process formally. Draft Resolution Background In March 2020, at the end of the ccNSO meeting during ICANN67, the term of the following ccNSO Council members ends: AF region: Souleymane Oumtanaga (.ci) AP region: Hirofumi Hotta (.jp) EU region: Giovanni Seppia (.eu) LAC Region: Alejandra Reynoso (.gt) NA Region: Stephen Deerhake (.as) Following the applicable Guideline, the ccNSO Council appointed the Election manager and adopted the Election timeline at its meeting on 22 August 2019. The Election manager submitted the Election Report on 11 December 2019. Decision The ccNSO Council adopts the Council Election Report FY 2020, notes the observations, and thanks Joke Braeken for her work as Election Process Manager. By this adoption the election process 2020 is closed. The ccNSO Council congratulates the elected candidates: · AF region: Souleymane Oumtanaga (.ci) · AP region: Ai-Chin LU (.tw) · EU region: Giovanni Seppia (.eu) · LAC Region: Alejandra Reynoso (.gt) · NA Region: Stephen Deerhake (.as) The Council notes that elected candidates will take their seat at the end of the Council meeting at ICANN67 meeting in Cancun, Mexico. The chair of the ccNSO is requested to inform the ICANN Secretary and candidates accordingly and invite the future Councillors for the upcoming Council workshop at the Cancun meeting. Update Board Seat 11 Nomination Process Informational Selection candidates Root Server System Governance Working Group (RSS GWG) Informational & reminder Call for volunteer closed on 16 December 2019. Selection process by Council closes on 20 December 2019. Call for volunteers Meeting Program Committee For decision Draft Resolution The ccNSO Council request the secretariat to prepare and send out a call for volunteers for membership of the Meeting Program Committee by mid- January 2020. Appointment member ICANN Ethos Award Panel 2020 The ccNSO Appointees to the 2019 Ethos Award Selection Panel are Stephen Deerhake and Ajay Data. Both are not term limited (appointed in January 2019 for first term). Draft Resolution After call for volunteers to Council the following Councillors volunteered: Margarita Valdes (.cl) Stephen Deerhake (.as) The ccNSO Council appoints both as ccNSO appointee to ICANN’s Ethos Award Panel 2020. The chair is requested to inform relevant ICANN staff accordingly PDP 3 Part 1 Retirement – Update Informational Amendment timeline ccPDP 3: launch Part 2 of the PDP3 For decision: amendment timeline, implies launch Part 2 and call for volunteers WG Review Mechanism. The timeline has been updated to reflect progress RET WG and opportunity to work in parallel. Draft Resolution Background Taking into account the progress to date of the WG Retirement, the schedule for PDP 3 as amended at the 13 March 2019 Council meeting needs to adjusted to reflect progress to date and to adjust the timing of the call for volunteers fro the second WG under ccPDP3, which is tasked to develop a review mechanism for decisions pertaining to the delegation, transfer, revocation and retirement of ccTLDs. The updated schedule was presented to the Retirement WG, which considered the proposed schedule reasonable. Decision The ccNSO Council has taken notice of and confirms the amended schedule and timeline of ccNSO PDP 3 version 3, as proposed by the PDP Issue Manager and request the Issue Manager to launch the call for volunteers as foreseen in the updated schedule and timeline. IDN ccTLD related work items ccPDP 4 & Bylaw change Launch PDP ccPDP 4: request for Issue report, appointment Issue Manager and adoption initial timeline For decision: In order to launch ccPDP4 the Council will need to take the following decisions: Request an Issue report (ICANN Bylaws, Annex B section 1 and 2). Written request (Council resolution) which describes the topics/ issue at high level that needs to be addressed. The request for the issue report will determine the breadth and width of the issues to be addressed and hence whether the policy development process Appointment of the Issue manager. The role of the issue manager is defined in Annex B. Main tasks are effectively to manage the process, which includes ensuring progress and reporting. Tentative timeline to receive the Issue Report. Unless otherwise defined, the issue report should be available within 15 days after appointment. However to ensure an adequate basis for the next Council decision, for example the required Opinion of ICANNs general Council on whether the issues are within the scope of the ccNSO and requirement to draft comprehensive Issue Report, the suggestion is to request the Issue Report by mid- February 2020. This would allow the Council to initiate the PDP prior to the Cancun meeting and use that meeting for PDP4 work. Appointment an oversight committee. Although not required, the ccNSO PDP allows for the creation of a Council committee that will oversee the Issue Manager, at least during the first stage of the process. Experience in the proceeding PDP’s has shown that this mechanism ensures an adequate definition of the issues at stake and progress. If Council intends to appoint such a committee it is suggested to appoint one Councillor from every region under chairmanship of the chair of the ccNSO. Draft Resolution Background In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP 2) Board Report in September 2013 to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: · Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. · Proposals to enable the inclusion of IDN ccTLD in the ccNSO. By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1]. In March 2019 the ccNSO Council tasked a team (PRT)to review ccPDP2 in light of the evolved Fast Track Process, request of the ICANN Board of Directors with respect to IDN Variants and other relevant developments and advise the Council on whether to launch an additional Policy Development Process to address open issues, if any The PRT advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various items it had identified, including the de-selection of IDN ccTLD strings. In order to implement the adopted PRT recommendations the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and stop the evolution of the Fast Track Process. In November 2019 the ICANN Board confirmed this approach. Following the initial discussions of Council, input and feed-back was sought from the community at the Kobe (ICANN64), Marrakesh (ICANN65) & Montreal (ICANN66) meetings. The community present was of the view that (IDN) ccPDP4, should be launched and focus should be on the (de-)selection of IDN ccTLD strings and management of variants of selected IDNccTLD strings and limited to the Items identified by the ccNSO Preliminary Review Team. Decisions 1. In accordance with Annex B section 1 of the ICANN Bylaws the ccNSO Council requests an Issue Report, which should address the following topics: a. Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de-)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. b. Whether or not to convene a Taskforce or use other method to address these issues. In addition, if the conclusion of the Issue Report is to initiate a ccNSO Policy Development Process, the ccNSO Council requests that the Issue Report include a proposed time line for conducting each of the stages of PDP outlined in Annex B of the ICANN Bylaws (PDP Time Line). 2. In preparing the Issue Report, and in proposing a time line for conducting each stage of ccPDP4 the Issue Manager should take into consideration and be guided by the following documents: - RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt ) - ISO 3166 standard (http://www.iso.org/iso/country_codes) - The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ) - The Fast Track Implementation Plan and related documents, latest version. - The draft policy for the selection IDN ccTLD strings ( September 2013) - The Final Report of the IDN policy preliminary review team ( June 2019) - The Board resolution on IDN (cc)TLD Variants (14 March 2019) (https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a) requesting the ccNSO to work on Variant Management - and any other matters and documents that the Issue Manager considers to be of relevance. 3. The ccNSO Council expects the Issue Report by its February 2020 meeting. 4. In accordance with Annex B section 2 of the ICANN Bylaws the ccNSO Council appoints Bart Boswinkel, VP Policy Support – ccNSO relations, as Issue Manager. 5. To establish a Council sub-committee to act as a steering group for the PDP, and to liaise with and assist the Issue Manager on behalf of the Council, up and until the Council decides whether or not to initiate ccPDP4. The sub-committee will have 6 members consisting of one (1) Councillor from each of ICANN geographic regions, including the chair of the ccNSO verseeing the policy and one (1) NomCom appointed Councilor. The initial members of the PDP Oversight Committee are: a. Katrina Sataki ( chair ccNSO, EU region) b. TBD (AF region) c. TBD (AP Region) d. TBD (LAC Region) e. TBD ( NA Region) f. TBD (NomCom appointed Councillor) 6. The secretariat is requested is publish this resolution as soon as possible. Request change Article 10 and Annex B ICANN Bylaws to include IDN ccTLD Managers in the ccNSO For discussion and confirmation by email vote. Draft letter was circulated, including the proposed amendments as foreseen in ccPDP2 Update ccNSO related ICANN Bylaw Change Repository For information: The Bylaw change repository has been updated to reflect adoption of the Fundamental Bylaw change re IFRT and amendment of Article 10 and Annex B of the ICANN Bylaw Results Council Workshop Montreal (ICANN66) & Implementation WS 2 and ccNSO Organizational Review recommendations & suggestions For information and discussion. Preparation Cancun meeting (ICANN67, 7-12 March 2020) Council Workshop Council meetings Tech Day & Members meeting Plenary sessions WG meetings Joint meeting with the Board (Topics for discussion) Joint meeting with GAC Update ECA & CSC ECA CSC. Updates Chair, Vice-Chairs and Councillors, Regional Organisations, secretariat. Updates WGs. GRC IGLC SOPC Meeting Program Committee TLD-OPS Auction Proceeds Update liaisons Update ALAC Liaison (written update) Update GNSO Liaison (written update) Next meetings 2020 proposed Council calls: January 23 – 18:00 UTC February 20 – 12:00 UTC (TBD) March @ICANN67 April 16 – 12:00 UTC May 21 – 18:00 UTC June @ICANN68 August 20 – 12:00 UTC September 17 – 18:00 UTC October @ICANN69 November 19 – 12:00 UTC December 17 – 18:00 UTC AOB Closure [1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-2…, general introduction page 4.

1 0

REMINDER: ccNSO Council Teleconference | 19 December at 18:00 UTC
by Kimberly Carlson Dec. 19, 2019

Dec. 19, 2019

Dear Councilors, As a reminder, the next ccNSO Council Teleconference will be this Thursday, 19 December at 18:00 UTC. Draft agenda and background material are attached (circulated by Bart last week). Call details: Join Zoom Meeting https://icann.zoom.us/j/388311562?pwd=SVc4YUJKcy9wQlFhUm51aU5ObW1IQT09 Wiki space: https://community.icann.org/x/Nwn_BQ (recording, transcript and background material will be posted as it becomes available) Meeting ID: 388 311 562 Password: 129744 **Please note this added security/privacy feature. Participants will only be required to enter the password if they are joining via the application and typing in the meeting ID manually. Anyone who joins a meeting via a link in a calendar or e-mail invitation will not be required to enter the password upon joining** Find your local number: https://zoom.us/u/aAAP6aGAx If you are unable to attend, please let Bart and I know as soon as possible. Thank you. Best, Kim

2 1