FYI! Best regards Wolf-Ulrich -----Original-Nachricht----- Von: Nathalie Peregrine <nathalie.peregrine@icann.org <mailto:nathalie.peregrine@icann.org> > Betreff: [council] Please review: GNSO Council motions 24 August 2017 Datum: 27.08.2017, 09:03 Uhr An: council@gnso.icann.org <council@gnso.icann.org <mailto:council@gnso.icann.org> > CC: gnso-secs@icann.org <gnso-secs@icann.org <mailto:gnso-secs@icann.org>

Dear Councilors, Ahead of the official minutes, the following resolutions were passed by the GNSO Council at its meeting on Thursday, 24 August 2017. 20170824-1 Motion expressing support for continued ICANN community engagement in Internet Governance activities appropriate to ICANN’s mission, withdrawal as a Chartering Organization from the CCWG-IG and request for a proposal for a new structure for GNSO Council consideration by ICANN61) Submitted by Keith Drazek Seconded by James Bladel WHEREAS: 1.The GNSO Council adopted the charter for a Cross Community Working Group to discuss Internet governance (CCWG-IG) issues affecting ICANN and make recommendations to the chartering organizations on these issues on 15 October 2014, and as such became a Chartering Organization. 2. The GNSO Council adopted the "Uniform Framework of Principles and Recommendations for Cross Community Working Groups" (CCWG Framework) in October 2016. The CCWG Framework details the lifecycle of a CCWG including initiation, operation, decision-making, and closure, and the GNSO Council has observed that the CCWG-IG, whose formation predated the adoption of the CCWG Framework, does not follow this lifecycle or some of the principles outlined in the CCWG Framework. 3. The GNSO Council recognizes the importance of a continued discussion of the topic of Internet governance within an ICANN context, and the continued participation by the GNSO in this discussion. 4. The GNSO Council has shared its concerns with the ccNSO Council and representatives of other SO/ACs on the current scope of the CCWG-IG and the appropriate vehicle through which ICANN SO/ACs may continue to participate in Internet governance discussions within the ICANN context. 5. During its meeting on 7 November 2016, the GNSO Council confirmed it would continue to participate as a Chartering Organization for the CCWG-IG. However, this participation was conditioned upon a comprehensive review of the CCWG-IG Charter by the CCWG-IG, in accordance with the CCWG Framework, including the possibility that another vehicle may be more suitable for cross community discussions on the topic of Internet governance ( http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendations-16sep16-en.pdf)[gnso.icann.org] <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_drafts...> . 6. On 11 March 2017, the CCWG-IG submitted a revised charter to the GNSO Council (https://mm.icann.org/pipermail/council/2017-March/019819.html) for its consideration. 7. The GNSO Council reviewed the charter and discussed it during a number of meetings as well as in its meetings with the ccNSO Council. These discussions highlighted remaining concerns over the group’s compliance with the CCWG Framework as well as its accountability vis-√†-vis the Chartering Organizations. 8. During ICANN 59 in Johannesburg, the CCWG-IG held a face-to-face meeting that included members of the ICANN Board’s Internet Governance Committee. There was discussion about the future of the group, challenges with the ongoing nature of Internet Governance, and the constraints imposed by the community-developed requirements for CCWG structures. Members from multiple SOs and ACs recognized the challenges and generally agreed that a CCWG is not a required vehicle for the important and legitimate work of the group, provided the group is able to continue its engagement with adequate ICANN support and resources and there is no gap between the retirement of the CCWG-IG and the establishment of its successor. Resolved, 1.The GNSO Council expresses its gratitude to the CCWG-IG for its work in ensuring that discussions on Internet governance take place within the ICANN context. 2. The GNSO Council emphasizes that it fully recognizes the importance of the continued involvement of the ICANN community in Internet governance-related activities that are appropriate to ICANN’s mission. 3. The GNSO Council requests that members of the CCWG-IG and others interested parties come together to explore a framework / model that more fully addresses the concerns that have been expressed by the GNSO Council, and submit this framework / model to the GNSO Council for its consideration at the Council meeting mid-way between ICANN 60 and ICANN 61 (e.g. February GNSO Council meeting). 4. To facilitate the work as requested under Resolved clause #3, allowing for a reasonable time to coordinate with other SOs and ACs to develop a new structure, and to ensure there is no gap between the retirement of the CCWG-IG and the establishment of its successor group, the GNSO Council shall withdraw as a Chartering Organization from the CCWG-IG effective at the conclusion of ICANN 61 in San Juan, expecting that a replacement structure will be ready for approval by the Council at that time. 5. The GNSO Council emphasizes that its planned withdrawal as a Chartering Organization from the CCWG-IG reflects solely the Council’s conclusion that, based on the reports it has received from the CCWG-IG, a CCWG is not an appropriate vehicle for the CCWG-IG’s work, and the GNSO Council’s decision on this narrow point is not intended to prevent any GNSO community members who have been participating in the CCWG-IG from continuing to participate in the group’s activities should they decide to do so. 6. The GNSO Council requests that the GNSO Secretariat communicate this decision to the CCWG-IG and the other Chartering Organizations Vote results[gnso.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meeti...> 20170824-2 Nomination of GNSO Replacement Candidate for Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team Submitted by Julf Helsingius Seconded by James Bladel WHEREAS, 1. On 19 January 2017, the GNSO Council nominated (see https://gnso.icann.org/en/council/resolutions#201701) the following candidates to serve on the SSR2-RT (in alphabetical order): James Gannon, Denise Michel, and Emily Taylor as its primary three candidates for the SSR2-RT, noting that these candidates under the new ICANN Bylaws are entitled to be selected. Furthermore, the GNSO nominated (in alphabetical order): Howard Eland, Scott McCormick, Rao Naveed bin Rais, and Norm Ritchie to be considered for inclusion in the SSR2-RT by the SO-AC Chairs should additional places be available. 2. On 14 February 2017, ICANN announced the selection of the 16-member team (see https://www.icann.org/news/announcement-2-2017-02-14-en), which included the three primary candidates nominated by the GNSO Council. 3. On 16 July 2017, Emily Taylor submitted her resignation to the SSR2-RT (see http://mm.icann.org/pipermail/ssr2-review/2017-July/000468.html) <http://mm.icann.org/pipermail/ssr2-review/2017-July/000468.html)> . 4. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with recommending a replacement candidate, taking into account the criteria outlined in the call for volunteers as well as the desire to ensure a RT that is balanced for diversity and expertise ( https://www.icann.org/news/announcement-3-2016-06-30-en)[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> . 5. Out of the four candidates that were nominated in the initial selection process for consideration, beyond those that were entitled to be selected, the following three expressed that they were still interested in serving on the SSR2-RT: Scott McCormick, Rao Naveed bin Rais, and Norm Ritchie. 6. The SSC submitted its recommendation to the GNSO Council on 18 August 2017. 7. The GNSO Council considered the recommendation of the SSC. Resolved, 1. The GNSO Council nominates Norm Ritchie to replace Emily Taylor on the SSR2-RT. 2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to the staff supporting the SSR2-RT as soon as possible. 3. The GNSO Council instructs the GNSO Secretariat to inform the selected applicant that he has been chosen and that the GNSO Council expects that, the applicant will represent the views of the entire GNSO community in his work on the SSR2-RT, and provide regular feedback as a group on the discussions taking place in the SSR2-RT, as well as the positions being taken by GNSO Review Team Members. 4. The GNSO Council asks the GNSO Secretariat to send a response to those applicants who were not selected, thanking them for their continued interest. The response should also encourage them to follow the SSR2-RT work, and participate in Public Comments and community discussions Vote results[gnso.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meeti...> Thank you, Nathalie _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council