August 2017 - council - lists.icann.org

For your review: Please update Project List
by Nathalie Peregrine 21 Aug '17

21 Aug '17

Dear Councilors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meeting. If there are no comments, the list will be posted on the website on page: http://gnso.icann.org/en/council/project<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> and be directly viewed at :http://gnso.icann.org/meetings/projects-list.pdf<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings…> Thanks so much, Kind regards, Nathalie

1 0

Draft motion - replacement candidate for SSR2
by Johan Helsingius 21 Aug '17

21 Aug '17

Here is the draft motion to nominate the GNSO replacement candidate for the Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team (to be discussed and hopefully approved at our Council Meeting on 24 August). The actual name will hopefully be provided in a couple of days. Julf

4 6

Proposed Final Agenda GNSO Council Meeting 24 August 2017 at 12:00 UTC
by Nathalie Peregrine 18 Aug '17

18 Aug '17

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_coun…> 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-recommendation…). 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-procedu…> 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-l…> 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-27jun1…) – 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

4 5

Proposed amendments to CCWG-IG motion
by Rafik Dammak 16 Aug '17

16 Aug '17

Hi all, please find attached a document with proposed amendments to the CCWG-IG motion that was deferred in the last council call. I hope they can be accepted as friendly. Best, Rafik

7 7

GNSO Council Abstention Notification Form [#253]
by ICANN 16 Aug '17

16 Aug '17

1 0

FW: [soac-chairs] Status regarding appointment of new chair and vice chair of SSAC
by James M. Bladel 14 Aug '17

14 Aug '17

Councilors, FYI - Please see below for a message from Patrik on the new SSAC leadership selection. The incoming Chair and Vice Chair will take office at the beginning of the year (2018). I will convey our congratulations on behalf of the GNSO to Rod and Julie, and express our gratitude to Patrik and Jim for their work over the years (and the next few months remaining in their term). Thank you, J. ------------------ James Bladel GNSO Chair On 8/13/17, 15:09 , "soac-chairs-bounces(a)icann.org on behalf of Patrik Fältström" <soac-chairs-bounces(a)icann.org on behalf of paf(a)frobbit.se> wrote: All, This is for your information. We in SSAC do appoint chair and vice chair on three year terms. The current term ends December 31, 2017. We have in SSAC have finalized our selection process, and for your information we have selected Rod Rasmussen and Julie Hammer as chair and vice chair. The next step is that ICANN Board formally will make the appointment of the chair at the board meeting at ICANN61. And of course after that on January 1 2018 the new chair and vice chair start their term. Because of this, although you might have heard rumors of the selection, the actual announcement(s) we will make more broadly at next ICANN meeting after the appointment process formally is finalized and of course when the new chair and vice chair start their term. Until then myself and Jim Galvin continue to lead SSAC just like the last couple of years. Patrik Fältström SSAC Chair

1 0

REMINDER: Document and Motion deadline Monday, 14 August 2017 at 23:59 UTC for the GNSO Council Meeting 24 August 2017 at 12:00 UTC
by Nathalie Peregrine 14 Aug '17

14 Aug '17

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 14 August 2017 at 23:59 UTC) of the GNSO Council Meeting on 24 August 2017 at 12:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/x/kAwhB Thank you very much. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses<file:////learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…>

1 0

REMINDER: Document and Motion deadline Monday, 14 August 2017 at 23:59 UTC for the GNSO Council Meeting 24 August 2017 at 12:00 UTC
by Terri Agnew 10 Aug '17

10 Aug '17

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 14 August 2017 at 23:59 UTC) of the GNSO Council Meeting on 24 August 2017 at 12:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/x/kAwhB Thank you very much. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: <mailto:terri.agnew@icann.org> terri.agnew(a)icann.org Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…> GNSO Newcomer pages

1 0

Fwd: Note on Work Track 5
by Heather Forrest 09 Aug '17

09 Aug '17

