Dear councillors, Please find below the proposed triage recommendation 23, 24 and 25 - 2017. Kindly provide me with your input by the end of 16 May 2017, 23:59 UTC, in case you do not agree with the proposed recommendations. Thank you. Topic: 23-2017: Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps Now Available for Public Comment Originator: ICANN, GNSO Summary of request: ICANN published a paper, "Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps," for public comment. Feedback will be incorporated into a report of public comments and provided to the Generic Names Supporting Organization (GNSO) Council for their review and consideration. In accordance with the ICANN Procedure for Handling Whois Conflicts with Privacy Law (Whois Procedure)[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources...>, this paper opens a review process to gather community input on the effectiveness of the revised Whois Procedure, which was made effective on 18 April 2017. Furthermore, as requested by the GNSO Council, ICANN is publishing this paper to provide analysis of and solicit community input on the practicality and feasibility of the triggers, as well as suggestions for moving forward with the review. Outputs from this assessment and comment process are expected to inform the next periodic review of the procedure.The Whois Procedure has recently been updated, although no ICANN-accredited registrar or registry operator to date has formally invoked the procedure. As a result, this analysis is based solely on community discussions and input received during the previous review[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draft...> [PDF, 155 KB], which related to allowing for evaluation of an additional trigger for invoking the procedure. It also draws upon ICANN's experience administering other processes where a contracted party is seeking ICANN's approval for new services, or waiving certain contractual requirements, as a point of comparison for the implementation of the procedure. Read the announcement here: https://www.icann.org/news/announcement-2017-05-03-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D05-2D03-2Den&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HyTT2ymvadmiQcmo6B088sWOukGjEbibHJ64u5rMiME&m=VjQbO9VqPlqpDQtpOUMs-Y9ORXS06XKV_g12VbXbgao&s=JPuUc8oNuW4AQlsAisyjv2gqfLGxGLkAufzaHIMbHTE&e=> Date received: 4 May 2017 Last day for Comments/input/response, if any: 12 June 2017 Recommended action, if any: none Expertise needed, if any: WHOIS, gTLDs Date of submission to Triage Committee: 11 May 2017 Recommendation received by Triage Committee: 12 May 2017 Date of submission to Council: 12 May 2017 Deadline Council decision: 16 May 2017, 23:59 UTC Impact on ccNSO/ccTLDs: low = = = = = Topic: 24-2017: Draft Framework of Interpretation for Human Rights Summary of request: This Public Comment seeks community input on the Cross Community Working Group on Enhancing ICANN Accountability Work Stream 2 (CCWG-Accountability, WS2) draft Framework of Interpretation for Human Rights. This draft was developed by the CCWG-Accountability as required by Annex 12 of the final report of the CCWG-Accountability, Work Stream 1. Read the announcement here: https://www.icann.org/news/announcement-2017-05-05-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D05-2D05-2Den&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HyTT2ymvadmiQcmo6B088sWOukGjEbibHJ64u5rMiME&m=VjQbO9VqPlqpDQtpOUMs-Y9ORXS06XKV_g12VbXbgao&s=jFaC206vSYqvWnCpdDsS2bJRW8Tfg0YBcPmF65ore7w&e=> Date received: 9 May 2017 Last day for Comments/input/response, if any: 16 June 2017 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 accounts. Expertise needed, if any: bylaws, human rights Date of submission to Triage Committee: 11 May 2017 Recommendation received by Triage Committee: 12 May 2017 Date of submission to Council: 12 May 2017 Deadline Council decision: 16 May 2017, 23:59 UTC Impact on ccNSO/ccTLDs: low = = = = = Topic: 25-2017: Release of Country and Territory Names within the .PIONEER, .FUJITSU, .OBI, .SHARP, .TOYOTA, and .LEXUS TLDs Summary of request: Five (5) Registry Services Evaluation Policy (RSEP)[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources...> requests were submitted by the registry operators listed below to allow the release of country and territory names for the below TLDs. In total, the requests concern six (6) new gTLDs. .pioneer, .fujitsu, .obi, .sharp, .toyota, .lexus Currently, the .PIONEER, .FUJITSU, .OBI, .SHARP, .TOYOTA, and .LEXUS Registry Agreements require country and territory names contained in specific internationally recognized lists to be withheld from registration or allocated to the registry operator at all levels. As required by the RSEP, ICANN has undertaken a preliminary determination on whether these RSEP proposals might raise significant competition, security or stability issues. ICANN's preliminary review (based on the information provided) did not identify any such issues. Following ICANN's preliminary determination that the proposals do not raise significant competition, security or stability issues, it was further determined that the change would require a material change to the respective Registry Agreements and that an amendment is needed in order to effect the change. The proposed amendments, which are being posted for comment, would allow the registration of country and territory names at all levels in .PIONEER, .FUJITSU, .OBI, .SHARP, .TOYOTA, and .LEXUS. It should be noted that Specification 13 has been granted for .PIONEER on 16 July 2015, .FUJITSU on 30 July 2015, .OBI on 25 September 2014, .SHARP on 03 September 2015, and .TOYOTA and .LEXUS on 23 April 2015. Read the announcement here: https://www.icann.org/public-comments/ctn-release-tlds-2017-05-08-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_ctn-2Drelease-2Dtlds-2D2017-2D05-2D08-2Den&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HyTT2ymvadmiQcmo6B088sWOukGjEbibHJ64u5rMiME&m=VjQbO9VqPlqpDQtpOUMs-Y9ORXS06XKV_g12VbXbgao&s=NzQr4OjBFzzgg3C-Nc93FTNZYLNoD6-NXMZoeUXZvmk&e=> Date received: 9 May 2017 Last day for Comments/input/response, if any: 20 June 2017 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 accounts. Expertise needed, if any: top level domains, second level domains, contracted party agreements, security/stability Date of submission to Triage Committee: 11 May 2017 Recommendation received by Triage Committee: 12 May 2017 Date of submission to Council: 12 May 2017 Deadline Council decision: 16 May 2017, 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