Dear ccNSO council members, Please find below the proposed triage recommendation(s) [22-25 - 2018]. Kindly provide me with your input by the end of 6 June 2018, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. Topic: 22-2018: Draft Final Report of the RSSAC2 Review Summary of request: Public comment on the independent examiner's Draft Final Report is invited as part of the second Root Server System Advisory Committee Review (RSSAC2). A webinar on the Draft Final Report will be hosted by the independent examiner, Interisle. Read more: https://www.icann.org/news/announcement-2018-05-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> Date received: 4 May 2018 Last day for comments/input/response, if any: 10 June 2018 Recommended action, if any: share with ccnso-council@icann.org<mailto:ccnso-council@icann.org>; ccnso-members@icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity@cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Expertise needed, if any: Reviews/Improvements, Accountability/Transparency Date of submission to Triage Committee: 23 May 2018 Deadline Triage Committee input: 25 May 2018, 23:59 UTC Date of submission to Council: 4 June 2018 Deadline Council decision: 6 June 2018, 23:59 UTC Impact on ccNSO/ccTLDs: low = = = = Topic: 23-2018: Long-Term Options to Adjust the Timeline of Reviews Summary of request: This public comment proceeding invites feedback on long-term options to provide more reasonable scheduling across ICANN reviews (Specific and Organizational), with the goal of meeting ICANN's accountability and transparency obligations in a more practical and sustainable manner. The proposal provides details on the challenges with the existing schedule of Specific and Organizational Reviews. This includes the constraints under which ICANN organization must conduct these reviews in line with the mandate from the Bylaws and a discussion on the principles and related options that the community may wish to consider. The goal is to develop a more realistic and sustainable review schedule for the future. Read more: https://www.icann.org/news/announcement-3-2018-05-14-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> Date received: 17 May 2018 Last day for comments/input/response, if any: 20 July 2018 Recommended action, if any: share with ccnso-council@icann.org<mailto:ccnso-council@icann.org>; ccnso-members@icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity@cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Webinar details have been shared with the aforementioned list, and the GRC mailing list. GRC will prepare a draft council statement. Expertise needed, if any: Reviews/Improvements, Accountability/Transparency, Bylaws Date of submission to Triage Committee: 23 May 2018 Deadline Triage Committee input: 25 May 2018, 23:59 UTC Date of submission to Council: 4 June 2018 Deadline Council decision: 6 June 2018, 23:59 UTC Impact on ccNSO/ccTLDs: middle = = = = Topic: 24-2018: Short -Term Options to Adjust the Timeline of Reviews Summary of request: This public comment proceeding proposes short-term options pertaining to current reviews to address the workload of the volunteer community and impact on ICANN resources. Specifically, the aim of this public comment proceeding is to invite feedback on options on whether and how to adjust the timeline for two Specific Reviews to alleviate existing strain on volunteer and ICANN resources. The two reviews for consideration for short-term options are the third Accountability and Transparency Review (ATRT3) and the second Registration Directory Service Review (RDS-WHOIS2). Read more: https://www.icann.org/news/announcement-2-2018-05-14-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> Date received: 17 May 2018 Last day for comments/input/response, if any: 6 July 2018 Recommended action, if any: share with ccnso-council@icann.org<mailto:ccnso-council@icann.org>; ccnso-members@icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity@cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Webinar details have been shared with the aforementioned list, and the GRC mailing list. GRC will prepare a draft council statement. Expertise needed, if any: Reviews/Improvements, Accountability and Transparency Review, Registration Directory Service Review Date of submission to Triage Committee: 23 May 2018 Deadline Triage Committee input: 25 May 2018, 23:59 UTC Date of submission to Council: 4 June 2018 Deadline Council decision: 6 June 2018, 23:59 UTC Impact on ccNSO/ccTLDs: middle = = = = Topic: 25-2018: Release for Registration one .COM Domain Name with a Single-Character Label: O.COM Summary of request: This public comment proceeding is to gather community input on the proposed amendment to implement the approved Registry Service request from the registry operator VeriSign, Inc., ("Verisign"), to release for registration one domain name with a single-character label, O.COM [o.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__o.com_&d=DwMFaQ&c=FmY1u3...>, in the .COM generic top-level domain (gTLD). The ICANN organization conducted a review of the proposed Registry Service and did not identify significant Security or Stability issues, but determined that the proposed Registry Service might raise significant competition issues. On 7 December 2017, the ICANN organization referred the matter to the appropriate governmental competition authority, the United States Department of Justice. On 14 December 2017, the Antitrust Division of the United States Department of Justice communicated to the ICANN org that it did not intend to open an investigation on the matter. Upon approving the proposed Registry Service, ICANN org determined the Registry Service requires an amendment to the .COM Registry Agreement to enable the implementation of this service. The ICANN org is seeking public comments on the proposed amendment. Read more: https://www.icann.org/news/announcement-2-2018-05-10-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> Date received: 14 May 2018 Last day for comments/input/response, if any: 20 June 2018 Recommended action, if any: share with ccnso-council@icann.org<mailto:ccnso-council@icann.org>; ccnso-members@icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity@cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Expertise needed, if any: Contracted Party Agreements, .com, single character second level Date of submission to Triage Committee: 23 May 2018 Deadline Triage Committee input: 25 May 2018, 23:59 UTC Date of submission to Council: 4 June 2018 Deadline Council decision: 6 June 2018, 23:59 UTC Impact on ccNSO/ccTLDs: low 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