Dear councilors, Please find the Proposed Final Agenda for the GNSO Council Meeting on 24 August 2017 at 12:00 UTC. Additional necessary information will be added upon receipt and an updated version circulated at that moment. Final Proposed Agenda 24 August 2017 - GNSO Council Meeting 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/igwhB 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: http://tinyurl.com/y8tmfkkd 05:00 Los Angeles; 08:00 Washington; 13:00 London; 15:00 Istanbul; 22:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/gnso.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-28jun17-en.pdf> of the meeting of the GNSO Council on 28 June 2017, posted on 20 July 2017. Minutes<https://gnso.icann.org/en/meetings/minutes-council-13jul17-en.pdf> of the meeting of the GNSO Council on 13 July 2017, posted on 03 August 2017. 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> 2.2 - Report results of e-vote on the Council response to the GAC Communique. Item 3. Consent Agenda (5 mins) None Item 4: COUNCIL VOTE – Updated Charter for the Cross Community Working Group on Internet Governance (20 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. The Council discussed this motion on its 13 July 2017 call, where the vote was deferred. Here the Council will consider the motion that has been submitted in relation to this topic. 4.1 – Presentation of motion<https://community.icann.org/x/kAwhB> (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 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). Emily Taylor, 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, the SSC has performed its review process and selected [name] to replace Emily Taylor on the SSR2-RT. Here, the Council will vote to approve [name] as the replacement for Emily Taylor on the SSR2-RT. 5.1 – Presentation of motion<https://community.icann.org/x/kAwhB> (Johan Helsingius) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6. COUNCIL DISCUSSION – Changing the Name of the GNSO (15 minutes) Some in the community have noted that as domain name are available globally, the term “generic” has certain meanings to different parts of the ICANN community, that the usage of “generic” to describe a .brand is potentially confusing, and among other reasons, that it might make sense to substitute the word “Generic” for “Global” in Generic Names Supporting Organization. To consider this change, some on the GNSO Council have suggested that a narrowly scoped Drafting Team should be formed to determine whether a change of this nature is recommended and if so, develop a proposed implementation plan to effectuate that change. Here, the Council will discuss whether it supports the premise of changing the name of the GNSO and if so, what next steps might be. 6.1 – Presentation of discussion topic (Paul McGrady) 6.2 – Council discussion 6.3 – Next Steps Item 7: COUNCIL DISCUSSION – Review of the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law (20 minutes) As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised Whois 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 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 Attalah, providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council. Here, the Council will discuss options for moving forward with the review of the Whois Procedure. 7.1 – Update on current status (GNSO Council chairs) 7.2 – Council Discussion 7.3 – Next Steps Item 8: COUNCIL DISCUSSION – PLANNING FOR ICANN60 (10 minutes) During ICANN59, the proposed block schedule for ICANN60 was shared (https://gnso.icann.org/en/drafts/icann60-draft-prelim-block-schedule-27jun17...) – note that further updates have been made as a result of the SO/AC Planning Committee and the resulting cross-community session selections. Based on requests received to date from the different GNSO PDP WGs, CCWGs WGs, and cross community session landscape, the Council leadership has revised its draft GNSO schedule for Council input and review, available here. Following Council review, this draft GNSO schedule will again be shared with the GNSO Stakeholder Groups and Constituencies to facilitate their planning and scheduling. 8.1 - Update on planning for ICANN60 (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: ANY OTHER BUSINESS (5 minutes) 9.1 – Report from chairs on our call with Subsequent Procedures (“SubPro”) PDP co-chairs, regarding the creation of Work Track 5 (WT5) 9.2 – Update from CCWG-ACCT WS2 ________________________________ 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-7 05:00 San José, Costa Rica UTC-6 06:00 Iowa City, USA (CDT) UTC-5 07:00 New York/Washington DC, USA (EDT) UTC-4 08:00 Buenos Aires, Argentina (ART) UTC-3 09:00 Rio de Janeiro, Brazil (BRST) UTC-3 09::00 London, United Kingdom (GMT) UTC+1 13:00 Bonn, Germany (CET) UTC+2 14:00 Cairo, Egypt, (EET) UTC+2 14:00 Istanbul, Turkey (TRT) UTC+3 15:00 Singapore (SGT) UTC +8 20:00 Tokyo, Japan (JST) UTC+9 21:00 Sydney/Hobart, Australia (AEDT) UTC+11 22:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2017, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and http://tinyurl.com/y8tmfkkd