Dear all, Please find below the resolutions from the GNSO Council at its meeting on Wednesday 24 October 2018. If no objections we will publish them on the GNSO website here: https://gnso.icann.org/en/council/resolutions Consent Agenda: Motion: Reappointment of GNSO Council Liaison to the Governmental Advisory Committee Submitted by Donna Austin Seconded by Michele Neylon Whereas: 1. As part of the discussions within ICANN between the GNSO and GAC on how to facilitate early engagement of the GAC in GNSO policy development activities, the option of appointing a GNSO liaison to the GAC was initially piloted in FY15 and F16, and subsequently confirmed by the GNSO Council as a permanent role at the start of FY17. 2. The GNSO Council appointed Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee on 1 November 2017, until the end of the ICANN AGM 2018. 3. The GNSO Council has an obligation to review the role annually and reconfirm the appointment unless the review indicates otherwise and/or the Liaison has indicated that he/she is no longer available to continue in this role, in which case a new selection process will take place. 4. The GNSO Council leadership has met with Julf Helsingius to discuss his experience and to confirm that he is willing to continue in this role. 5. The GNSO Council has reviewed the annual report prepared by the GNSO Liaison to the GAC. Resolved: 1. The GNSO Council hereby reappoints Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee until the end of the ICANN AGM 2019. 2. The GNSO Council leadership team will inform the GAC leadership team accordingly, and will co-ordinate with Julf Helsingius as well as the GAC leadership team and GAC Secretariat on next steps and the continued successful implementation of this role. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...> Motion to adopt the charter for the GNSO Standing Committee on Budget and Operations (SCBO) on a permanent basis Submitted by: Ayden Férdeline Seconded by: Rafik Dammak Whereas, 1. In 2017 the GNSO Council expressed its desire to establish the GNSO Standing Committee on Budget and Operations (SCBO) to assist with the development of GNSO Council comments that relate to ICANN’s Budgetary and Finance matters; 2. On 21 December 2017, the GNSO Council adopted the formation of the SCBO and its interim charter; 3. In late 2017 and early 2018, GNSO Council members as well as subject matter experts from GNSO Stakeholder Groups and Constituencies joined the SCBO; 4. In FY18, the SCBO developed four public comments (IANA-PTI FY19 Budget, ICANN's Reserve Fund Target Level, ICANN’s Draft FY19 Budget and Operating Plan, and ICANN Reserve Fund: Proposed Replenishment Strategy) on behalf of the GNSO Council that were later accepted and posted to ICANN’s public forum; and 5. On 17 September 2018, the SCBO delivered an After-Action Report on the SCBO experiences and lessons learned wherein the report suggested that the SCBO charter did not warrant any changes and that the SCBO become a permanent Standing Committee of the GNSO Council. Resolved, 1. The GNSO Council adopts the GNSO Standing Committee on Budget and Operations (SCBO) charter on a permanent basis (see: https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-ican... [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...>); 2. The GNSO Council thanks the Council members and subject matter experts for their contributions through the FY19 budget planning cycle; 3. The GNSO Council will appoint the incoming Council Chair as the Council liaison to the SCBO and add Council Vice-Chairs as observers; 4. The GNSO Council instructs the GNSO Secretariat to launch a fresh call for volunteers per the membership criteria outlined in the SCBO Charter as soon as possible; and 5. The GNSO Council tasks the SCBO to carry out the review and comment formulation for future ICANN fiscal-year draft budget planning cycles and to submit its proposed recommendations to the GNSO Council with sufficient time for its consideration. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...> Motion to recommend the implementation of certain improvements to enhance the efficiency and effectiveness of the GNSO Policy Development Process (PDP 3.0) Submitted by Rafik Dammak Seconded by Heather Forrest Whereas, 1. In January 2018, the GNSO Council held an inaugural three-day Strategic Planning Session during which it, amongst other activities, reviewed the workload for the year ahead and identified potential milestones, noting that the current average timeline for delivery of an Initial Report has increased at least 2-4 times compared to previous PDPs. 2. The GNSO Council began identify challenges being encountered in PDPs, informed by a staff discussion paper on optimizing increased engagement and participation while ensuring efficient and effective policy development. 3. In order to engage the broader GNSO community in this discussion, the GNSO Council organized a collaborative session involving the members of the current PDP Leadership Teams as well as the broader community to summarize key points from the Strategic Planning Session, elaborate on the challenges that PDPs presently face and identified, and begin to brainstorm possible solutions. 4. As a result of these discussions, staff was tasked to publish a discussion paper that synthesizes the challenges that were identified as part of these discussions as well as possible improvements — both immediate and longer term — that the Council and PDP Working Groups could consider implementing to enhance efficiency and effectiveness of GNSO policy development activities. This discussion paper was published on 8 May 2018 (see https://gnso.icann.org/en/drafts/pdp-discussion-paper-11may18-en.pdf [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draft...>). 5. GNSO Stakeholder Groups, Constituencies as well as other SO/ACs were invited to provide their input and feedback on the discussion paper. A summary report of the feedback received was shared with the Council on 10 September 2018 (see https://gnso.icann.org/en/drafts/pdp-summary-feedback-10sep18-en.pdf [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draft...>) followed by a dedicated webinar on 11 September 2018 to further review and discuss the input received (see https://participate.icann.org/p1s5rcio69b/). 6. Based on the input received as well as the subsequent webinar, Council leadership developed a proposed GNSO PDP 3.0 Final Report and Recommendations for Council consideration (see (https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-increa... [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...>). 7. The GNSO Council and broader community reviewed and discussed the GNSO PDP 3.0 Final Report and Recommendations during the GNSO Weekend Session at ICANN63 (Oct 2018). Resolved, 1. The GNSO Council hereby adopts the GNSO PDP 3.0 Final Report and Recommendations and instructs GNSO Support Staff to work with the incoming Council leadership on the roll out of the Implementation Plan. 2. The GNSO Council requests the incoming 2018/19 Council leadership to report on a quarterly basis on the status of implementation. 3. The GNSO Council thanks all those that have contributed to the discussions on GNSO PDP 3.0 as well as the proposed improvements to enhance the efficiency and effectiveness of the GNSO PDP. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...> Motion to terminate the Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process Submitted by Stephanie Perrin Seconded by Darcy Southwell Whereas, 1. Following submission of the WHOIS Policy Review Team's Final Report, the ICANN Board passed a resolution on 8 November, 2012, launching an Expert Working Group on gTLD Registration Directory Services (EWG) to (1) help redefine the purpose of gTLD registration data and consider how to safeguard the data, and (2) propose a model for gTLD registration directory services to address accuracy, privacy, and access issues. 2. Upon publication of the EWG's Final Report in June, 2014, an informal group of Generic Names Supporting Organization (GNSO) Councilors and ICANN Board members collaborated to propose a Process Framework for structuring a GNSO Policy Development Process (PDP) to successfully address these challenging issues. 3. On 26 May, 2015, the ICANN Board adopted that Process Framework and reaffirmed its 2012 request for a Board-initiated PDP to define the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy. 4. On 19 November 2015, the GNSO Council adopted the charter for the next-generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process Working group. 5. Following ICANN61 (March 2018), the RDS PDP Leadership decided to put on hold WG meetings indefinitely. This decision was made in light of the uncertain status of GDPR-related work and the possible duplication of efforts as a result of the adoption by the ICANN Board of the Temporary Specification for gTLD Registration Data. 6. Following the initiation by the GNSO Council of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration data, the RDS PDP on 17 July 2018, the GNSO Council Liaison to the RDS PDP WG, Stephanie Perrin, submitted, at the request of the RDS PDP WG, the required Termination Summary [https://gnso.icann.org/sites/default/files/file/field-file-attach/next-gen-r... [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...>] to recommend to the GNSO Council that the RDS PDP WG be terminated as per section 15 of the PDP Manual. 7. The GNSO Council has reviewed the Termination Summary. Resolved, 1. The GNSO Council hereby terminates the next-generation gTLD Registration Directory Service (RDS) to replace WHOIS Policy Development Process. 2. The GNSO Chair will share the Termination Summary as well as the Council decision with the ICANN Board for its information. 3. The GNSO Secretariat will inform the RDS PDP WG of this decision. 4. The GNSO Council expresses its sincere appreciation to the members of the RDS PDP Working Group, leadership team and ICANN support staff for all its work and efforts. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...> Motion for GNSO Council Adoption of the Final Report of the IGO-INGO ACCESS to Curative Rights PDP Working Group - WITHDRAWN PRIOR TO THE COUNCIL MEETING BY DONNA AUSTIN Submitted by Donna Austin Seconded by Whereas: 1. On 5 June 2014, the GNSO Council launched [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_counc...> a Policy Development Process (PDP) on access to curative rights mechanisms at the second level of the domain name system by International Governmental Organizations (IGOs) and Non-Governmental Organizations; 2. On 25 June 2014, the GNSO Council approved the initial Charter [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draft...> for the PDP Working Group, which was subsequently amended<https://community.icann.org/download/attachments/48347887/WG%20Charter%20-%2...> on 16 April 2015; 3. This PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issue...> delivered to the GNSO Council on 9 July 2018; 4. The PDP Working Group has reached consensus on all the recommendations in its Final Report; 5. At its 19 July 2018 meeting, the GNSO Council had acknowledged [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_counc...> the report and “the need to consider the topic of curative rights protections for IGOs in the broader context of appropriate overall scope of protection for all IGO identifiers (including IGO acronyms)”. The GNSO Council had declared its intention to review the Final Report (including the Minority Statements submitted) “with a view toward developing a possible path forward that will also facilitate the resolution of the outstanding inconsistencies between GAC advice and prior GNSO policy recommendations on the overall scope of IGO protections” as well as act on the recommendations “at the earliest opportunity following its review and deliberations on these topics”; 6. The GNSO Council had also noted that, until outstanding issues concerning protections for IGO names and acronyms are resolved, IGO acronyms remain reserved on an interim basis at the second level of the domain name system for those gTLDs delegated under the 2012 New gTLD Program round; and 7. The GNSO Council has reviewed and discussed the Working Group’s recommendations, including at a special Council discussion on 9 October 2018 where the Council also discussed the following questions: a. What questions/topics was the Working Group chartered to consider? b. Did the Working Group consider those charter topics/questions, and did it do so in a legitimate way? c. Has the Working Group followed due process? d. What were the process issues (if any) encountered by the Working Group? e. Did the Working Group address GAC advice on this topic? Resolved: 1. The GNSO Council adopts all the PDP Working Group’s final recommendations as contained in the Final Report. 2. The GNSO Council thanks the members of the PDP Working Group for their hard work in developing the recommendations. 3. Should the PDP recommendations be adopted by the ICANN Board, the GNSO Council directs ICANN staff to convene an Implementation Review Team. The Implementation Review Team will be tasked with assisting ICANN staff in developing the implementation details for the PDP recommendations, evaluating the proposed implementation of the recommendations as approved by the Board, and working with ICANN staff to ensure that the resultant implementation conforms to the intent of the approved recommendations. The Implementation Review Team shall operate in accordance with the Implementation Review Team Principles and Guidance approved by the GNSO Council in June 2015. 4. The GNSO Council requests that, following the adoption by the ICANN Board of the PDP recommendations, ICANN staff issue a call for volunteers for the Implementation Review Team, to be circulated at a minimum to the members of the PDP Working Group. Vote results [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_de...> Kind regards, Nathalie