December 2019 - Ccnso-council

Resolution to Launch ccPDP 4
by Bart Boswinkel Jan. 15, 2020

Jan. 15, 2020

Dear all, Following yesterday’s (19 December 2019) Council call, you are kindly requested to agree to the launch of ccPDP4 by 15 January 2019, in particular if you want to abstain from voting or are against. In accordance with Annex B of the Bylaws to launch the ccPDP it is required you request an Issue Report and define the scope it should cover, set a date you expect the Issue Report and appoint the Issue Manager. Please note that the appointment of the Council oversight committee is not included in the draft resolution as the volunteers are not known yet. There will be a separate email on that topic. If you have any questions or comments, please send them to the list. Kind regards, Bart ------------------------------------- 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. The secretariat is requested is publish this resolution as soon as possible. [1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-2…, general introduction page 4.

11 10

Number Resource Organisation (NRO) and Address Supporting Organisation (ASO) and .org
by Stephen Deerhake ＠ ASNIC Dec. 31, 2019

Dec. 31, 2019

Greetings, Oscar Robles-Garay, Chair of the NRO Executive Council, via the Address Supporting Organisation as a Decisional Participant within the Empowered Community, recently submitted the following to John Jeffrey, the ICANN Corporate Secretary: ICANN Secretary, The 5 Regional Internet address Registries (RIRs) have participated in ICANN since its inception, collectively in the names of the NRO (Number Resource Organization) and the ASO (Address Supporting Organization). With the recent ASO Review, the NRO communities reaffirmed our relationship with ICANN as a critical component of the global Internet Governance ecosystem, and our participation in ICANN as a Decisional Participant in the Empowered Community. The NRO has reviewed recent events surrounding the proposal by ISOC to transfer the ownership of PIR, the .org Registry, to Ethos Capital. While we do not normally engage in policy matters related to the DNS, we consider ICANN’s handling of this proposal to be an important Internet governance decision, with bearing on the community’s trust in ICANN, and the legitimacy of the ICANN model. We have therefore agreed to issue an Inspection Request to ICANN (as follows), in the name of the ASO as a Decisional Participant in the Empowered Community. We believe that confirming the process that will be used for review of the assignment of the .org registry agreement, including the extent of public input into that process, will enhance the transparency of the decision making and strengthen public trust in ICANN. Request: “As a Decisional Participant in the Empowered Community and pursuant to ICANN Bylaws section 22.7, the ASO hereby submits this Inspection Request to inspect the records of ICANN, including minutes of the Board or any Board Committee, for the purpose of determining whether the ASO's may have need to use its empowered community powers in the near future relating to the potential assignment of the .org Registry Agreement. For this purpose, the ASO seeks to inspect any ICANN records which pertain to or provide relevant insight to the process by which ICANN will consider (and potentially approve) the assignment of the .org Registry Agreement, including the process by which input from the affected community will be obtained prior to ICANN’s consideration and potential approval of the assignment.” Best Regards, Oscar Robles-Garay Chair of the NRO EC (On behalf of the ASO as a Decisional Participant in the Empowered Community) So what does this mean? Basically, the ASO, as a Decisional Participant, has exercised their right under Section 22.7 of the ICANN Bylaws to request background information, consistent with the limitations present in Section 22, regarding Board and ICANN org correspondence, memoranda, etc., with respect to ICANN’s involvement with what is generally known as the “.org transfer”. No immediate action is required of the ccNSO Council at this time with regards to the action the ASO has taken as a Decisional Participant. The purpose of this email to you is strictly informational. You need to be aware of this action by a fellow Decisional Participant. Writing in a purely personal capacity, I offer a few observations. First, it’s apparent that via this action on the part of the NRO’s via their participation in the ASO, they are really NOT happy with recent developments with respect to .org. Second, I believe that what the NRO, via the ASO, has initiated is a major stress test of the ICANN Bylaws; I cannot predict that outcome… Third, I see no reason for the ccNSO (and especially the Council, lacking a consultative effort with the membership) to weigh in on this matter at this time. Best Regards, /Stephen

2 1

outcome selection process RSS GWG
by Joke Braeken Dec. 26, 2019

Dec. 26, 2019

Dear all, This is to inform you about the outcome of the Council Selection Process for the Root Server System Governance Working Group (RSS GWG), which closed Monday, 23 December 2019 (23:59 UTC). 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 In the table below (see also PDF in attachment), you will be able to find an overview of the ballot numbers, their date of receipt and the order of preference as listed by the individual council members. 11 councillors submitted their preference before the 23 December (23:59 UTC) deadline. Hiro Hotta abstained. BALLOT NUMBER RECEIVED ON 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 1 17 Dec 2 3 5 6 4 1 2 17 Dec 1 2 3 5 4 6 3 17 Dec 1 3 2 4 6 5 4 18 Dec 1 2 3 4 6 5 5 20 Dec 3 5 2 4 6 1 6 21 Dec 0 3 4 0 6 5 7 23 Dec 3 2 1 4 6 5 8 23 Dec 5 4 1 2 6 3 9 23 Dec 1 5 6 4 3 2 10 23 Dec 0 3 0 6 5 4 11 23 Dec 1 2 3 4 6 5 SUM 18 34 30 43 58 42 The ccNSO needs to appoint 2 members to the RSS GWG. The 2 candidates with the most supportive votes: * Peter Janssen (.eu) * Luis Diego Espinoza (.na) Next steps The 2 candidates receiving most supportive votes, are selected. The ccNSO Secretariat will inform relevant ICANN staff of the selection of the candidates, ahead of the 8 January 2020 deadline. Background * 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 At closure of the application window, 6 applications were received. After receipt of the applications, the application material documents were transmitted to the ccNSO Councillors. The Councillors selected and listed the candidates in order of preference and mailed them to the ccNSO Secretariat mailing list. The selection procedure closed on 23 December 2019 (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

2 1

EARLY DRAFT: ccNSO-related sessions at ICANN67 - Cancun
by Kimberly Carlson Dec. 23, 2019

Dec. 23, 2019

Dear all, In an effort to give you as much notice as possible, I would like to share the current draft of the ccNSO-related sessions in Cancún. Please keep in mind the schedule is tentative and subject to change, however the dates/times have been confirmed by leadership and the working group/committee chairs. NOTE: The Plenary sessions for Monday and Thursday, have been confirmed – however, the ICANN meeting planning team is still discussing whether there will be a session Wednesday morning. If you are interested in the CSC and/or IFRT sessions, please let me know and I will provide a draft of those sessions as well. If interested in presenting at Tech Day, please email the committee at: ccNSO-techday(a)icann.org<mailto:ccNSO-techday@icann.org> Day 1, Saturday, 7 March * Guidelines Review Committee – 1030-1200 (block 2) * Internet governance liaison committee – 1330-1500 (block 3) * PDP 3 (pdp-ret) – 1515-1830 (blocks 4, 5) Day 2, Sunday, 8 March * ccNSO Council Workshop – 900-1200 (blocks 1, 2) * ccNSO Council Preparatory session – 1215-1330 (lunch) * Tech Working Group – 1330-1500 (block 3) * SOPC – 1330-1645 (blocks 3, 4) * TLD OPS Standing Committee 1515-1645 (block 4) * Joint session: ALAC and ccNSO – 1700-1800 (block 5) Day 3, Monday, 9 March * Welcome Ceremony * Tech Day – 1030-1830 (blocks 2, 3, 4 and 5) * Joint session: ccNSO and GNSO 1215-1330 – (lunch) * Public Forum 1 - 1515-1645 * Plenary session #1: The Domain Name Services Marketplace - Market Dynamics, Business Models and Commercial Drivers * Gala night – TBD Day 4, Tuesday, 10 March * Members meeting – 900- * Joint session: ICANN Board and ccNSO – 1100-1200 * Joint session: ccNSO and GAC – time has NOT been confirmed * ccNSO Networking Event – Save the date along with additional details will be sent in January Day 5, Wednesday, 11 March * Members meeting – 900 * Plenary session: TBD * DNSSEC Workshop – 900-1200 * ccNSO Council Face to Face meeting – 1700-1830 (block 5) Day 6, Thursday, 12 March * Plenary session: The DNS and the IoT: Opportunities, Risks, and Challenges * PDP 4 (RM) – 1030-1200 (block 2) * MPC – 1330-1500 (block 3) * Q&A with ICANN Org execs – 1445-1545 * Public Forum 2 – 1600-1730 * Public Board Meeting – 1730-1830 All sessions are open and observers are welcome (unless otherwise noted). If you are not planning on being in Cancún, remote participation will be available and you are encouraged to attend. I will send out details as they become available, or you are welcome to reach out to me directly. Calendar notices will be sent to individual working group/committee members. Please visit our meeting Wiki for additional information: https://community.icann.org/x/bwBxBw (I will update this page as information becomes available and/or confirmed) ICANN67 Meeting page: https://meetings.icann.org/en/cancun67 If you have any questions, comments or concerns please do not hesitate contacting me. Best regards, Kim Carlson

3 2

Volunteers oversight Issue report drafting (ccPDP4)
by Bart Boswinkel Dec. 23, 2019

Dec. 23, 2019

Dear all, Following yesterday’s calls, and assuming the Council agrees to the oversight committee, please put your name forward. Suggest we do this on a first come first serve basis. Its role will be limited. The committee will be asked to oversee the schedule up and until the Issue report has been adopted, and may be asked to review the draft issue report before it is send to Council. Depending on the timing and if deemed relevant and appropriate, Councillors may also be asked to present at meetings of the Regional Organisations. For the oversight committee we are looking for one member from the AF, AP, LAC and NA region and one of the NomCom members. As Katrina is already member and from EU, no member is sought from EU. By 2 January I will send out a follow-up email to seek formal approval of the committee by 15 January. Kind regards, Bart

3 2

January: ccNSO Council Teleconference | January 23, 2020 at 18:00 UTC
by Kimberly Carlson Dec. 23, 2019

Dec. 23, 2019

Dear all, The next ccNSO Council Teleconference will be January 9, 2020 at 18:00 UTC. An agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/438404161 Meeting ID: 438 404 161 Find your local number: https://icann.zoom.us/u/aAAP6aGAx Wiki page: https://community.icann.org/x/IghxBw (recording, transcript and background material will be posted as it becomes available)

1 0

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