- Ccnso-council - lists.icann.org

Revised Schedule for Public Comment Period on Two Key ICANN Plans
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

Hello All, ICANN is notifying the community that the Public Comment period for the Draft FY21-FY25 Operating and Financial Plan and Draft FY21 Operating Plan and Budget has changed. Originally scheduled for Tuesday, 17 December 2019, drafts of the two plans will now be available beginning Friday, 20 December 2019. This date change may impact previously scheduled meetings intended for the Supporting Organizations and Advisory Committees to begin their review. ICANN org is prepared to provide those groups with the Table of Contents of the documents and other information that may be helpful prior to the release of the complete drafts. Please email planning(a)icann.org <https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_H…> to request. Information also will be published on the Finance community wiki page. In addition, the Public Comment period has been extended by 7 days to 58 days (excluding holidays) to give the community more time to review the documents. To learn more and ask questions during the Public Comment window, webinars will be held on: * 9 January 2020 at 01:00 UTC https://icann.zoom.us/j/935036343<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_J…> * 9 January 2020 at 16:00 UTC https://icann.zoom.us/j/506858960<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_d…> * 14 January 2020 at 16:00 UTC https://icann.zoom.us/j/257109807<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_U…> More details about how to join these webinars will be available in January. ICANN org staff is available to meet with individual community groups to answer questions and help increase understanding about the plans. Please email planning(a)icann.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_H…> to request a 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

Apply Now for ICANN and PTI Leadership Positions
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

Dear All, The Nominating Committee (NomCom) for the Internet Corporation for Assigned Names and Numbers (ICANN) invites interested individuals to submit applications for key leadership positions within ICANN and Public Technical Identifiers (PTI), an affiliate of ICANN organization. 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 February 2020 at 23:59 Universal Coordinated Time (UTC). Read more here: https://www.icann.org/news/announcement-2019-12-18-en? We are inviting applications for the following positions: * Two members of the ICANN Board of Directors. * One member of the PTI Board of Directors. * Two regional representatives to the At-Large Advisory Committee (ALAC) – one from the European region and one from the North American region. * One member 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. Qualifications Fluency in English is a requirement for all positions. Other qualifications, skills, and time commitments vary depending on the position. For information, visit the NomCom webpage [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_G…>. Application Deadline and Process Candidates must submit applications through the online candidate portal [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_B…>. For full consideration, the NomCom must receive applications by 18 February 2020, 23:59 UTC. There will be no grace period for candidates to complete their application forms through theonline candidate portal [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_B…>. Candidate applications that remain incomplete at the end of this period will not be considered. Candidates will receive an automated email from either no-reply(a)email.zenginehq.com<mailto:no-reply@email.zenginehq.com> or no-reply(a)webportalapp.com<mailto:no-reply@webportalapp.com> after creating an account. In addition, candidates can contact NomCom Staff Support at nomcom2020(a)icann.org [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_f…> if there are any questions. All applications are confidential. Selections are expected to be announced by August 2020. Successful candidates will assume their positions after ICANN's Annual General Meeting scheduled to be held during ICANN69, which runs from 17-22 October 2020. Meetings, Travel, Reimbursement, and Compensation These positions require regular participation in teleconferences and may involve significant international travel, including to ICANN's three annual Public Meetings. Meetings will be held in Hamburg, Germany (17-22 October 2020); Cancún, Mexico (20-25 March 2021); The Hague, Netherlands (14-17 June 2021); and Seattle, United States (23-28 October 2021). Reasonable direct and properly documented expenses incurred in the course of service will be reimbursed. Each ICANN Board member has the option to receive compensation in accordance with the resolution passed by the Board on 30 July 2014, but it is not required. (See Board Member Compensation [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_J…>.) For More Information Learn more by visiting the 2020 NomCom website [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_G…>. If you have any questions or comments, email nomcom2020(a)icann.org [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_f…>. Read more here: https://www.icann.org/news/announcement-2019-12-18-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

Third Accountability and Transparency Review Team (ATRT3) Draft Report
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

Hello everyone, Purpose: This Public Comment proceeding is on behalf of the third Accountability and Transparency Review Team (ATRT3), who seeks to solicit input on its draft report<https://www.icann.org/en/system/files/files/draft-report-atrt3-16dec19-en.p…>. The Accountability and Transparency Review is mandated by ICANN's Bylaws (Article 4, Section 4.6<https://www.icann.org/resources/pages/governance/bylaws-en/#article4.6>) to review "ICANN's execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community." Current Status: The report drafted by the ATRT3 contains key findings and draft suggestions and recommendations. The ATRT3 has not reached consensus on its suggestions and recommendations. It is seeking input from the community on the proposals included in the draft report. Next Steps: The ATRT3 will carefully consider comments received and amend the report as it deems appropriate and in the public interest before submitting its final report to the Board. The ATRT3 expects to submit its final report to the Board in March 2020. The final report will be published for Public Comment in advance of the Board's consideration. Read more here: https://www.icann.org/public-comments/atrt3-draft-report-2019-12-16-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

NextGen@ICANN program
by Joke Braeken Dec. 20, 2019

Dec. 20, 2019

Dear all, ICANN launched the application round for those interested in participating in the ICANN68 Public Meeting in Kuala Lumpur, Malaysia, through the NextGen@ICANN program. ICANN68 will take place from 22 June to 25 June 2020. The application round will remain open until 24 January 2020. Successful candidates will be announced on the ICANN website on 24 February 2020. For more information: https://newsalerts.icann.org/ZRN0g01zd000010Ms20PEC5 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

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