Councilors, Please below find the final proposed agenda for the GNSO Council Meeting on 22 February 2018 at 12:00 UTC. This has been posted on the GNSO Council meeting wiki page<https://community.icann.org/x/WAK8B> and on the GNSO master calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...>. The missing links will be inserted upon receipt of the requested documents, and the wiki page and master calendar will be updated accordingly. Final proposed agenda 22 February 2018 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/VQK8B This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_counc...> v3.2, updated on 01 September 2016. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 12:00 UTC: https://tinyurl.com/y8etlo5z 04:00 Los Angeles; 07:00 Washington; 12:00 London; 17:00 Islamabad; 21:00 Tokyo; 23:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/stream01.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/en/meetings/minutes-council-21dec17-en.pdf> of the GNSO Council meeting on the 21 December 2017 were posted on 8 January 2018. Minutes of the GNSO Council meeting on the 30 January 2017 were posted on XXXXXXXX Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3. Consent Agenda (0 min) None Item 4: COUNCIL VOTE – Adoption of the Charter related to the next steps for the ICANN Procedure of Handling WHOIS conflicts with Privacy Law (15 minutes) As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised WHOIS Conflicts with Privacy Law Procedure<https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts-...> on 18 April 2017 to better accommodate issues where WHOIS requirements conflict with applicable laws. As requested by this GNSO Council, ICANN published a paper<https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedur...> for public comment<https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en> to provide analysis and solicit community input on the practicality and feasibility of the triggers identified in the revised WHOIS Conflicts with Privacy Law Procedure. The public comment period was also intended to collect suggestions for moving forward with the review. The public comment period closed on 7 July 2017 and the staff report of public comments<https://www.icann.org/en/system/files/files/report-comments-whois-privacy-la...> was published on 28 July 2017. On 1 August 2017, the Council received a letter<https://gnso.icann.org/en/correspondence/atallah-to-bladel-et-al-01aug17-en....> from Akram Atallah providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council. On 24 August 2017, the Council received an update from GDD staff and discussed possible options for moving forward with the review of the Procedure for Handling WHOIS Conflicts with Privacy Law. A small group of Councilors have prepared a Charter<https://gnso.icann.org/en/drafts/draft-icann-procedure-whois-conflicts-iag-2...> (including guidelines and parameters around scope, deliverables, composition, operating procedures, etc.) pursuant to which a subsequent group will operate as it deliberates and provides suggested next steps and/or recommendations. This motion was considered during the Council’s 30 January 2018 meeting but was deferred. Here, the Council will vote to approve the Charter. 4.1 – Presentation of motion<https://community.icann.org/x/WgK8B> (Keith Drazek) 4.2 – Council Discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Replacement for GNSO member for the Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team (15 minutes) On 19 January 2017, the GNSO Council voted to approve its three primary candidates for the Second Security, Stability, and Resiliency Review Team (SSR2-RT). James Gannon, one of those three candidates, has since resigned from the SSR2-RT. The Standing Selection Committee (SSC) has been tasked with recommending a replacement candidate to be considered by the GNSO Council. Taking into account the criteria outlined in the call for volunteers, as well as the scoping information and the skills matrix developed by the SSR2-RT, the SSC has performed its review process and selected [insert name] to replace James Gannon on the SSR2-RT. Here, the Council will vote to approve [insert name] as the replacement for James Gannon on the SSR2-RT. 5.1 – Presentation of motion<https://community.icann.org/x/WgK8B> (Susan Kawaguchi) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL UPDATE – Updated Charter for the Cross Community Working Group on Internet Governance (15 minutes) At ICANN57 in Hyderabad in November 2016, the GNSO Council approved a motion conditioning the future participation of the GNSO as a Chartering Organization of the CCWG on Internet Governance (CCWG-IG) upon a comprehensive review of the group’s Charter by the CCWG-IG, in accordance with the Framework of Uniform Principles for CCWGs that had been adopted recently by the ccNSO and GNSO Councils (http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendations...). In its resolution, the GNSO Council had noted that the CCWG-IG’s future work is expected to be subject to a clear work plan, with regular updates and clear deliverables, and had requested that, by ICANN58, the CCWG-IG was to report on its findings, which report may include a revised charter, and the CCWG-IG was to also consider whether it will be preferable to reconstitute the group under a new structure (https://gnso.icann.org/en/council/resolutions - 20161107-3<https://gnso.icann.org/en/council/resolutions#20161107-3>). The CCWG-IG provided a written report on its 2016 activity and a draft revised Charter for the GNSO Council’s consideration on 10th March 2017 (http://mm.icann.org/pipermail/council/2017-March/019816.html) At its Public Meeting at ICANN58 in Copenhagen on 15 March 2017 and its joint meeting with the ccNSO Council on 13 March 2017, the Council engaged in a discussion with the CCWG-IG co-chairs regarding the group’s reports. At the GNSO Council’s call on 18 May 2017, the Council continued its discussion of the topic as well as during ICANN59 during which it became clear that although there is strong support to continue the GNSO’s involvement in Internet Governance, a CCWG is not considered the appropriate vehicle for such involvement. On 24 August 2017, the Council adopted a motion<https://community.icann.org/x/kAwhB> that among other things, requested that the members of the CCWG-IG explore a framework / model (INSERT LINK) that addresses the concerns expressed by the GNSO Council and then submit this framework / model for Council consideration between ICANN60 and ICANN61. Here the Council will consider the framework / model submitted by the CCWG-IG. 6.1 - Update on framework / model (Rafik Dammak) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION – Update and discussion on the GNSO Standing Committee on Budget and Operations (SCBO) review of the Draft FY19 ICANN Operating Plan and Budget (15 minutes) The GNSO Council has determined that it may need to provide a Council specific response (not to supersede any response from any SG/C) to certain ICANN budget related public comments. Operating on an interim charter, the Standing Committee on Budget and Operations (SCBO) is considering the Draft FY19 ICANN Operating Plan and Budget<https://www.icann.org/public-comments/fy19-budget-2018-01-19-en> and preparing a public comment in advance of the public comment close date on 8 March 2018. The SCBO and its supporting subject matter experts from various Stakeholder Groups and Constituencies have identified a number of areas where it is considering providing comment on behalf of the GNSO Council. Here, the Council will receive an update from the SCBO on these potential areas of comment. 7.1 - Update on progress (SCBO) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Discussion of the Draft Post-Implementation Review Framework (15 minutes) The Consensus Policy Implementation Framework (CPIF<https://www.icann.org/en/system/files/files/gdd-consensus-policy-implementat...>) provides guidance to ICANN org and the community for implementing policy. However, there is minimal guidance in this document or in other documentation around the review of implemented policies adopted by the GNSO Council. In some cases, a review is explicitly mandated as an element of the PDP WG’s recommendations to the Council, but in some cases, the recommendations are silent in this respect. ICANN org has prepared some initial thoughts on the approach for post-implementation reviews of Council adopted policy recommendations. ICANN org has also identified a number of questions for the Council to consider (e.g., When should a review be initiated when there is NO PDP recommendation to do so? what triggers should initiate a review? What are the expected outcomes of the review? Etc.). This document was briefly mentioned during the GNSO Council Strategic Planning Session and it was agreed during that meeting that the draft framework would be discussed in greater detail in a future Council meeting. Here, the Council will consider the possible approach and suggested questions from ICANN org. 8.1 – Presentation of materials (Brian Aitchison, ICANN staff) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION – Planning for ICANN61 (10 minutes) Taking note of the proposed block schedule for ICANN61, which was discussed at ICANN60 in Abu Dhabi, a draft GNSO schedule has been prepared for Council’s consideration. This draft largely follows the outline of the ICANN60 schedule. Based on requests received to date from the different GNSO PDP WGs, CCWGs, WGs, and cross community session landscape, the Council leadership has prepared a draft GNSO schedule<https://gnso.icann.org/en/drafts/icann61-draft-gnso-schedule-12feb18-en.pdf> for Council input and review. Following Council review, this draft GNSO schedule will continue to be shared with the GNSO Stakeholder Groups and Constituencies to facilitate their planning and scheduling. Here, following the discussions during the Council’s Strategic Planning Session, the Council will discuss its plans for the GNSO Working Session, as well as meetings with other SO/ACs and the Board. 9.1 - Update on planning for ICANN61 (Council leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: COUNCIL DISCUSSION – Assignment of Council Liaisons (15 minutes) The GNSO Council assigns liaisons to a number of different efforts, in particular to PDP WGs (as described in the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf>), as well as to Implementation Review Teams, Cross Community Working Groups, to the Country Code Names Supporting Organization (ccNSO), etc. Following the discussions during the Council’s Strategic Planning Session, where the role of liaisons was discussed in detail, the description (INSERT LINK) of the liaison role has been revised. As agreed during the Strategic Planning Session, the Council will review the liaisons for the various PDPs, IRTs, and other relevant efforts. Here, the Council will seek new volunteers or confirmation from existing liaisons<https://gnso.icann.org/en/meetings/projects-list.pdf> to continue to serve in their role. The Council will also seek to reach general agree on the updated description of the liaison role. 10.1 – Presentation of discussion topic (Council leadership) 10.2 – Council discussion 10.3 – Next steps Item 11: ANY OTHER BUSINESS (5 minutes) 11.1 – Discussion of GNSO Council Strategic Planning Session Report ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf. References for Coordinated Universal Time of 12:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 04:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-5 07:00 Buenos Aires, Argentina (ART) UTC-3 09:00 Rio de Janeiro, Brazil (BRST) UTC-2 10:00 London, United Kingdom (GMT) UTC 12:00 Paris, France (CEST) UTC+1 13:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 13:00 Islamabad, Pakistan (PKT) UTC+5 17:00 Singapore (SGT) UTC+8 20:00 Tokyo, Japan (JST) UTC+9 (+ 1 day) 21:00 Sydney/Hobart, Australia (AEDT) UTC+11 23:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/y8etlo5z