Dear Councillors, We have received several requests for input, that were addressed via triage recommendations. Below I have included an overview of all recommendations as formulated by the Triage Committee. The summary and background of the recommendations, the proposed action for each of them and the relevant deadlines, are included in the tables further down in this e-mail. If you do not agree with the recommendations, kindly let me know by Monday, 13 May 2019, 23:59 UTC. Thank you! NEW fields in template below: assessment - Impact on ccNSO - Relevance for ccTLDs Regarding the impact assessment, one of the following labels was assigned: <no impact, low, medium, high, very high>. Overview triage recommendation number + topic: 23-2019: Updated Request for Proposal: ICANN's Technical Compliance Monitoring System 24-2019: Invitation: Name Collision Analysis Project (NCAP) Discussion Group 25-2019: Evolving ICANN’s Multistakeholder Model 26-2019: Label Generation Rules for Root Zone Version 3 (RZ-LGR-3) 27-2019: Process Proposal for Streamlining Organizational Reviews Number: 23-2019 Topic: Updated Request for Proposal: ICANN's Technical Compliance Monitoring System Request from: ICANN Summary: ICANN is seeking to identify a provider to develop and maintain a Technical Compliance Monitoring system. The Technical Compliance Monitoring system is intended to enable the ICANN organization to help generic top-level domain (gTLD) registries and registrars ensure compliance with ICANN's consensus policies, as well as the provisions described in the 2017 gTLD Base Registry Agreement and the 2013 Registrar Accreditation Agreement (contracted parties' agreements). ICANN is seeking to identify a provider to develop this system based on ICANN's requirements, as well as to maintain the system and develop additional enhancements. his announcement updates the previously announced request for proposals [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...>, by including additional control points covered by more recent policy documents. Close date: until 23:59 UTC on 14 May 2019 Read more: https://www.icann.org/news/announcement-2019-04-10-en? [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> Recommended action: none Impact on ccNSO: No impact Relevance for ccTLDs: low Number: 24-2019 Topic: Invitation: Name Collision Analysis Project (NCAP) Discussion Group Request from: ICANN Summary: ICANN is seeking participants for the Name Collision Analysis Project (NCAP) discussion group. The NCAP discussion group, as defined by the Security and Stability Advisory Committee (SSAC) proposal and revised by ICANN's Office of the CTO, is an open and public group tasked with discussing issues pertaining to the work of the NCAP Study 1. The NCAP Study 1 was authorized by the ICANN Board of Directors on 14 March 2019. The study will: * examine all prior work on the issue of name collisions and produce a summary report that brings forward important knowledge from prior work into this study, and which can act as a primer for those new to the subject. * create a list of data sets used in past studies, identify gaps, if any, and list additional data that would be required to successfully complete Studies 2 and 3. * decide if the project should proceed based on the results of the survey of prior work and the availability of data. Close date: 6 May 2019 Read more: https://www.icann.org/news/announcement-2-2019-04-17-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> Recommended action: Share with the following mailing lists: ccNSO-members, broader ccTLD community, ccNSO-council. Share via the ccNSO twitter account. (done, seen the short deadline) Impact on ccNSO: low Relevance for ccTLDs: low Number: 25-2019 Topic: Evolving ICANN’s Multistakeholder Model Request from: ICANN MSSI Summary: This public comment supports the Draft ICANN Strategic Plan for Fiscal Years 2021-2025 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system...>. The Draft Strategic Plan includes a set of five strategic objectives. Strategic Objective #2 addresses ICANN Governance and aims to improve the effectiveness of ICANN's multistakeholder model. The strategic objectives provide guidance for establishing Specific, Measurable, Attainable, Results-oriented, and Time bound (SMART) operating goals and plans to fulfill the vision and deliver on the mission over the five-year horizon of the Strategic Plan. At ICANN64, to develop a plan to support Strategic Objective # 2, the community engaged in a facilitated conversation [64.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__64.schedule.icann.org_m...> about how to improve the effectiveness and efficiency of ICANN's multistakeholder model of governance. Building on the conversation at ICANN64, this public comment invites the community to further define issues that challenge the effectiveness of ICANN's multistakeholder model. Close date: 4 June 2019 Read more: https://www.icann.org/news/announcement-2019-04-25-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> Recommended action: * Council statement need, as defined inhttps://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-state... [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_d...> * Share with the following mailing lists: SOPC, ccNSO-members, broader ccTLD community, ccNSO-council. * Share via the ccNSO twitter account. Impact on ccNSO: high Relevance for ccTLDs: high Number: 26-2019 Topic: Label Generation Rules for Root Zone Version 3 (RZ-LGR-3) Request from: ICANN GDD Summary: Purpose: To determine valid top-level Internationalized Domain Name (IDN) labels and their variant labels, the community had finalized the Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system...> (the Procedure). The Procedure requires community-based Generation Panels (GPs), organized for relevant scripts, to convene and propose specific rules. These rules are evaluated and then integrated into the Root Zone Label Generation Rules (RZ-LGR) by the Integration Panel (IP). Current Status: The IP has successfully evaluated the Root Zone Label Generation Rules (LGR) proposals [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources...> for 10 additional scripts, including Devanagari, Gujarati, Gurmukhi, Hebrew, Kannada, Malayalam, Oriya, Sinhala, Tamil and Telugu. These proposals were finalized and submitted by the respective GPs, following the release of the individual proposals for public comments. The IP has integrated these proposals, along with Arabic, Ethiopic, Georgian, Khmer, Lao and Thai scripts already integrated into the second version of the Root Zone LGR (RZ-LGR-2 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources...>), to develop the third version of the Root Zone LGR (RZ-LGR-3) [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_sites_def...>. Next Steps: As per the Procedure, RZ-LGR-3 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_sites_def...> is being released for public comments to gather community feedback for its finalization. Proposals for additional scripts will be integrated in future versions of the RZ-LGR. Close date: 19 June 2019 (23:59 UTC) Read more: https://www.icann.org/public-comments/rz-lgr-3-2019-04-25-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2D...> Recommended action: Share with the following mailing lists: ccNSO-members, broader ccTLD community, ccNSO-council. Share via the ccNSO twitter account. Impact on ccNSO: low Relevance for ccTLDs: low Number: 27-2019 Topic: Process Proposal for Streamlining Organizational Reviews Request from: ICANN MSSI Summary: Organizational reviews are a key component of ICANN accountability and transparency measures as mandated by the ICANN Bylaws, Section 4.4. The community has identified areas of the organizational review process that may benefit from streamlining. This public comment proceeding seeks to solicit community input on "Process for Streamlining Organizational Reviews: A Proposal [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system...>". Specifically, the community is asked to provide feedback on four questions that are the focus of this public comment: 1. Do you/your organization agree with the proposed list of issues that should form the focus of the streamlining process? If not, with which do you disagree and what would you like to add? 2. Do you/your organization agree with the proposed underlying principles that should guide the solutions? If not, with which do you disagree and what would you like to add? 3. Do you/your organization agree with the community role in the streamlining process? If not, what would you propose? 4. Do you/your organization agree with the proposed high-level timeline? If not, what would you propose? Close date: 15 July 2019 (23:59 UTC) Read more: https://www.icann.org/public-comments/streamlining-org-reviews-proposal-2019... [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2D...> Recommended action: Council statement needed, draft to be prepared by GRC. (see https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-state... [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_d...>) Impact on ccNSO: high Relevance for ccTLDs: middle Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@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