May 2017 - council - lists.icann.org

Fwd: [SOAC-Leaders] Announcement: Pre-ICANN59 Policy Update Webinar - Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC
by James M. Bladel 22 May '17

22 May '17

Councilors - See below. In preparation for ICANN59, these Policy Webinars can be very helpful in getting up to speed on all of the various work efforts underway. Please feel free to share with your SG/C. Thank you, J. ----------------- James Bladel GNSO Chair ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: May 22, 2017, 07:54 -0500 Subject: [SOAC-Leaders] Announcement: Pre-ICANN59 Policy Update Webinar - Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC Dear SOAC Leaders: Please find below the announcement of the “Pre-ICANN59 Policy Update Webinar” published on the ICANN website. Please share it with your groups. Best regards, David https://www.icann.org/news/announcement-2017-05-22-en Please RSVP via this form<https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> by 13 June 2017. You will receive remote participation details the week of 12 June 2017. The ICANN Policy Development Support Team will host a Policy Update Webinar on Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC), in preparation for the upcoming ICANN59 Policy Forum in Johannesburg, South Africa. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and to brief the community on the Empowered Community consultation and cross-community sessions taking place in Johannesburg. Briefings on the Empowered Community Consultation and Cross-Community Sessions: · Special session on the Proposed Fundamental Bylaws Amendments · Next-Generation Generic Top-Level Domain (gTLD) Registration Directory Services (RDS) policy requirements · General Data Protection Regulation (GDPR) · Geographic names · Operational side of ICANN's Operating Plan and Budget · Who sets ICANN's priorities? Updates on Supporting Organizations and Advisory Committees: · Address Supporting Organization (ASO) and regional Internet registries (RIR) policy development · Country Code Names Supporting Organization (ccNSO) · Generic Names Supporting Organization (GNSO) · At-Large Advisory Committee (ALAC) and At-Large Community · Governmental Advisory Committee (GAC) · Root Server System Advisory Committee (RSSAC) · Security and Stability Advisory Committee (SSAC) The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs in English for 90 minutes. The webinar will be conducted via Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, participants may submit questions using the chat function in Adobe Connect. Recordings of the webinars will be made available here<https://www.icann.org/resources/pages/presentations-2012-08-27-en>. The Policy Development Support Team is always available to answer any questions via email at policyinfo(a)icann.org<mailto:policyinfo@icann.org>. Please RSVP via this form<https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> by 13 June 2017. You will receive remote participation details the week of 12 June 2017.

1 0

Announcement: Pre-ICANN59 Policy Update Webinar Thursday, 15 June 2017 at 10:00 UTC and 19:00 UTC
by Terri Agnew 22 May '17

22 May '17

https://www.icann.org/news/announcement-2017-05-22-en Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. The ICANN Policy Development Support Team will host a Policy Update Webinar on Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC), in preparation for the upcoming ICANN59 Policy Forum in Johannesburg, South Africa. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and to brief the community on the Empowered Community consultation and cross-community sessions taking place in Johannesburg. Briefings on the Empowered Community Consultation and Cross-Community Sessions: * Special session on the Proposed Fundamental Bylaws Amendments * Next-Generation Generic Top-Level Domain (gTLD) Registration Directory Services (RDS) policy requirements * General Data Protection Regulation (GDPR) * Geographic names * Operational side of ICANN's Operating Plan and Budget * Who sets ICANN's priorities? Updates on Supporting Organizations and Advisory Committees: * Address Supporting Organization (ASO) and regional Internet registries (RIR) policy development * Country Code Names Supporting Organization (ccNSO) * Generic Names Supporting Organization (GNSO) * At-Large Advisory Committee (ALAC) and At-Large Community * Governmental Advisory Committee (GAC) * Root Server System Advisory Committee (RSSAC) * Security and Stability Advisory Committee (SSAC) The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs in English for 90 minutes. The webinar will be conducted via Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, participants may submit questions using the chat function in Adobe Connect. Recordings of the webinars will be made available <https://www.icann.org/resources/pages/presentations-2012-08-27-en> here. The Policy Development Support Team is always available to answer any questions via email at <mailto:policyinfo@icann.org> policyinfo(a)icann.org. Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. Ozan Sahin Community Engagement Support Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6218 Mobile: +90.533.641.0007 Email: ozan.sahin(a)icann.org <mailto:ozan.sahin@icann.org> Skype: ozan.sahin.icann www.icann.org

