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

Decision needed: Adoption of 2019-2021 Work Plan
by Bart Boswinkel May 3, 2019

May 3, 2019

Dear all, Per the discussion on the last Council call, the secretariat would circulate the “annual” work plan for adoption by email. Draft Resolution The ccNSO Council adopts the annual work plan as reflected in the ccNSO Activities Portfolio 2019-2021. The secretariat is requested to publish the relevant documents and inform the community accordingly. The secretariat is further requested to provide the monthly work plan as soon as feasible following adoption of the annual work plan and in accordance with the relevant ccNSO Guideline. If you have any questions or comments, or you want to express your support, please do so by 6 May 2019, 17.00 UTC Kind regards, Bart Documentation The ccNSO Activities Portfolio 2019-2021 includes the following documents: High level overview ccNSO Activities 2019-2021 Mindmap Overview ccNSO Activities 2019-2021 GANTT chart Overview ccNSO Activities 2019-2021 Description Relevant Guideline: https://ccnso.icann.org/about/guidelines-work-plan-30mar16-en.pdf

2 1

May ccNSO Council call | 23 May @18:00 UTC
by Kimberly Carlson April 30, 2019

April 30, 2019

The next ccNSO Council meeting is scheduled for 23 May at 18:00 UTC. Please find the call details below: Topic: ccNSO Council Call Time: May 23, 2019 6:00 PM Universal Time UTC Join Zoom Meeting https://icann.zoom.us/j/519171677 Wiki: https://community.icann.org/x/Kwn_BQ (agenda, documents and recordings will be posted here as they become available) Meeting ID: 519 171 677 Find your local number: https://zoom.us/u/aAAP6aGAx

1 0

May ccNSO Council call | 23 May @18:00 UTC
by Kimberly Carlson April 30, 2019

April 30, 2019

The next ccNSO Council meeting is scheduled for 23 May at 18:00 UTC. Please find the call details below: Topic: ccNSO Council Call Time: May 23, 2019 6:00 PM Universal Time UTC Join Zoom Meeting https://icann.zoom.us/j/519171677 Wiki: https://community.icann.org/x/Kwn_BQ (agenda, documents and recordings will be posted here as they become available) Meeting ID: 519 171 677 Find your local number: https://zoom.us/u/aAAP6aGAx

1 0

Reminder: Volunteers needed for IRP IOT
by Joke Braeken April 30, 2019

April 30, 2019

Dear All, This is a reminder that ICANN seeks volunteers to re-compose the Independent Review Process (IRP) Implementation Oversight Team (IOT), which will develop published Supplemental Procedures for ICANN’s Independent Review Process. The work of the IRP IOT is important to ICANN’s accountability and sets many procedures around how IRPs are administered. Last October, the IRP IOT produced an interim set of Supplemental Procedures that were adopted by the ICANN Board during ICANN63, and now a final set of Supplemental Procedures is needed. The goal of this team is to reach a final set of Supplemental Procedures that reflects input from across the ICANN community, which prompts this request for additional volunteers to join. Under the ICANN Bylaws, ICANN is required to consult with the SOs and ACs regarding the establishment of the IRP IOT. How to apply? Kindly contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Background ICANN operates a separate process for independent third-party review of Disputes – the Independent Review Process (IRP). The International Centre for Dispute Resolution (ICDR) currently administers ICANN's Independent Review Processes. ICANN IRPs are governed by the ICDR's International Dispute Resolution Procedures as modified by Supplementary Procedures for ICANN's IRP. The CCWG-Accountability Work Stream 1 (WS1) in its final report included the following under Implementation for Recommendation 7 concerning the IRP: "The CCWG-Accountability proposes that the revised IRP provisions be adopted as Fundamental Bylaws. Implementation of these enhancements will necessarily require additional detailed work. Detailed rules for the implementation of the IRP (such as rules of procedure) are to be created by the ICANN community through a CCWG (assisted by counsel, appropriate experts, and the Standing Panel when confirmed), and approved by the Board, such approval not to be unreasonably withheld." This part of the recommendations on IRP is included in the following section of the new ICANN Bylaws which took effect on 27 May 2016: "(n) Rules of Procedure (i) An IRP Implementation Oversight Team shall be established in consultation with the Supporting Organizations and Advisory Committees and comprised of members of the global Internet community. The IRP Implementation Oversight Team, and once the Standing Panel is established the IRP Implementation Oversight Team in consultation with the Standing Panel, shall develop clear published rules for the IRP ("Rules of Procedure") that conform with international arbitration norms and are streamlined, easy to understand and apply fairly to all parties. Upon request, the IRP Implementation Oversight Team shall have assistance of counsel and other appropriate experts. (ii) The Rules of Procedure shall be informed by international arbitration norms and consistent with the Purposes of the IRP. Specialized Rules of Procedure may be designed for reviews of PTI service complaints that are asserted by direct customers of the IANAnaming functions and are not resolved through mediation. The Rules of Procedure shall be published and subject to a period of public comment that complies with the designated practice for public comment periods within ICANN, and take effect upon approval by the Board, such approval not to be unreasonably withheld." In early in 2016 the CCWG-Accountability created the IRP IOT which has been working on updating the Supplementary Rules of Procedures. It is important to note that the IRP IOT was included as part of WS2 for administrative simplicity but is in fact independent of WS2. Relevant Resources * ICANN BYLAWS - https://www.icann.org/resources/pages/governance/bylaws-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * CCWG-Accountability Work Stream 1 – Final recommendations – Recommendation #7 https://community.icann.org/pages/viewpage.action?pageId=58723827&preview=/… * November 2016 Public consultation on the Updated Supplementary Rules - https://www.icann.org/public-comments/irp-supp-procedures-2016-11-28-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> * 2018 consultation on the interim set of Supplemental Procedures that were adopted by the ICANN Board during ICANN63 https://www.icann.org/public-comments/irp-iot-recs-2018-06-22-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> * IOT wiki - https://community.icann.org/display/WEIA/WP-IOT+-+IRP+Implementation+Oversi… 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