Dear colleagues, Jeff's email below deals with some of the questions raised here on the list about SubPro WT5. James, Donna and I can update further after we talk with the SubPro leadership tomorrow. Best wishes, Heather ---------- Forwarded message ---------- From: Jeff Neuman <jeff.neuman(a)comlaude.com> Date: Tue, Aug 8, 2017 at 5:49 AM Subject: Note on Work Track 5 To: "James Bladel (jbladel(a)godaddy.com)" <jbladel(a)godaddy.com>, Heather Forrest <haforrestesq(a)gmail.com>, "Austin, Donna" <Donna.Austin(a)team.neustar > Cc: avri doria <avri(a)apc.org>, Steve Chan <steve.chan(a)icann.org>, Emily Barabas <emily.barabas(a)icann.org>, Julie Hedlund <julie.hedlund(a)icann.org>, Marika Konings <marika.konings(a)icann.org> All, It seems that there have been a number of questions on the operation and establishment of Work Track 5 on the GNSO Council Mailing list. I am not able to post on that list, but ask that this be forwarded. I have not run this response by Avri, but I would hope she agrees. According to the GNSO Working Group Guidelines, found at https://gnso.icann.org/en/improvements/gnso-working-group-guidelines-final- 10dec10-en.pdf, Section 2.3 states: *“2.3. Use of Sub-Teams * *The WG may decide to employ sub-teams as an efficient means of delegating topics or assignments to be completed. Sub-team members need to have a clear understanding of issues they work on as well as the results to be achieved. The members of sub-teams report their results to whole working group for review and approval. The WG should indicate whether or not it would like to have meetings of the sub-team recorded and/or transcribed. * *Any member of the WG may serve on any sub-team; however, depending upon the specific tasks to be accomplished, the Chair should ensure that the sub-team is properly balanced with the appropriate skills and resources to ensure successful completion. It is recommended that the sub-team appoints a co-ordinator who heads up the sub-team and is responsible for providing regular progress updates to the Working Group.* *There is no need for formal confirmation by the CO or WG of such a co-ordinator. * *The lifespan of a sub-team should not extend beyond that of the Working Group. Decisions made by sub-teams should always be shared with the larger working group and a call for consensus must be made by the entire WG. “* This is what Avri and I are doing. We are setting up a “Sub Team” which we are calling a “Work Track.” Other than the last sentence of ensuring that all decisions go to the larger working group, there are no other restrictions on the operation of a Sub Team. Therefore, we believe that the choice of leadership, how meetings are conducted, the name of the group, membership, etc. is at our (the co-chair’s) discretion. Yes, all of the recommendations from this Work Track will of course go to the full Working Group, just as they will for all of the other Work Tracks. On the question of whether this will set a precedent on how Sub Teams will be used in the future, I will leave that to the folks who look back at this time period in 15 years or so. But if it works and strengthens the multi-stakeholder process, while still having it operate under the rubric of the GNSO, would that not be a positive precedent? I appreciate the Council interest in this and encourage you all to bring that enthusiasm to Work Track 5. Please let me know if you have any other questions. *Jeffrey J. Neuman* *Senior Vice President *|*Valideus USA* | *Com Laude USA* 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: *jeff.neuman(a)valideus.com <jeff.neuman(a)valideus.com>* or *jeff.neuman(a)comlaude.com <jeff.neuman(a)comlaude.com>* T: +1.703.635.7514 <(703)%20635-7514> M: +1.202.549.5079 <(202)%20549-5079> @Jintlaw

4 11

FW: [So-ac-sg-cleaders] Empowered Community – ICANN Budget and Operating Plans in Effect - ICANN
by James M. Bladel 08 Aug '17

08 Aug '17

Councilors, FYI. Thank you – J. From: <so-ac-sg-cleaders-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Tuesday, August 8, 2017 at 13:57 Subject: [So-ac-sg-cleaders] Empowered Community – ICANN Budget and Operating Plans in Effect - ICANN https://www.icann.org/news/blog/empowered-community-icann-budget-and-operat… Empowered Community – ICANN Budget and Operating Plans in Effect On 17 July 2017, the ICANNEmpowered Community confirmed that it was not rejecting any of the following documents previously approved by the ICANN Board on 24 June 2017: · ICANN’s FY2018 Budget and Operating Plan · IANA’s Budget for FY2018 · ICANN’s Five-Year Operating Plan The confirmation followed the expiration of the 21-day period for the Empowered Community to raise a petition against any of these documents. Read more about these and other Empowered Community actions here<https://www.icann.org/en/ec#ongoing-actions> Details · ICANN Blog · Author: Xavier Calvez · 08 Aug 2017 Sent from my iPhone David A. Olive Senior Vice President, Policy Development Support Managing Director, ICANN Regional Office –Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349<tel:10%2034349> Fulya, Besiktas, Istanbul Internet Corporation for Assigned Names and Numbers (ICANN)

1 0