1 0

GNSO Council motions 18 May 2017
by Nathalie Peregrine 22 May '17

22 May '17

Dear Councilors, Ahead of the official minutes, the following resolutions were passed by the GNSO Council at its meeting on Thursday, 18 May 2017. Please review and I will then circulate to the Council list and post to the website. Consent agenda Acknowledgment of the Selection of Matthew Shears for Seat 14 on the ICANN Board. The NCPH has selected Matthew Shears to succeed Markus Kummer for Seat 14 on the ICANN Board of Directors. As required by Section 7.2 of the ICANN Bylaws, on 5 May 2017, the GNSO Council Chair has informed the Empowered Community Administration, the ICANN Secretary, and the Decisional Participants of Matthew’s selection (see https://gnso.icann.org/en/correspondence/bladel-to-empowered-community-admi…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…>). This agenda item is intended to acknowledge the selection and confirm that the notification process was completed. GNSO validation of the CCWG-Accountability-WS2 request for extension of mandate and funding for FY18 Following the request from the CCWG-Accountability Chairs (see https://gnso.icann.org/en/correspondence/ccwg-accountability-to-chartering-…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…>), a motion (see https://community.icann.org/x/eQLfAw<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>) was submitted for the GNSO to validate the extension of mandate and funding for FY18 to allow the CCWG-Accountability-WS2 to complete its work. Vote results<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> Adoption of the GNSO Review of GAC Communiqué for submission to the ICANN Board Submitted by James Bladel Seconded by Michele Neylon Whereas, 1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the Copenhagen GAC Communiqué (see https://gnso.icann.org/en/drafts/review-gac-communique-25apr17-en.pdf ) and requests that the GNSO Council Chair communicate the GNSO Review of the Copenhagen GAC Communiqué to the ICANN Board. 2. The GNSO Council requests that the GNSO Council Chair also informs the GAC Chair of the communication between the GNSO Council and the ICANN Board. Vote results<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> Thank you very much for your time and feedback. Nathalie

1 0

Fwd: [SOAC-Leaders] Clarifying the Roles of the ICANN Complaints Office and Ombudsman - ICANN
by James M. Bladel 19 May '17

19 May '17

Councilors - Please see below for a blog post on the distinction between the new Complaints Officer and the Ombudsman. This question was raised at the recent GDD Summit in Madrid. Thank you, J. ----------------- James Bladel GNSO Chair ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: May 19, 2017, 02:51 -0700 Subject: [SOAC-Leaders] Clarifying the Roles of the ICANN Complaints Office and Ombudsman - ICANN Clarifying the Roles of the ICANN Complaints Office and Ombudsman <https://www.icann.org/news/blog/clarifying-the-roles-of-the-icann-complaint…><https://www.icann.org/news/blog/clarifying-the-roles-of-the-icann-complaint…><https://www.icann.org/news/blog/clarifying-the-roles-of-the-icann-complaint…><https://www.icann.org/news/blog/clarifying-the-roles-of-the-icann-complaint…><https://www.icann.org/news/blog/clarifying-the-roles-of-the-icann-complaint…><https://www.icann.org/news/blog/clarifying-the-roles-of-the-icann-complaint…> Last month, the ICANN organization officially launched<https://www.icann.org/news/blog/complaints-office-update-objectives-next-st…> its Complaints Office, which serves a complimentary role to ICANN’s existing complaints processes<https://www.icann.org/resources/accountability>, such as Contractual Compliance<https://www.icann.org/resources/pages/compliance-2012-02-25-en>, Request for Reconsideration<https://www.icann.org/groups/board/governance/reconsideration> and the Ombudsman<https://www.icann.org/ombudsman>. However, we have noticed some confusion about the difference between the scope of the Complaints Office and the Office of the Ombudsman. We hope that this blog will help clarify and differentiate the roles and scopes of our offices. https://www.icann.org/news/blog/clarifying-the-roles-of-the-icann-complaint… Sent from my iPhone David A. Olive Senior Vice President, Policy Development Support Managing Director, ICANN Regional Office –Istanbul

1 0

MP3 and AC Chat transcript/ GNSO Council Teleconference 18 May 2017
by Terri Agnew 18 May '17

18 May '17

Dear GNSO Council, Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 18 May 2017 at: https://audio.icann.org/gnso/gnso-council-18may17-en.mp3 as well as the Adobe chat at: <https://gnso.icann.org/en/meetings/transcript-chat-council-18may17-en.pdf> https://gnso.icann.org/en/meetings/transcript-chat-council-18may17-en.pdf And the Adobe recording: <https://participate.icann.org/p8ubbtz6a9l/?OWASP_CSRFTOKEN=1d0b66cd3929354d 21560731d101913a0a7092f23edd328723cd77441b3653ca> https://participate.icann.org/p8ubbtz6a9l/ all on page: <https://gnso.icann.org/en/group-activities/calendar#may> https://gnso.icann.org/en/group-activities/calendar#may In addition, the slide presentations are linked below and attached. Item 5: UPDATE - CCWG-Accountability-WS2 status of work and expected timeline for delivery of Final Report - Presenter: Thomas Rickert <https://www.icann.org/en/system/files/files/ccwg-acct-ws2-dashboard-18may17 -en.pdf> Slide deck Item 10.1 - Update from the GNSO Standing Selection Committee (SSC) on the its work to select the GNSO representative for the Empowered Committee - Presenter: Susan Kawaguchi <https://gnso.icann.org/en/meetings/presentation-ssc-gnso-representative-emp owered-community-admin-18may17-en.pdf> Slide deck. Thank you. Happy listening and reading! With kind regards, Terri --- Terri Agnew Secretariat Services Coordinator, GNSO 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 i <file://learn.icann.org/courses/gnso> nteractive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy -efforts.htm#newcomers> GNSO Newcomer pages

1 0

Re: [council] Proposed Final Agenda GNSO Council Meeting 18 May 2017 at 12:00 UTC
by Darcy Southwell 18 May '17

18 May '17

My apologies, but I have a scheduling conflict and will have to drop off today’s meeting at 13:30. That timing shouldn’t interfere with any voting. Best, Darcy From: <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, May 10, 2017 at 12:54 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Proposed Final Agenda GNSO Council Meeting 18 May 2017 at 12:00 UTC Dear councilors, Please find the Proposed Final Agenda for the GNSO Council Meeting on 18 May 2017 at 12:00 UTC. Additional necessary information will be added upon receipt and an updated version circulated at that moment. Proposed Final Agenda for GNSO Council Meeting of 18 May 2017 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/fQLfAw This agenda was established according to the GNSO Operating Procedures 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/ml6mx9f 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 of the meeting of the GNSO Council on 15 March 2017, posted on 6 April 2017. Minutes of the meeting of the GNSO Council on 20 April 2017, posted on 8 May 2017. 1.5 – Note the Electronic vote results on the Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names (see results). 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 and Action Item List Item 3. Consent Agenda (5 mins) 3.1 – Acknowledgment of the Selection of Matthew Shears for Seat 14 on the ICANN Board. The NCPH has selected Matthew Shears to succeed Markus Kummer for Seat 14 on the ICANN Board of Directors. As required by Section 7.2 of the ICANN Bylaws, on 5 May 2017, the GNSO Council Chair has informed the Empowered Community Administration, the ICANN Secretary, and the Decisional Participants of Matthew’s selection (see https://gnso.icann.org/en/correspondence/bladel-to-empowered-community-admi…). This agenda item is intended to acknowledge the selection and confirm that the notification process was completed. 3.2 - GNSO validation of the CCWG-Accountability-WS2 request for extension of mandate and funding for FY18 Following the request from the CCWG-Accountability Chairs (see https://gnso.icann.org/en/correspondence/ccwg-accountability-to-chartering-…), a motion (see https://community.icann.org/x/eQLfAw) was submitted for the GNSO to validate the extension of mandate and funding for FY18 to allow the CCWG-Accountability-WS2 to complete its work. The two items described in 3.1 and 3.2 above will be considered approved if the Council votes to pass the Consent Agenda Item 4. COUNCIL VOTE – Approval of GNSO Council Review of the GAC Communique from Copenhagen (10 minutes) The GNSO Council has adopted the practice of providing feedback to the ICANN Board on matters pertaining to gTLD policy, where the Governmental Advisory Committee (GAC) has included advice on such matters as part of a GAC Communique issued at each ICANN Public Meeting. Following the issuance of the GAC Copenhagen Communique (https://gacweb.icann.org/download/attachments/27132037/GAC%20ICANN%2058%20C…), a team of Councilors and the current GNSO Liaison to the GAC agreed to prepare an initial draft of possible GNSO Council input to the Board for Council consideration. While the draft was not completed in time for the April Council meeting, a draft response was completed shortly afterwards and communicated to the ICANN Board on 26 April 2017 (see https://gnso.icann.org/en/correspondence/gnso-council-to-icann-board-25apr1…). Here the Council will vote to confirm the final language of the response. 4.1 – Presentation of motion (James Bladel) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5: UPDATE – CCWG-Accountability-WS2 status of work and expected timeline for delivery of Final Report (15 minutes) The Co-Chairs of the CCWG-Accountability-WS2 have indicated that the group will not complete its work in FY17 as originally planned. However, the group has estimated that the extension of WS2 for all of FY18 can be supported by the original budget allocation (see also consent agenda item). Here the Council will receive an update from the GNSO appointed co-chair to the CCWG-Accountability on the status of work and expected timeline for delivery of the Final Report. 5.1 – Update (Thomas Rickert) 5.2 – Council discussion 5.3 – Next steps Item 6: DISCUSSION ITEM – 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-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 or a recommendation to reconstitute the group under a new structure (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, the Council engaged in a discussion with the CCWG-IG co-chairs regarding the group’s reports. Here the Council will take into consideration the information provided and the updated charter and discuss whether the GNSO will continue its participation as a Chartering Organization of this CCWG. 6.1 – Council discussion 6.2 – Next steps Item 7. COUNCIL DISCUSSION – Confirmation of Voting on Initiating the GNSO’s Section 16 Process for Amending Approved GNSO Policy Recommendations Relating to Certain Red Cross Movement Names (15 minutes) At ICANN58 in Copenhagen in March 2017, representatives from the GNSO (including the GNSO Council chairs) and the GAC held a dialogue, facilitated by former Board member Bruce Tonkin, to discuss possible ways of reconciling inconsistent GAC advice and GNSO policy recommendations relating to National Society names of the Red Cross Movement and the two names of the international components of the Movement (http://sched.co/9xr2). Following that discussion, the ICANN Board passed a resolution requesting that the GNSO Council initiate the process outlined in Section 16 of the GNSO’s Policy Development Process (PDP) Manual, which sets forth the requisite steps for amending policy recommendations that have been approved by the GNSO Council but not yet approved by the ICANN Board (https://www.icann.org/resources/board-material/prelim-report-2017-03-16-en#…). The Board’s request related to the 190 Red Cross National Society names and the two international movement names and a limited defined set of their variants. The Council initiated electronic voting on 3 May 2017. Here the Council will discuss the outcome of the electronic voting, as well as the anticipated next steps as it relates to initiating Section 16, together with the chair of the PDP WG, Thomas Rickert. 7.1 – Council discussion 7.2 – Next Steps Item 8: UPDATE – Multistakeholder Strategy and Strategic Initiatives (MSSI) Presentation on Specific Reviews (CCT-RT next steps, RDS & ATRT selection process, and SSR 2 Update) (20 Minutes) Section 4.6 in the ICANN Bylaws calls for periodic reviews performed by community review teams related to four key objectives. These Specific Reviews specifically focus on: a) Accountability and Transparency Review (ATRT) b) Security, Stability, and Resiliency Review (SSR) c) Competition, Consumer Trust and Consumer Choice Review (CCT-RT) d) Registration Directory Service Review (RDS) (formerly WHOIS) ICANN’s Multistakeholder Strategy and Strategic Initiatives (MSSI) team will provide an introduction to the Specific Reviews and discuss the CCT-RT Draft Report and next steps, the RDS and ATRT selection and scoping process, and the SSR selection process and initial activities. 8.1 – MSSI Presentation – MSSI Team 8.2 – Open discussion and Q&A Item 9: COUNCIL DISCUSSION – PLANNING FOR ICANN59 IN JOHANNESBURG, JUNE 2017 (10 minutes) The next ICANN Public Meeting (ICANN59) will be a 4-day Policy Forum, to be held in Johannesburg, South Africa, from 26-29 June 2017. A draft GNSO Block Schedule has been prepared by the GNSO Council leadership team with the support of staff [INSERT LINK] and a draft overall Block Schedule for the meeting has been circulated to members of the community-based Planning Committee [INSERT LINK]. Here the Council will discuss scheduling and other planning-related topics in preparation for ICANN59, including confirmation of face-to-face meeting sessions for the following PDP Working Groups: Next-Generation Registration Directory Services, New gTLD Subsequent Procedures, Review of All Rights Protection Mechanisms in All gTLDs, and IGO-INGO Curative Rights Protection Mechanisms, all of whose leadership teams have submitted requests for specific sessions. 9.1 – Summary of planning activities to date (GNSO Council chairs) 9.2 – Council discussion 9.3 – Next steps Item 10: ANY OTHER BUSINESS (5 minutes) ________________________________ 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 October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-7 05:00 San José, Costa Rica UTC-6 06:00 Iowa City, USA (CST) UTC-5 07:00 New York/Washington DC, USA (EST) 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 and https://tinyurl.com/ml6mx9f Thank you. With kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

1 0

Fyi INVITATION: IETF Overview and Special-Use Domain Names Problem Statement Last Call Webex - Tuesday May 23, at 1700-1830 UTC
by Nathalie Peregrine 18 May '17

18 May '17

*Forwarding on behalf of the IETF* INVITATION FROM THE IETF TO THE ICANN COMMUNITY This session is intended to help the ICANN community understand the IETF process and productively participate in the discussion of a document on Special Use Names that may be of interest. The DNSOP Working Group within the IETF has recently completed work on a problem statement document on Special-Use Domain Names (draft-ietf-dnsop-sutld-ps-03 - https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/[datatracker.iet…<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_d…> ). The IETF will soon be initiating their final comment period for the document – the IETF Last Call. The IETF would like to invite the ICANN community to share their input on the document. This session will start with an overview of the IETF last call process and how it works. It will then have a short summary of the SUTLD document, and describe how to provide comments. It would be helpful for participants to have read "The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force" (https://www.ietf.org/tao.html[ietf.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_tao.html&…> ) This session will be held via WebEx on Tuesday, May 23, at 1700 -1830 UTC. Webex participation details are included below. Meeting Link: https://ietf.webex.com/ietf/j.php?MTID=m1333532ce167e4a5a09b1d42d002b632[ie…<https://urldefense.proofpoint.com/v2/url?u=https-3A__ietf.webex.com_ietf_j.…> (going to this link in advance of the meeting will allow you to generate a calendar invitation) Join by phone: 1-877-668-4493 Call-in toll free number (US/Canada) 1-650-479-3208 Call-in toll number (US/Canada) Meeting number: 310 638 156 Meeting password: LastCall

2 1

GNSO Council Abstention Notification Form [#246]
by ICANN 18 May '17

18 May '17

1 0

CCWG-IG Charter
by Austin, Donna 17 May '17

17 May '17

Thanks Rafik, for providing a copy of the word doc. I’ve made some comments in the document and perhaps you can address these during the Council meeting tomorrow or over email. I apologise that I didn’t get these to you earlier. These comments are reflective of concerns expressed by the RySG when the CCWG IG has been discussed. I understand that post-transition ICANN needs to be cognizant, and responsive, to any potential threats to its mandate and well-being from external entities. This is not a new situation, but certainly the new environment may see a new wave of threats emerge. I certainly appreciate the benefits of having a community that is conversant of these threats and are actively engaged with ICANN the organisation and the Board with a view to mitigating against any emerging threats. I do have concerns about the authority of the CCWG IG to develop position papers and present these as ICANN community contributions, but perhaps this concern would be allayed if I had a better understanding of the subject matter of these position papers. I would also hope that any position papers would be supported by ICANN’s GE team and the Board IG WG. I think the Charter would benefit from more specificity in this regard, along with concrete examples of the IG fora the CCWG would attend or be involved in in some way. I still struggle with the CCWG as the most appropriate vehicle for this effort and it would be helpful to understand if other possibilities were discussed, or conversely why the CCWG believes this is the most appropriate vehicle. My struggle relates to the fact that the Charter speaks to a number of different products, but no timeline or specificity. While the charter proposes co-ordination with the ICANN’s GE team and the Board IG WG, to me it would seem a much better option to have the members of the current CCWG IG, ICANN’s GE team and the Board IG WG, develop an overarching strategy on IG, which clearly sets out roles and responsibilities and project plans could be developed as a result. Perhaps this has already been done and I am just not familiar with it. Look forward to discussing on the Council call tomorrow. Regards Donna From: Rafik Dammak [mailto:rafik.dammak@gmail.com] Sent: Tuesday, May 16, 2017 12:12 AM To: Austin, Donna <Donna.Austin(a)neustar.biz<mailto:Donna.Austin@neustar.biz>> Cc: mariliamaciel(a)gmail.com<mailto:mariliamaciel@gmail.com>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: Copy of CCWG-IG charter in word doc Hi Donna, please find attached the word version. Best, Rafik 2017-05-16 3:22 GMT+09:00 Austin, Donna <Donna.Austin(a)neustar.biz<mailto:Donna.Austin@neustar.biz>>: Hi Rafik and Marilia I have some comments on the CCWG-IG, but I am unable to make them on the pdf doc. I was wondering if you could possibly share the word version of the document. Thanks Donna

1 0

FW: The 2-Character Answer to this GAC Advice Should be "No"
by Phil Corwin 16 May '17

16 May '17

Fellow Councilors - this new article relates to the response to Copenhagen GAC advice that we shall be voting on in two days. Best, Philip From: Phil Corwin Sent: Tuesday, May 16, 2017 9:29 AM To: Phil Corwin Subject: The 2-Character Answer to this GAC Advice Should be "No" I have just published a new article regarding current ICANN developments between the Board and GAC. It can be found at http://www.circleid.com/posts/20170516_the_2_character_answer_to_this_gac_a… Here's the introduction- Overview: ICANN's GAC has reacted to the ICANN Board's November 2016 decision to authorize the release of two-character domains at new gTLDs with advice to the Board that does not have true consensus backing from GAC members and that relates to procedure, not policy. The Board's proper response should be to just say no, stick to its decision and advise the GAC that it will not consider such advice. Instead, the Board has, against the preliminary advice of the policy-making GNSO Council, initiated discussions with aggrieved GAC members that may reopen its decision. Continuing down this dangerous path may provide governments with far more leverage over ICANN policy decisions than was ever envisioned or intended by the long debated and carefully crafted new Bylaws language addressing the Board's responsibility to give attention to GAC advice. I hope you find it of interest and welcome any feedback. Best regards, Philip Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/Cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com/email-signature> Version: 2016.0.8012 / Virus Database: 4776/14441 - Release Date: 05/06/17 Internal Virus Database is out of date.

2 2