FW: [ICANN Community Leaders] 29 April Update
by Katrina Sataki April 29, 2019

April 29, 2019

FYI From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces@icann.org] On Behalf Of ICANN Community Leadership Digest Sent: Monday, April 29, 2019 5:00 PM To: so-ac-sg-cleaders(a)icann.org Subject: [ICANN Community Leaders] 29 April Update <http://r20.rs6.net/on.jsp?ca=a16a33f6-c025-4995-9a26-59c1331a7d9a&a=1122025…> Monday, 29 April 2019 ICANN Community Leadership Digest <https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…> This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. Due to a scheduling error, the 25 April 2019 issue was not distributed. Apologies. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> TABLE OF CONTENTS Requests * REMINDER: Input to Establish IRP Standing Panel Information Sharing * NEW: Evolving ICANN's Multistakeholder Model * NEW: CSC Findings on PTI Performance (March 2019) * LOOKING AHEAD: ICANN66 Travel Support Timeline ICANN65 Planning * COMING UP: CROP Deadline for ICANN65 * REMINDER: ICANN65 Travel Support Deadlines * THIS WEEK: Publication Support for ICANN65 * SAVE THE DATE: ICANN65 Community Leadership Reception * REMINDER: Meet with the ATRT3 Team at ICANN65 Public Comment * Proposal for Hebrew Script Root Zone Label Generation Rules * Proposed Renewal of .info Registry Agreement * Proposed Renewal of .org Registry Agreement * Proposed Renewal of .asia Registry Agreement * Proposed Renewal of .biz Registry Agreement * Evolving ICANN's Multistakeholder Model * Label Generation Rules for the Root Zone Version 3 (RZ-LGR-3) Requests REMINDER: Input to Establish IRP Standing Panel Executive: John Jeffrey, General Counsel and Secretary FOR: All SO/AC Chairs REQUEST ICANN organization needs input on the open questions regarding how the Supporting Organizations (SOs) and Advisory Committees (ACs) will coordinate their participation in the process for the selection of a standing panel to preside over ICANN’s Independent Review Process (IRP) proceedings. The questions identified here need to be resolved in order to move forward with the work on establishing a standing panel. ACTION Please send your input on the open questions to the public email list: < <mailto:irp-standing-panel@icann.org> i <mailto:irp-standing-panel@icann.org> rp-standing-panel(a)icann.org>. For more information, please contact Liz Le at < <mailto:elizabeth.le@icann.org> elizabeth.le(a)icann.org>. BACKGROUND The IRP is an accountability mechanism provided by the ICANN Bylaws that allows for third-party review of actions (or inactions) by the ICANN Board or staff that are allegedly in violation of the Bylaws or Articles of Incorporation. The Bylaws provide that an omnibus standing panel shall be established from which panelists shall be selected to preside over specific IRP disputes. The ICANN Bylaws specify that ICANN shall, in consultation with the SOs and ACs, establish the standing panel. The Bylaws requires ICANN, in consultation with the SOs and ACs, to pursue a four-step process to establish the standing panel. As part of the process, the SOs and ACs must collectively agree on one slate of candidates for the standing panel to be submitted to the ICANN Board for approval. Information Sharing NEW: Evolving ICANN's Multistakeholder Model Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING Following up on the 14 March 2019 session at ICANN64 on how ICANN can evolve its multistakeholder model, a <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> public comment proceeding on the topic opened on 25 April 2019 and will close 4 June 2019. A webinar will be held the week of 13 May 2019 to continue the conversation with the community and to encourage public comment. More details on the webinar will follow soon. Brian Cute will lead the conversation to develop and prioritize a list of issues that are hampering the multistakeholder model from being more effective and efficient. When the public comment proceeding closes, the Issues List will be updated based on comments received. A second webinar will be scheduled prior to ICANN65 in June 2019 to review the Issues List and discuss the work plan to be developed by the end of 2019. BACKGROUND This current Issues List combines community inputs from ICANN63 where the ICANN Board, Advisory Committees, and Supporting Organizations discussed Strategic Objective #2 as well as community inputs from a facilitated session at ICANN64. At ICANN64 the community was invited to add specificity to the issues identified at ICANN63, to offer new issues that are hampering the effectiveness of ICANN's multistakeholder model and to offer reasons why an issue should be removed from the Issues List. The Issues List, updated with community inputs from ICANN64, is the focus of this public comment proceeding. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> NEW: CSC Findings on PTI Performance (March 2019) From: Byron Holland, Customer Standing Committee (CSC) Chair FOR: All Community Leaders INFORMATION SHARING I am pleased to inform you the CSC has concluded that Public Technical Identifier overall performance over March 2019 was “Satisfactory." PTI met the service level agreement at 98.4% for the month of March 2019. The single missed service level is subject to a CSC recommendation to be adjusted. The adjustment would recategorize this month's performance for this metric as 'met'. The related PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> https://www.iana.org/performance/ <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> csc <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> -reports. I am also very pleased to inform you that the CSC and PTI made considerable progress in changing the Service Level Agreements identified in our Findings report. We will keep you informed. BACKGROUND Generally, the CSC regular meeting is scheduled at or around the 15th every month, and the CSCFindings report on the PTI performance is sent out shortly after that meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> h <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> ttps://mm.icann.org/mailman/listinfo/ <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> csc <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> -announce. Any comments on our reporting to you is welcome. The CSC became effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found at https://www.icann.org/csc. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> LOOKING AHEAD: ICANN66 Travel Support Timeline Executive: Sally Costerton, Senior Advisor to the President and CEO; Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING All travel support requests are now due 120 days prior to the next ICANN Public Meeting. This was previously a 90-day deadline. Therefore, the deadline for ICANN66 travel support is Friday, 5 July 2019. If applicable, community groups will need to adjust their election timelines accordingly to ensure new leaders are eligible in time for the ICAN66 travel support deadline. ICANN65 Planning COMING UP: CROP Deadline for ICANN65 Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The Community Regional Outreach Program (CROP) for FY19 will end on 30 June 2019. For groups planning to use CROP funds to conduct outreach during ICANN65, requests must be submitted no later than Monday, 6 May 2019. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: * Trip requests must be approved by your respective community leadership team. * For FY19, the trip request must be filled in by the CROP participant (you) via the CROP Wiki space. * In order to access the Wiki space, you must first have an account; please let your CROP Coordinator know if you need an account. * All individuals requesting CROP funding must also review the CROP Guidelines prior to submitting a request: <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> https://community.icann.org/x/yicFBQ. Please contact < <mailto:crop-staff@icann.org> crop-staff(a)icann.org> with any questions. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> REMINDER: ICANN65 Travel Support Deadlines Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Friday, 10 May 2018 is the cut-off date to replace supported travelers. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> THIS WEEK: Publication Support for ICANN65 Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Translation Deadline If your ICANN65 publication requires translation, please provide the final material(s) by Friday, 3 May. This ensures that there is enough time to translate the publication by the print deadline. Print-Only Deadline If you only need your ICANN65 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 17 May. Please work directly with your support staff to submit these requests. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> SAVE THE DATE: ICANN65 Community Leadership Reception Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Save the date for the ICANN65 Community Leadership Reception with members of the ICANN Board and Executive Team on Sunday, 23 June 2019, 18:00-20:00 CET in Marrakech, Morocco. Details will be confirmed as the date approaches. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> REMINDER: Meet with the ATRT3 Team Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All SO/AC Chairs INFORMATION SHARING The third Accountability and Transparency Review Team (ATRT3) will meet in Marrakech to advance its work. As some of the team will be in Marrakech we would like to ask for a 30 to 40-minute slot on your community group's agenda, if possible. Community input is key to the success of this process. If you are able to accommodate us on your agenda, please send us an email to <atrt3-coordination(a)icann.org <mailto:atrt3-coordination@icann.org> > to let us know a day and time that would suit. We will send you a preliminary set of questions ahead of the meeting to aid the discussion. We also welcome any questions you wish to raise in advance. Our goal for Marrakech is to: - Socialize our terms of reference and scope; - Conduct investigation of identified objectives - Seek input from the community to help us shape our findings and draft recommendations. BACKGROUND The ATRT review is mandated by ICANN Bylaws Section 4.6 (b) to examine 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. Prior to meeting in Marrakech, the review team met on 3-5 April in Los Angeles for its first substantive meeting to develop our terms of reference and workplan, in response to the Board Resolution (2018.10.25.15) requesting that “ATRT3 adopt its Terms of Reference and Work Plan within 60 days of convening its first meeting, and submit these documents to the Board and to the leadership of the Supporting Organizations and the Advisory Committees, to confirm that the team's scope and timeline are consistent with the requirements of the ICANN Bylaws and ICANN community expectations.” We look forward to hearing from you. Many thanks and best regards, Cheryl Langdon-Orr and Pat Kane, ATRT3 Co-Chairs Public Comment <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> Proposed Renewal of .info Registry Agreement Close Date: Monday, 29 April 2019 <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> Proposed Renewal of .org Registry Agreement Close Date: Monday, 29 April 2019 <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> Proposed Renewal of .asia Registry Agreement Close Date: Tuesday, 7 May 2019 <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> Proposed Renewal of .biz Registry Agreement Close Date: Tuesday, 14 May 2019 <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> Evolving ICANN's Multistakeholder Model Close Date: Tuesday, 4 June 2019 <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> Label Generation Rules for the Root Zone Version 3 (RZ-LGR-3) Close Date: Tuesday, 4 June 2019 Volume 1, Issue 14 | <http://r20.rs6.net/tn.jsp?f=001Aah1MVJDv5EWHUMkT9fTNyPBfdquKJXmeUZ9KIZLQbsw…> Archive | Next Issue: Thursday, 2 May 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Unsubscribe so-ac-sg-cleaders(a)icann.org <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile | <http://www.constantcontact.com/legal/service-provider?cc=about-service-prov…> About our service provider Sent by <mailto:david.olive@icann.org> david.olive(a)icann.org in collaboration with <http://www.constantcontact.com/index.jsp?cc=nge> <http://www.constantcontact.com/index.jsp?cc=nge> Try it free today

1 0

Call for volunteers: IDN Preliminary Review Team (IDN PRT)
by Joke Braeken April 29, 2019

April 29, 2019

Dear all, The ccNSO Secretariat is launching a call for volunteers for membership of the IDN Preliminary Review Team (IDN PRT). The call for volunteers will be open from today 29 April 2019 and will close: Monday, 13 May 2019 (23:59 UTC). Further background details, including the scope and goals of the IDN, the time commitment and qualification requirements etc, are included below. How to apply? If interested, please send the following documents to: joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> no later than Monday, 13 May 2019 (23:59 UTC). * Your resume, curriculum vitae, or biography. * If applicable, a letter of support from your employer in respect to the required time commitment to participate actively in the IDN PRT Next steps Once we have received your intent to volunteer as IDN PRT member, the ccNSO Secretariat will send you a link to an online Acknowledgement of Terms Form. Via this form, you consent to ICANN processing data in order to add you as a member of the CSC and its mailing list(s). The form explains the information ICANN will process to administer your participation in the IDN PRT and how the information will be used for this purpose. It also describes the rights you have regarding your information. After receiving your application, the documents will be transmitted to the ccNSO Council who will appoint the members to the IDN PRT. Qualification Requirements Membership The PRT is open to : * representatives of all ccTLD Managers (either ASCII or IDN) can join as members of the IDN PRT. There is no requirement for a ccTLD to be a member of the ccNSO. * participants from other stakeholder groups, such as the Regional Organisations as defined in Section 10.5 of the ICANN Bylaws, GAC, GNSO, SSAC. Participants shall not be considered members of the PRT. Participants are entitled to participate on equal footing with members, unless the Terms of Reference state otherwise. * observers * experts from ICANN Org and PTI. Experts shall not be considered members but are entitled to participate on an equal footing The PRT should have at least 5 members, who are representatives from ccTLD managers. The members of the PRT shall nominate a Chair, who will be appointed by the ccNSO Council. The Chair should be a member of the PRT. Further details about the role of the chair are included in the Terms of Reference (see Links-section under “Background” below). Qualification Members, participants, and experts commit to participate actively and regularly in the work and are expected to have at least a basic understanding of the reference material (see below) Time commitment The IDN PRT is expected to report to the ccNSO Council by mid-July 2019, hence the DN PRT members and liaisons should be able to participate in weekly calls/meetings. The meetings will rotate from a timing perspective to share the burden as the membership may be distributed over different time zones. Outside of the weekly meetings, members and participants may also be asked to participate in other processes such as: * Provide an update to community at ICANN65 * Provide updates to any group/constituency regarding the IDN PRT at their request. * The IDN PRT is expected to perform the majority of its work telephonically and via email. Background Scope and Goals of the IDN PRT The intent of the preliminary review of the ccNSO Recommendation to resolve policy issues pertaining to the selection of IDN country code Top Level Domains strings (IDN ccTLD strings) and the inclusion of IDN ccTLD managers in the ccNSO is to identify issues and advise Council on: * Whether additional work needs to be done on the proposed Bylaw changes included in the ccNSO Recommendation to resolve policy issues pertaining to the selection of IDN country code Top Level Domains strings (IDN ccTLD strings) and the inclusion of IDN ccTLD managers in the ccNSO, and way forward to include IDN ccTLD managers in the ccNSO, based on the 2013 Policy recommendations as soon as possible. * Scope delineation and mechanism proposals to review and - when considered necessary - update the 2013 Policy Recommendations, taking into account the evolution of the Fast track Process, and other areas pertaining to the introduction and following the introduction of IDN ccTLDs strings which require a recommended policy, for example variant management and retirement of IDN ccTLDs. The mechanisms could consist of an advice to re-launch the PDP or to start a new PDP on the selection of IDN ccTLD strings, taking into account the work done to date. * Possible mechanisms to cooperate and/or coordinate efforts to harmonize the development processes, procedures and/or criteria pertaining to the selection of (IDN cc)TLD strings The Review Team should not propose solutions to the issues they have identified, nor propose updates or substantial changes to either: the Fast Track Process, the ccNSO Recommendation to resolve policy issues pertaining to the selection of IDN country code Top Level Domains strings (IDN ccTLD strings) and the inclusion of IDN ccTLD managers in the ccNSO, or other policy or policy related documentation. If, in the process of the review, the Review Team becomes aware of issues that are out of scope of the Preliminary Review but considered relevant for the future work in this or other areas pertaining to IDN ccTLDs, it will inform the ccNSO accordingly. To achieve its goal the PRT is expected to: * Conduct a review of the relevant documentation referenced in Section 6 of these Terms of Reference, and other material considered relevant by the PRT. * Prepare a consultation document seeking wider community input. * Conduct a public session at ICANN65 (June 2019) that is intended to inform the community on progress and provide an opportunity to give feed-back and input to the process. * Produce an Advice to the ccNSO Council, which includes its findings and proposed mechanisms and next steps. Links * The ccNSO Recommendation to resolve policy issues pertaining to the selection of IDN country code Top Level Domains strings (IDN ccTLD strings) and the inclusion of IDN ccTLD managers in the ccNSO (https://ccnso.icann.org/en/announcements/announcement-26sep13-en.htm) * IDN Fast Track Implementation Plan and related Guidelines (https://www.icann.org/resources/pages/fast-track-2012-02-25-en) * ccNSO Council Statements, Letters and related material: * https://ccnso.icann.org/en/about/sataki-et-al-to-namazi-28feb19-en.pdf * https://ccnso.icann.org/en/about/council-statement-new-gtld-subsequent-proc… * Relevant ICANN Board Resolutions and related material: * Recommendations for Managing the IDN variant TLDs (https://www.icann.org/resources/board-material/resolutions-2019-03-14-en#2.a) * Terms of Reference (see attachment) 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

Decision needed: Approval Terms of Reference
by Bart Boswinkel April 26, 2019

April 26, 2019

Dear all, As proposed on the 18 April 2019 Council call included for adoption the Terms of Reference for the Review Team, which is to conduct a Preliminary review of the IDN ccTLD recommended policy. Please note that after re-reading the text section 5.2 sub 1 has been slightly changed: it now reads Conduct a review of the relevant documentation referenced in Section 6 of these Terms of Reference, and other material considered relevant by the PRT. The marked text has been added to ensure that the Review team can take all documentation it deems relevant into account. Please let us know your vote, in particular whether you object or abstain from taken a decision by 26 April 2019, 17.00 UTC. Thank you, and kind regards, Bart Boswinkel

10 15

NOTES | ccNSO Council | 18 April 2019 @12 UTC
by Joke Braeken April 18, 2019

April 18, 2019

Hello all, Below please find the high-level notes and preliminary action items as noted from today’s ccNSO Council meeting. (18 April 2019 | 12 UTC) Link to the google document: https://docs.google.com/document/d/1FTn9Vl8TeVoLw-OjJF0CldiasJqSq7VdtWUTe-m… 1. Welcome and roll call Apologies from Abdalla, Margarita, Giovanni We are quorate: at least half of all councillors, and at least 1 councillor per region needed. Welcome to the newcomers. Feedback from ICANN64? Bar stools were a good idea mentioned Stephen in the chat. This time we used a separate room for the ccNSO council meeting. Alejandra and Katrina liked this. Jordan agreed, Laura and Biyi too. Let’s try to have a u-shaped table again in Marrakech. 2. Action Items Majority is completed, still 1 ongoing. We are waiting for the risk mitigation approach being adopted by the Board. Hopefully before ICANN65 3. Intermeeting decisions (since 14 February) · Letter to Board on IFRT · Members to IGLC appointed · Approved membership from .la · Drafted email to ICANN CEO not to use blog posts to initiate calls to action. His response forwarded to council mailing list. Other communities also supported this. Deadline for comments 15 May. No public comment round launched yet. Difference between public comments and public consultation. 4. Next Steps IFRT 3 members were appointed, among them 1 interim-member. All of them ccNSO member representatives. But, the bylaws require 1 non-member. Trang suggested we needed other organisations not to object to us moving forward with those 3 representatives. There are rumours one group is not happy with this. Some individuals from different parts of the community approached Katrina, support from non ccNSO-members. None of them stepped forward during the original call for volunteers. Their candidacy cannot be evaluated without evaluating all others again as well. All 3 reps must be from different ICANN regions. If a non-ccNSO member candidate is from a region, where we already have a member, we have an issue. Ifwe want to do it in a transparent way, and select the best candidate, we need to have another call for volunteers, for all interested, not just for non-ccNSO member candidates. Even if we go via a fast-track change of the bylaws, it is not sure that we can go forward with our current selection. Preferred option for Katrina: We go with the current selection under the current bylaws. However, then we need the other appointing organisations not to object. No clear response yet. Byron: the process requires a formal objection by another community, correct? Katrina: unchartered territory. There is no process. But indeed, that was what Trang suggested. No formal objections received yet, and no green light either. Byron: Trang speaks for ICANN, we need to assume this is correct. Catch 22. There is no objection, let’s move forward until there is a time when there is a formal objection 3 options: 1. Another call for volunteers, to get a third non-ccNSO member representative. But, would be the third call 2. To wait for the bylaw changes. But, even then we need another call for volunteers 3. Unless there is a formal objection by an appointing organisation, we move forward with the current set up. Action item #1: Next steps IFRT: council supports the 3rd option: To be presented to ICANN org. 5. ccNSO Co-chair GNSO Subsequent procedures WT5 Annebeth Lange retires from .no Full support from NORID for Annebeth to continue in her role as ccNSO appointed co-chair to WT5. Council supports this too. Action item #2: Katrina will write Annebeth and thank her for her availability to continue as ccNSO appointed co-chair to WT5. Thanks to NORID for their support to Annebeth, allowing her to continue and complete her work on WT5. 6. Membership application. ccTLD Manager for .tc was contacted: apparently their membership application was not submitted by the official representatives of this ccTLD manager. What to do when there are doubts whether the ccTLD manager submitted the application? What happens when there is a transfer of the ccTLD from one entity to the other: do we approach the new member? What happens if the ccTLD retires? What happens in that case to the ccNSO membership? End the membership of the previous ccTLD Manager? These issues require some further discussion, and clear guidance on these matters is needed. Souleymane advices .tc do correct the data in the IANA database. Katrina: We cannot proceed with the application. Needs to be dismissed. 7. Next steps Road Map review and update IDN overall policy Terms of Reference were shared on the mailing list. We are getting ready for the next steps regarding the roadmap council decision from Kobe. What we need to understand is what needs to be done with the current policy. Adjusted? Preliminary review, high-level, of the documents that are currently relevant. In order to do this, we need to set up a preliminary review team. To deliminate the review that needs to be undertaken. As a triage exercise. Intense schedule leading up to Marrakech, 1 call per week, to inform the council and the community asap on the next steps. We are awaiting a response on the risk mitigation, focus on IDN policy, replacing fast track is a high priority. Council needs to adopt the ToR. Via email vote. Ending next week. Once the document has been adopted, we can launch the call for volunteers. We need to reach out to the current IDN ccTLDs, and some of the usual members. Intense, but short-lived review team.Providing a sound basis for the next steps. Call for volunteers: Giovanni already mentioned his availability on mailing list. Ajay did the same in the council meeting chat Action item #3: Council to adopt the ToR via an online vote. Deadline: 26 April 2019, 23:59 UTC. Once the ToR have been adopted, the Secretariat will issue a call for volunteers. 8. Approval Travel Funding Guideline First revision submitted to council 1 year ago. Comments by Nigel. GRC re-worked the document almost completely. Shared with Council some time ago. No objections. Also sent to ccNSO community: some minor comments received, language tweaks. Updated travel funding guideline. Criteria introduced in this guideline are used for some time already by Travel Fund Committee. Positive feedback from the committee, on these criteria. Council adopts the guideline Move? Alejandra. Stephen seconded. Against? None Abstain? None Action item #4: Secretariat publishes the adopted travel funding guideline asap. After 7 days, the guideline comes into force 9. Annual Work plan ccNSO a/ Mind-map High-level categories where the activities are clustered. · ICANN-related activities: SOPC, GRC, UA · Policy and policy-related work: ccPDP3, IDN ccTLD policy update, emoji SG recommendations (closes at Marrakech meeting) · ccTLD community: ccNSO Members Meeting, Tech Day, TLD OPS, IGLC b/ GANTT chart, based on listed activities. Gives a good overview of the high-level activities and clusters just described. Until 2021. c/ Full description of the different activities. To understand the abbreviations used in the previous 2 documents. Bart proposed Council to adopt the annual work plan by email over the next week or 2. Pablo, Young-eum, Jordan and Laura expressed their appreciation of the mind map. Stephen mentioned there are many things to do. Action item #5: Bart will circulate an email to council by the end of next week, to ask for online adoption of the 3 aforementioned documents related to the annual ccNSO work plan 10. Approval roles and responsibilities Councillors Thanks to those that stepped forward. Final version of the table was shared with the council mailing list. Move? Stephen, seconded by Alejandra Against? None Abstain? None All in favour. Resolution approved 11. PDP3 Part 1 Retirement – Update Discussion on mailing list since the meeting last week. Good progress on the language. The group is rather large, 25 members plus experts and observers. Unequal level of engagement among members. Chair started reaching out to non-active members. 2 members are also Board members. (Danko, Nigel) Both expressed being comfortable in being a WG member and at the same time being a Board member. If there is an issue, this becomes an issue for the Board itself (abstain voting?) or ICANN’s legal council. Board operates on consensus. Another SO member approached us to participate. Still no GAC participation. Meeting face to face in Marrakech on Monday morning, calls every 2 weeks. 12. Agenda Marrakesh Alejandra presents the draft block schedule. Policy forum is a short meeting. Day 1: Monday, 24 June. Council prep, WG meetings, Tech Day, DNSSEC lunch Several HIT/CC sessions : afternoon of each day. No news yet regarding the community forum. Members meeting on Tue & Wed. Afternoon: unsure at the moment. Planning call with all SO/AC leaders next week. Hopefully more clarity yet. ccNSO cocktail on Tue: to be confirmed, depending on whether there are sufficient sponsors. Joint meeting with GNSO councils during the networking hour. HIT/CC: if the topic does not have any relevance to ccTDS, we might be able to schedule something against the HIT/CC that is of interest to the ccNSO. Discussion that 7 blocks for HIT/CC might be too much. Most likely on Wednesday afternoon there will be no HIT/CC, conflict with GAC communique drafting. Thursday: further WG meetings. No joint meeting between ccNSO and ALAC at ICANN65. Draft members meeting. Input from the ICANN64 session on how to shape policy forums, and based on results from the satisfaction survey. ccNSO cocktail, several 1000 dollars short. Not enough funding at the moment. Probably we will not get sufficient support. Option1: get something for the amount we have? Option2: cancel the ccNSO cocktail No support for cancelling. 13. Update CSC, RZERC, ECA · CSC met last week. Performance of PTI for March was satisfactory. One metric to be updated shortly. CSC is working closely with PTI on changing some SLAs, to align them more with current practices. One on technical checks, trivial change to SLA. Second one is related to LGI and IDN tables, needs to go through public consultation and required council approval. Third one is specific to ccTLD community: related to transfer of ccTLDs. Process will start later on, presented to community at ICANN65. · RZERC, no updates · No ECA updates. Board nomination member couple of weeks ago. 14. Update ccNSO Review Public consultation on the assessment report. Webinar was conducted yesterday. 15. Updates chair, vice-chairs and Councillors, Regional Organisations, secretariat. 16. Updates WG. a. GRC Katrina mentioned Special IFR. needs to be coordinated with the GNSO Council. They started looking into this. One of the topics for our bilateral meeting in Marrakech. Not entirely clear from bylaws who initiates the special IFR. Normal IFR is initiated by the Board. More questions than answers at the moment b. IGLC (progress to date) Secretariat is setting up first call. In prep of that call, we will have a meeting with ICANN org staff from global and government engagement. They want to understand what this group is doing, and liaise with them. The board committee on IG has also shown interest on this group. We need a chair for this group. Assessment report of ccNSO Review commented that it is not clear how chairs are being selected. WG typically nominates a chair, and then Council appoints the chair. c. SOPC d. Members Programme Committee e. Emoji Study Group 17. Updates liaisons a. Update ALAC Liaison (written update) b. Update GNSO Liaison (written update) 18. Next meetings · May 23rd · June – Marrakech (24-27 June) · July/August – 22 August · September 19 · October 17th · November -Montreal (2-7 November) · December 19th 19. AOB 20. Closure Thank you all. Bye! 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

MPC update - draft agenda ICANN 65
by Alejandra Reynoso April 18, 2019

April 18, 2019

Dear All Please find in attachment the documents shared today in our call. Best regards, Alejandra -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso(a)cctld.gt 18 Ave. 11 <https://maps.google.com/?q=18+Ave.+11&entry=gmail&source=g>-42 Zona 15, V.H. III. Guatemala, Guatemala www.gt

1 0

Re: [ccnso-council] Background material ccNSO Council call
by Bart Boswinkel April 18, 2019

April 18, 2019

Dear all, Please find included the Agenda and draft resolutions. Kind regards, Bart Agenda & Draft Resolutions ccNSO Council Meeting 18 April 2019 Welcome and roll call Action Items Action Item 149-01: The secretariat is requested to inform the chair of the Tech WG accordingly. (appointment of Regis Masse) Completed Action Item 149-02: Secretariat to inform the Council on the results of the signup session during the workshop. Completed, see agenda item 10. Action Item 149-03: Councilors are requested to provide feedback and comments on the proposed Approval Action Process Guideline (by 27 March 2019). Completed. Action Item 149-04: Secretariat to follow up on membership application process and report back to Council by next meeting (in April) Completed, see item 6. Action Item 149-05: The chair to draft a letter to the Board to agree on closing further evolution of the Fast Track Process after implementing the Risk Mitigation Process and agree to stop further steps with respect to the ccNSO PDP 2 and assist in review of the recommendations. Ongoing awaits clarity on Risk Mitigation response. Action Item 149-06: The secretariat to draft terms of reference for working party (review policy recommendation) (IDNccTLD) by meeting in April. Completed Intermeeting decisions (since 14 February) Adoption letter to the Board on IFRT Appointment members Internet Governance Liaison group Approval membership .la (Lao People's Democratic Republic) Response to blog post CEO & President ICANN on IRP Next Steps IFRT For discussion and decision How to move forward Background: The ccNSO Chair’s letter to the chair of the ICANN Board of Directors ccNSO Co-chair GNSO Subsequent procedures WT 5 Annebeth Lange is retiring on 1 May 2019 from Norid, However she is willing to continue. It is also re-confirmed that she is ccTLD (Norid) related. Membership application. After contacting the ccTLD manager itself, the case of the .TC application is closed (no formal application from the ccTLD manager). For discussion? Background material: Overview of steps and outcome of the application process pertaining to .tc, the specific ccTLD manger in this case. 7 . Next steps Road Map review and update IDN overall policy For discussion Draft ToR for review working party. Call for volunteers Letter from ICANN Org (IDN Variant management) Approval Travel Funding Guideline For adoption Background. The Travel funding Guideline has been shared with Council and membership to solicit changes and GRC has incorporated them. The Guideline is now submitted for adoption. Draft Resolution The ccNSO Council adopts Guideline travel funding as submitted to the Council, draft version 3. Annual Work plan ccNSO For information & discussion. Background material: The workplan is 2 years rolling forward overview of activities and schedule for these activities undertaken and to be undertaken over the next 2 years. The high level mindmaap is an attempt to cluster activites in categories that have been. The scheduling is clarified in the GANTT chart (document 9.b) and the overview document ( 9.c) contains a more detailed description of the activities. After concluding the discussion and updating the documents, to capture the comments, Council will be asked to adopt the work plan by email vote. Approval roles and responsibilities Councillors After consolidating the output from the Kobe Council Workshop and confirmation by email the ccNSO Council will adopt the consolidated overview of roles and responsibilities Draft Resolution The ccNSO Council adopts the roles and responsibilities overview and assigns these to the Councillors as listed, including the chair and vice-chair(s). PDP 3 Part 1 Retirement – Update Agenda Marrakesh Council meetings i. Prep meeting ii. Council meeting Tech Day & Members meeting WG meetings Update CSC, RZERC, ECA Update ccNSO Review Updates chair, vice-chairs and Councillors, Regional Organisations, secretariat. Updates WG. GRC IGLC (progress to date) SOPC Members Programme Committee Emoji Study Group Update liaisons Update ALAC Liaison (written update) Update GNSO Liaison (written update) Next meetings May 23rd June – Marrakech (24-27 June) July/August – 22 August September 19 October 17th November -Montreal (2-7 November) December 19th 19.AOB 20 .Closure From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Wednesday, 17 April 2019 at 17:21 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: [ccnso-council] Background material ccNSO Council call Dear all, Please find included (belated) background material. Kind regards, Bart

4 3