May 2017 - council - lists.icann.org

Please review: Updated Project List
by Nathalie Peregrine July 10, 2017

July 10, 2017

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 1

FW: [Ext] ICANN News Alert -- Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps Now Available for Public Comment
by Marika Konings June 1, 2017

June 1, 2017

For your information, the public comment period that kicks of the next review of the ICANN Procedure for Handling Whois conflicts with Privacy Law is now open (see below). Comments may be submitted until 12 June 2017. Best regards, Marika From: ICANN News Alert <no-reply(a)external.icann.org> Reply-To: "no-reply(a)external.icann.org" <no-reply(a)external.icann.org> Date: Thursday, May 4, 2017 at 01:30 To: Marika Konings <marika.konings(a)icann.org> Subject: [Ext] ICANN News Alert -- Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps Now Available for Public Comment [CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2017-05-03-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps Now Available for Public Comment 3 May 2017 LOS ANGELES – 3 May 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today published a paper, "Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps," for public comment. Read the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 159 KB]. This paper is available for public comment through 12 June 2017. Feedback will be incorporated into a report of public comments and provided to the Generic Names Supporting Organization (GNSO) Council for their review and consideration. Comment on the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>. In accordance with the ICANN Procedure for Handling Whois Conflicts with Privacy Law (Whois Procedure)[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, this paper opens a review process to gather community input on the effectiveness of the revised Whois Procedure, which was made effective on 18 April 2017. Furthermore, as requested by the GNSO Council, ICANN is publishing this paper to provide analysis of and solicit community input on the practicality and feasibility of the triggers, as well as suggestions for moving forward with the review. Outputs from this assessment and comment process are expected to inform the next periodic review of the procedure. The Whois Procedure has recently been updated, although no ICANN-accredited registrar or registry operator to date has formally invoked the procedure. As a result, this analysis is based solely on community discussions and input received during the previous review[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> [PDF, 155 KB], which related to allowing for evaluation of an additional trigger for invoking the procedure. It also draws upon ICANN's experience administering other processes where a contracted party is seeking ICANN's approval for new services, or waiving certain contractual requirements, as a point of comparison for the implementation of the procedure. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMFa…>. This message was sent to marika.konings(a)icann.org from: ICANN News Alert | no-reply(a)external.icann.org | ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [Contact - Try It Free!] [icontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icontact.com_a.pl_1…> Manage Your Subscription [app.icontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__app.icontact.com_icp_mm…>

1 1

ICANN59 Draft GNSO Schedule and GNSO Working session agenda
by Nathalie Peregrine May 31, 2017

May 31, 2017

Dear all, Please find attached the draft GNSO Schedule for ICANN59 as well as the draft agenda for the GNSO Working session (09:15 – 15:00 local time on Monday 26 June) posted below. Draft agenda GNSO Working Session 9.15 – 9.30 – Welcome by GNSO Chair, confirmation of agenda 9.30 – 10.00 – new gTLD Sub Pro PDP WG Status Update 10.00 – 10.15 – KSK Roll Over by David Conrad (TBC) 10.15 – 10.30 – Coffee Break 10.30 – 10.45 – Planning for PTI FY19 Budget with Elise Gerich (TBC) 10.45 – 11.15 – RPMs PDP WG Status Update 11.15 – 11.45 – RDS PDP WG Update 11.45 – 12.15 – GSE Briefing and Q&A with Sally Costerton (TBC) 12.15 – 13.30 – Working lunch – prep for meeting with ccNSO, prep for meeting with GAC 13.30 – 14.00 – Joint meeting with the Board Working Group on Internet Governance (TBC) 14.00 – 14.30 - IGO Curative Rights PDP WG Status Update 14.30 – 15.00 – AOB As a reminder, the ICANN59 Block Schedule will be published on the 5th June 2017, so further changes may still be made. Remote Participation emails will be sent out shortly after that date, the Remote Participation wiki page for public, open GNSO meetings has already been set up here: https://community.icann.org/x/aSTwAw Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FW: [Correspondence] Steve Crocker to GNSO Council Leadership RE: Draft Review of the Copenhagen GAC Communiqué
by Marika Konings May 26, 2017

May 26, 2017

Dear all, On behalf of the GNSO Council leadership, I’m hereby sharing a letter from Chairman Steve Crocker in response to the GNSO Council draft review of the GAC Copenhagen Communiqué that was received today. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Action Item from the GNSO Council call: Update on Jurisdiction Work Stream 2 subteam - Thomas Rickert
by Nathalie Peregrine May 26, 2017

May 26, 2017

Dear all, As a reminder, one of the Action items from the GNSO Council call on the 18 May 2017 was that Thomas Rickert as a follow up to the update he provided on the call, provide the Council with an additional update on the WS2 Jurisdiction sub team’s work to date. Please see his email below. Kind regards, Nathalie From: "rickert(a)anwaelte.de" <rickert(a)anwaelte.de> Date: Friday, May 26, 2017 at 4:06 PM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Cc: "rickert(a)anwaelte.de" <rickert(a)anwaelte.de>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] Re: Reminder: Action Item from the GNSO Council call: Update on Jurisdiction Work Stream 2 subteam Dear Nathalie, Sorry for the delay. The current status of the Jurisdiction sub-group is as follows: * Currently working on completing the analysis of ICANN's past litigations with the sub-group - about 50% completed and pushing to complete by ICANN 59. * Currently working on analyzing responses to the Jurisdiction questionnaire - some in the sub-group was disappointed that there were only about 20 responses. Most responses did not find any issues with ICANN's jurisdiction of incorporation and did not provide any documentation relative to this. However a number brought up issues around OFAC, governments being asked to sign a contract with ICANN for a TLD or issues around certain names such as WINE. Again the sub-group is trying to complete this by ICANN 59. * The sub-group has received a response from ICANN legal regarding an initial list of questions with respect to jurisdiction and is currently awaiting a response to questions regarding the choice of law vs the Registry and Registrar agreements. * The work plan is focused on completing the above analyses and then returning to the work of identifying issues, if any, and proposing solutions to any issues identified. I am happy to answer more questions and if you need more detail or context, please let me know. Best, Thomas Am 24.05.2017 um 17:06 schrieb Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>>: Dear Thomas, Thank you so much for joining the GNSO Council meeting on Thursday 18 May 2017. Your presentation was greatly appreciated and your slide deck has since been circulated to the Council mailing list. This is just a friendly reminder that you offered to provide the Council with an update on the WS2 Jurisdiction sub team’s work to date. Please let me know if I can assist in any way. Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <x-msg://67/nathalie.peregrine@icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Draft Minutes Meeting of the GNSO Council 18 May 2017 to review
by Nathalie Peregrine May 26, 2017

May 26, 2017

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on the 18 May 2017 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 5th June 2017. Thank you very much. Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FOR INFORMATION: New webpages launched for Empowered Community and Empowered Community Administration
by Mary Wong May 26, 2017

May 26, 2017

Dear Councilors, As you’ll see from the announcement below, three new web pages describing the structure and powers of the Empowered Community, the role of the Empowered Community Administration, and a list of all notices and correspondence handled through the Empowered Community Administration, have now been launched on the ICANN website. Please let me know if you or your communities have any questions or feedback. Thanks and cheers Mary From: <ecadmin-bounces(a)icann.org> on behalf of Mary Wong <mary.wong(a)icann.org> Date: Friday, May 26, 2017 at 09:17 To: "ecadmin(a)icann.org" <ecadmin(a)icann.org> Subject: [ECAdmin] New webpages launched for Empowered Community and Empowered Community Administration Dear members of the Empowered Community Administration, We wish to inform you that, as discussed at the first Empowered Community Administration meeting in Copenhagen, ICANN has launched the initial set of web pages that describe the Empowered Community and the Empowered Community Administration, as well as a Correspondence page to house all correspondence and notifications sent to and by the Empowered Community Administration: https://www.icann.org/news/announcement-2017-05-25-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>. We hope that you and your community groups will find these web pages helpful. We will continue to build out and update these and other informational web pages for each exercise by the Empowered Community of any of its powers under the ICANN Bylaws. You may wish to note that the first update, in respect of the Empowered Community’s Approval Action concerning the proposed Fundamental Bylaw amendment, has already been made: https://www.icann.org/en/ec/proposed-fundamentals-bylaws-changes-move-gov-c…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_ec_pr…>. In preparation for the upcoming Community Forum at ICANN59 in Johannesburg, ICANN staff will work with you to set up a conference call shortly to discuss logistical and other organizational matters concerning the Empowered Community Administration’s moderation and management of the forum. Thanks and cheers Mary Mary Wong Senior Policy Director & Special Adviser for Strategic Policy Planning Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org<mailto:mary.wong@icann.org> Telephone: +1-603-5744889

1 0

FW: Business Constituency (BC) - New Chair through December 2017
by Nathalie Peregrine May 24, 2017

May 24, 2017

FYI From: <gnso-secs-bounces(a)icann.org> on behalf of Chantelle Doerksen <chantelle.doerksen(a)icann.org> Date: Wednesday, May 24, 2017 at 4:25 PM To: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Business Constituency (BC) - New Chair through December 2017 Dear GNSO Council and Support Staff, This email is to notify you that Andrew Mack has been elected as the new chair of the Business Constituency, effective immediately. Andrew is based in Washington D.C., and will be attending ICANN59 in Johannesburg. His email is amack(a)amglobal.com<mailto:amack@amglobal.com>. Kind regards, Chantelle _________________ Chantelle Doerksen | Secretariat Support - BC, IPC, ISPCP ICANN - Internet Corporation for Assigned Names and Numbers

1 0

FW: 23 May 2017 Notice to Empowered Community on Fundamental Bylaws
by James M. Bladel May 24, 2017

May 24, 2017

Councilors - See attached for a letter from ICANN Legal, regarding Board approval of a modification to a Fundamental Bylaw. (Board approval link isn’t clickable in the doc, but is located here: https://www.icann.org/resources/board-material/resolutions-2017-05-18-en#1.c) These changes are subject to review and approval by the Empowered Community Administration, which is scheduled to begin at ICANN59 in Johannesburg. Thank you, J. From: John Jeffrey <john.jeffrey(a)icann.org> Date: Tuesday, May 23, 2017 at 15:50 Subject: 23 May 2017 Notice to Empowered Community on Fundamental Bylaws Greetings, Please see the attached Notice. Best, John Jeffrey General Counsel & Secretary, ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, California 90094-2536 JJ(a)ICANN.org<mailto:JJ@ICANN.org>

2 1

Action Items: GNSO Council meeting 18 May 2017
by Nathalie Peregrine May 23, 2017

May 23, 2017

Dear Councilors, Please find the action items, below and as attachment, arising from the GNSO Council meeting on 18 May 2017. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. The next GNSO Council meeting is on the 28 June 2017. ACTION ITEMS GNSO COUNCIL MEETING 18 May 2017 Item 2. Opening Remarks / Review of Projects & Action List * James Bladel to provide update to the Council regarding GNSO Nominees for the Registration Data Services Review Team (RDS RT) after meeting with the SO/AC leaders. Item 3. Consent Agenda * GNSO Secretariat to communicate the extension request support from the GNSO Council to WS2 leadership. Item 4. COUNCIL VOTE – Approval of GNSO Council Review of the GAC Communique from Copenhagen * Staff to schedule meeting/discussion between GNSO Council and ICANN Board to further discuss the decision-making process * James Bladel to inform the GAC Chair of the communication between the GNSO Council and the ICANN Board and to incorporate request that the GNSO Council would like to better understand the process and timeline for a decision on the communiqué regarding the two-letter string issue Item 5: UPDATE – CCWG-Accountability-WS2 status of work and expected timeline for delivery of Final Report * Thomas Rickert to provide written update to the GNSO Council on the work of the Jurisdiction Team * Staff to circulate presentation slide deck to the Council mailing list Item 6: DISCUSSION ITEM – Updated Charter for the Cross Community Working Group on Internet Governance * Council to discuss and prepare motion to either express support for a new charter or withdraw as a chartering organization. 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 * GNSO Council to work with staff to reconvene the PDP to address the questions that were outlined in the motion, specifically on Red Cross protections. * Staff to prepare draft letter on behalf of GNSO Council leadership to original PDP members to see if they are willing to be part of the reconvened group Item 8: UPDATE – Multi-stakeholder Strategy and Strategic Initiatives (MSSI) Presentation on Specific Reviews (CCT-RT next steps, RDS & ATRT selection process, and SSR 2 Update) * Item postponed. MSSI staff to provide update to the GNSO Council via the mailing list. Item 9: COUNCIL DISCUSSION – PLANNING FOR ICANN59 IN JOHANNESBURG, JUNE 2017 * Staff and Council Chairs to work on agenda for GNSO Working session, Day 1 * Staff to relay hotel booking confirmation delays to Constituency Travel Item 10: ANY OTHER BUSINESS (5 minutes) 10.2 Update from Registrars Stakeholder Group (RrSG) on IRTP-C Change of Registrant issues in relation to implementation of the Privacy/Proxy Services Accreditation PDP recommendations * James Bladel to bring further clarification about the nature and scope of the informal discussion group the Board requested of the GNSO to the GNSO Council mailing list. Please note that all Action Items will be posted on the Action Item wiki page here<https://community.icann.org/x/RgZlAg>. Thank you, Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

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 May 22, 2017

May 22, 2017

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 May 22, 2017

May 22, 2017

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 May 22, 2017

May 22, 2017

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 May 19, 2017

May 19, 2017

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 May 18, 2017

May 18, 2017

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 May 18, 2017

May 18, 2017

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 May 18, 2017

May 18, 2017

*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 May 18, 2017

May 18, 2017

1 0

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

May 17, 2017

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 May 16, 2017

May 16, 2017

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

For your review - proposed Council response to CCWG-Accountability-WS2 - The Diversity Sub-Group of WS2 seeks your input on Diversity
by Marika Konings May 16, 2017

May 16, 2017

Dear All, As discussed, please find attached for your review a draft response to the survey prepared by the CCWG-Accountability WS2 – Diversity sub group. The draft responses are from the perspective of the Council / GNSO Working Group perspective, prepared by staff in collaboration with the Council leadership team. As noted in the response, it is the expectation that SG/Cs will complement these responses with information from their respective groups. You are encouraged to share any comments and/or edits on this draft with the Council mailing list by 26 May at the latest. The CCWG-Accountability has requested to receive this input by 1 June, so this would provide the Council leadership with sufficient time to assess what updates, if any, need to be made, and/or whether further discussion is needed prior to submission. Best regards, Marika On Thu, Apr 20, 2017 at 11:32 AM, Bernard Turcotte <turcotte.bernard(a)gmail.com<mailto:turcotte.bernard@gmail.com>> wrote: Dear Chairman Steve Crocker, CEO Goran Marby, NomCom Chair Hans Petter Holen and SO/AC Chairs, As you are aware, the newly-adopted ICANN bylaws tasked our Cross Community Working Group to investigate several issues as part of our Work Stream 2 effort. Diversity is one of these items. As part of this effort, we have set up a subgroup, responsible for reviewing how diversity is accommodated, supported and promoted within ICANN and to make recommendations to enhance diversity efforts. As part of this work, the group intends to inform itself by an assessment of the current situation. That’s why we are turning to you to provide input and point us to any resources and documents related to diversity in your respective group or designated community, taking into account the particular or specific working modalities of each group. We would appreciate if you could provide responses to the attached questions by 1 June 23:59UTC , so that work on this important item of WS2 can proceed as quickly as possible. Responses can be provided to ws2-diversity-questionnaire(a)icann.org<mailto:ws2-diversity-questionnaire@icann.org> Along with the rapporteurs of the Diversity subgroup, Fiona Asonga and Rafik Dammak, we thank you in advance and remain available for any clarification that you may need. Best regards, Leon, Thomas & Mathieu

1 0

Council Dinner in Johannesburg
by James M. Bladel May 16, 2017

May 16, 2017

Councilors – We are in need of a volunteer to assist Staff in planning our Council Dinner for Johannesburg. If anyone is familiar with the local restaurant scene, or generally interested in helping, please ping Nathalie off list. Our dinner in Copenhagen was tremendous, and at an award-winning restaurant (thanks Ed!), but I think there’s also some appeal to the more casual cocktails and snacks approach we took in Hyderabad. Either works for me. Thank you, J.

1 0

Copy of CCWG-IG charter in word doc
by Austin, Donna May 15, 2017

May 15, 2017

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

2 1

Notification of Board Seat 15 Selection
by Heidi Ullrich May 11, 2017

May 11, 2017

Dear Empowered Community Administration, cc. ICANN Secretary and Decisional Participants On behalf of the ALAC Chair, Alan Greenberg, please find attached a notification concerning the selection for Board Seat 15. Kind regards, Heidi Heidi Ullrich VP, Policy Development & At-Large Relations Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 437 - 3956 Fax: +1 (310) 823 - 8649 E-mail: Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

1 0

ICANN59 Informational Webinar - on Tuesday, 16 May 2017 at 1600 UTC
by Nathalie Peregrine May 11, 2017

May 11, 2017

Dear Community Leaders and Representatives: Please review this note from the ICANN Meetings Team: ICANN will be holding an informational webinar on Tuesday, 16 May 2017 at 1600 UTC to provide the community with a full update on ICANN59, including information on logistics, accommodations and travel. Details on the meeting schedule for Johannesburg will also be shared during the webinar, as well as being posted on the ICANN59 meeting website. The call is open for all to attend. The presentation and recording will be posted shortly after the conclusion of the webinar. How to participate: Link to Adobe Connect: https://participate.icann.org/community/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Listen Only or Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial-in Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=3535257619&num=1-605-… Participant Passcode: 353 525 7619 If you have questions, please email: mailto:meetings@icann.org -------------------------------------------------------- Tanzanica S. King Sr. Manager, Meeting Strategy and Design ICANN Office +1 310 301 5800 Mobile +1 310 995 3038 Email king(a)icann.org<mailto:king@icann.org> www.icann.org

1 0

ICANN News Alert -- The ICANN History Project Goes Live
by Nathalie Peregrine May 11, 2017

May 11, 2017

fyi [CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2-2017-05-04-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ The ICANN History Project Goes Live 4 May 2017 LOS ANGELES – 4 May 2017 – ICANN is pleased to announce the launch of the ICANN History Project. The project seeks to preserve ICANN's institutional memory by capturing stories from key figures who helped to shape the organization from its origins to the present day. To get started, visit www.icann.org/history[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_history&…>. There, you'll find interviews with key figures such as Ira Magaziner, former Senior Policy Advisor to President Bill Clinton; Larry Strickling, former Assistant Secretary for Communications and Information and Administrator, National Telecommunications and Information Administration, U.S. Department of Commerce; Vint Cerf, one of the "fathers of the Internet"; Dr. Stephen Crocker, ICANN Board Chair; and many other major players from ICANN's past. We're presenting the ICANN History Project through thematic tracks so that you can delve into the topics that interest you most. The first track focuses on ICANN's relationship with the United States Government, from the U.S. Government's role in the establishment and development of ICANN to the steps leading up to the Internet Assigned Numbers Authority (IANA) Stewardship Transition. If you want to contribute your own experiences to this project, we encourage you to share your ICANN memories with us. Send us a link to your blogs, videos or pictures via Twitter using the hashtag #ICANNHistory. If you have any questions, please email us at history(a)icann.org<mailto:history@icann.org>.

2 1

Proposed Final Agenda GNSO Council Meeting 18 May 2017 at 12:00 UTC
by Nathalie Peregrine May 10, 2017

May 10, 2017

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<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: 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__tally.icann.org_cgi_re…>). 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 (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-…<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<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<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 <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

New gTLD Subsequent Procedures PDP WG newsletter - May 2017
by Emily Barabas May 9, 2017

May 9, 2017

Dear all, On behalf of the leadership team of the New gTLD Subsequent Procedures PDP WG, I am writing to share the latest edition of the WG newsletter: https://gnso.icann.org/en/news/working-group-newsletters/newsletter-new-gtl…. Please feel free to share with individuals and groups who may be interested. Kind regards, Emily Emily Barabas | Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

MOTION-- GNSO Response to GAC Copenhagen Communique
by James M. Bladel May 8, 2017

May 8, 2017

Colleagues- Staff has informed me that this motion was withdrawn, rather than deferred, from our last call. As a result, it is necessary to resubmit the motion, along with the draft response document. Both are attached to this message. Thank you -- J. ------------------ James Bladel GNSO Chair

2 1

Electronic vote result: Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names
by Nathalie Peregrine May 8, 2017

May 8, 2017

Dear Councilors, The GNSO Council email vote on the motion on <https://community.icann.org/display/gnsocouncilmeetings/Motion+for+Electron…> the Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names (see: https://community.icann.org/x/fwLfAw) closed at 23:59 UTC on Sunday 7 May 2017. With 7 votes in favor in the Contracted Party House, and 11 votes in favor in the Non-Contracted Party House, 1 abstention and 1 late apology, the motion passes with 100% votes in favor in the CPH and 84,62% in favor in the NCPH. Please find the results attached and at the url below: https://tally.icann.org/cgi/results?e=1876ca1df15 There were 20 eligible voters, 19 voters expressed their vote (one vote was a duplicate). The resolutions from this vote will be posted on page: http://gnso.icann.org/en/council/resolutions Thank you for your cooperation in completing the vote. Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

2 2

MOTION - GNSO Validation of CCWG-Accountablity WS2 Request for Extension of Mandate and Budget for FY2018
by James M. Bladel May 8, 2017

May 8, 2017

Councilors – Attached and copied below, please find a motion for your consideration during our 18 MAY 2017 meeting. I have not received any questions or oppositions to this issue on the mailing list, and a few Councilors have responded with support. Therefore, I’m proposing that this motion be slated for our Consent Agenda. Should any Councilor wish to discuss or amend this motion, we can move it off the Consent Agenda during our call. Thank you, J. _______________________ GNSO validation of the CCWG-Accountability-WS2 request for extension of mandate and funding for FY18 WHEREAS, 1. The CCWG-Accountability-WS2 funding for FY17 was part of the FY17 Transition budget which was funded from ICANN’s reserve fund for a total of 8.8M$. 2. The CCWG-Accountability-WS2 confirmed at its face to face meeting at ICANN 58 in Copenhagen that it would not be able to complete its work by the end of FY17 as originally planned. 3. In working on estimating the cost of the WS2 extension for FY18 with the PCST and ICANN Finance the CCWG-Accountability-WS2 published the CCWG-Accountability-WS2 FY18 Expense Forecast and Assumptions (see Annex B<http://mm.icann.org/pipermail/council/attachments/20170427/c2d53b7e/CCWG-Ac…>) which estimates that the extension of WS2 for all of FY18, including all costs of the Transition for FY17, would still remain within the original Transition budget. 1. The CCWG-Accountability-WS2 chairs submitted a request to the GNSO, as one of the chartering organizations of the CCWG-Accountability-WS2, to support the extension of its mandate and funding for all of FY18 (see https://mm.icann.org/pipermail/council/2017-April/019936.html) 2. In considering this request the GNSO notes that the funding for the Transition budget was from the ICANN reserve fund and that any extension of the CCWG-Accountability-WS2 for FY18 should also be funded similarly and as such would not impact the standard operating budget for FY18. 3. The GNSO Council has discussed and reviewed all the relevant materials. RESOLVED, 1. The GNSO Council hereby supports the CCWG-Accountability-WS2 request for an extension of its mandate and funding for FY18. 2. The GNSO Council expects to receive regular updates on actual expenditures as tracked against this adopted budget, as well as the status of WS2 activities. Additionally, the GNSO Council reserves the right to provide further input on the budget allocation in relation to the CCWG-Accountability related activities in FY18. 3. The GNSO Council expects ICANN staff, including its office of General Counsel, to continue to provide the assistance requested by the CCWG and its working groups in an expeditious, comprehensive, and unbiased manner. 4. The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of the approved budget, and that excess costs or requests for additional funding beyond said budget should be recommended by the Legal Committee only when deemed essential to completion of the CCWG's work and objectives. 5. The GNSO Council requests the GNSO Secretariat to communicate this resolution to the CCWG-Accountability Chairs, and to the office of the ICANN CFO.

1 0

Reminder: Document and Motion deadline Monday, 8 May 2017 at 23:59 UTC for the GNSO Council Meeting 18 May 2017 at 12:00 UTC
by Nathalie Peregrine May 8, 2017

May 8, 2017

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 8 May 2017 at 23:59 UTC) of the GNSO Council Meeting on 18 May 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/eQLfAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Notification of Board Seat 14 Selection
by Marika Konings May 5, 2017

May 5, 2017

Dear Empowered Community Administration, cc. ICANN Secretary and Decisional Participants On behalf of the GNSO Chair, James Bladel, please find attached a notification concerning the selection for Board Seat 14. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Reminder: Update: Notification of Electronic vote: Motion to Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names: 3 May 2017 - 7 May 2017
by Nathalie Peregrine May 5, 2017

May 5, 2017

Dear all, Please note that the electronic vote closes on Sunday 7 May 2017 at 23:59 UTC. Have a lovely weekend! Kind regards Nathalie From: <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, May 3, 2017 at 9:54 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Update: Notification of Electronic vote: Motion to Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names: 3 May 2017 - 7 May 2017 Dear Councilors, The GNSO Council email ballot on the motion to initiate a policy amendment process of specific Red Cross Names will be launched shortly. Considering the friendly amendment made to Resolved Clause 2, (please see updated motion here: (https://community.icann.org/x/fwLfAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>) which has been accepted by the Motion seconders, the electronic vote will now start a day later. The vote opens at 23:59 UTC on Wednesday 3 May 2017 and closes at 23:59 UTC on Sunday 7 May 2017. Please make sure that you receive your ballot, from tally(a)icann.org<mailto:tally@icann.org>, and if you do not please let me know immediately: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please remember that if you are off email, you can cast your vote by voice, but please provide me with a telephone number before 1 May. Please be sure to mark only one response: · In favour, · Not in favour, · Abstain Please also note the following applicable procedures: o The Operating Procedures do not permit absentee voting for either motion. Under Section 4.5 of the GNSO Operating Procedures, an abstention counts as a vote “not in favour”. The ballot includes a text box for you to state your reason(s) if you wish, should you decide to abstain from voting on either motion. o The voting threshold required for the motion to pass successfully is a simple majority of the Council. o In accordance with the rules for a vote outside a Council meeting, this ballot will be an open vote (i.e. not secret) and we will record and publish the outcomes as required by the GNSO Operating Procedures. Please let me know if you have any questions. Thank you. Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FW: notice re RySG Secretariat
by James M. Bladel May 5, 2017

May 5, 2017

Councilors, FYI – Please see below for an announcement from the Registry Stakeholder Group. Thank you, J. From: <2017-cph-excoms(a)googlegroups.com> on behalf of Paul Diaz <pdiaz(a)pir.org> Date: Friday, May 5, 2017 at 8:05 Subject: FW: notice re RySG Secretariat FYI – please share with your colleagues as appropriate From: regycon(a)googlegroups.com [mailto:regycon@googlegroups.com] On Behalf Of Paul Diaz Sent: Thursday, May 04, 2017 2:25 PM Cc: rysg.operations.coord(a)gmail.com; rysgsecretariat(a)gmail.com Subject: [REGYCON] notice re RySG Secretariat As most of you are aware, Cherie Stubbs informed the RySG Executive Committee at ICANN 57 (Hyderabad) that she intended to pare back her duties. Cherie has been the Secretariat for 16+ years, and has provided the critical support and structure to meet the day-to-day needs of the membership and leadership. This became an even bigger challenge with the launch of the new gTLDs 5 years ago when we found ourselves going from a steady state of 14 members with two dozen participants to over 100 members and 200+ participants. Cherie has brought the administrative and organizational strength we needed to make this journey, but now wants to pursue a different course. After numerous discussions and planning, we started implementing a transition plan following ICANN 58 (Copenhagen). I’m pleased to report that Cherie will continue to support the RySG, but in a different capacity. Moving forward, Cherie Stubb’s new role will be as RySG Operations Coordinator, and will oversee key internal RySG business and operations needs. A description of those duties follows. Cherie’s new email address will be rysg.operations.coord(a)gmail.com<mailto:rysg.operations.coord@gmail.com>; please update your records. I’m also pleased to report that Sue Schuler has stepped into the RySG Secretariat role. Sue was hired as the RySG Data Management Assistant about 2 ½ years ago, and her responsibilities have expanded since then. Besides managing membership tracking/rosters and dues invoicing, Sue helped design and manages the updated RySG website. She also has been attending in-person meetings and, through Cherie's mentoring, is now supporting the RySG membership’s needs. Sue already has taken the lead on coordinating the RySG bi-weekly conference calls, and provides support to the majority of other RySG working groups. A description of Sue’s new responsibilities follows. Moving forward, Sue will use the rysgsecretariat(a)gmail.com<mailto:rysgsecretariat@gmail.com> address; please update your records. My summary of Cherie’s and Sue’s duties are by no means exhaustive. We expect that there will be cross over and cross support as they’re both committed to assuring that the overall needs of the RySG are met. That said, please don't hesitate to contact me, any other member of the Executive Committee, or Cherie and Sue if you have any questions about these points. Best, Paul Diaz Chair, RySG __

1 0

FW: [CCWG-ACCT] Fwd: CCWG-Accountability-WS2-Extension-SubmissiontoCharteringOrganzations
by James M. Bladel May 5, 2017

May 5, 2017

Councilors – Please see attached for a request from the CCWG-ACCT co-chairs. Synopsis: The CCWG-ACCT will not complete its work on Workstream 2 (WS2) before the end of FY2017 in June. They are requesting an extension of this work, and to carry funding for WS2 forward in to the FY2018 budget. Let’s discuss our response, if any. Thank you, J. From: <accountability-cross-community-bounces(a)icann.org> on behalf of Bernard Turcotte <turcotte.bernard(a)gmail.com> Date: Thursday, April 27, 2017 at 8:46 To: Accountability Cross Community <accountability-cross-community(a)icann.org> Subject: [CCWG-ACCT] Fwd: CCWG-Accountability-WS2-Extension-SubmissiontoCharteringOrganzations All, Please find below the message from the Co-Chairs to the Chairs of the CCWG-Accountability Chartering Organizations requesting an extension of WS2 for all of FY18. Bernard Turcotte ICANN Staff Support to the CCWG-Accountability-WS2 ---------- Forwarded message ---------- From: Bernard Turcotte <turcotte.bernard(a)gmail.com<mailto:turcotte.bernard@gmail.com>> Date: Thu, Apr 27, 2017 at 9:44 AM Subject: CCWG-Accountability-WS2-Extension-SubmissiontoCharteringOrganzations To: soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> Cc: "Thomas Rickert (thomas(a)rickert.net<mailto:thomas@rickert.net>)" <thomas(a)rickert.net<mailto:thomas@rickert.net>>, Mathieu Weill <mathieu.weill(a)afnic.fr<mailto:mathieu.weill@afnic.fr>>, León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx<mailto:leonfelipe@sanchez.mx>>, Jordan Carter <jordan(a)internetnz.net.nz<mailto:jordan@internetnz.net.nz>>, "ACCT-Staff (acct-staff(a)icann.org<mailto:acct-staff@icann.org>)" <acct-staff(a)icann.org<mailto:acct-staff@icann.org>> Chairs of the CCWG-Accountability-WS2 Chartering Organizations (ALAC, ASO, ccNSO, GAC, gNSO, SSAC), Please find attached a request from the CCWG-Accountability-WS2 to extend its mandate and funding for all of FY18 so it can complete its work. The CCWG-Accountability-WS2 Co-Chairs would welcome your approval or support for this request prior to the finalization of the ICANN FY18 budget and remain at your disposal to provide any additional information or presentations you should require in considering this request. CCWG-Accountability-WS2 Co-Chairs Thomas Rickert, Mathieu Weill and Leon Sanchez.

5 6

FW: [soac-chairs] Participation of the ccNSO in the RDS-WHOIS2 review
by James M. Bladel May 5, 2017

May 5, 2017

Councilors – See below and attached for a message from Katrina Sataki, regarding the ccNSO’s participation in RDS-RT. Thank you, J. From: <soac-chairs-bounces(a)icann.org> on behalf of Katrina Sataki <katrina(a)nic.lv> Date: Tuesday, May 2, 2017 at 11:14 To: 'Steve Crocker' <steve.crocker(a)board.icann.org> Cc: "goran.marby(a)icann.org" <goran.marby(a)icann.org>, "ccnso-council(a)icann.org" <ccnso-council(a)icann.org>, 'Chris Disspain' <chris(a)disspain.uk>, 'Mike Silber' <mike.silber(a)board.icann.org>, SO-AC Chairs List <soac-chairs(a)icann.org> Subject: [soac-chairs] Participation of the ccNSO in the RDS-WHOIS2 review Dear Steve: As, according to Section 4.6 (e) of the Bylaws, the Board caused the Registration Directory Service (RDS-WHOIS2) review, I convey to you the ccNSO Council decision with respect to participation of the ccNSO in this review. As always, the ccNSO Council is available to explain its position. Kindest regards, Katrina Sataki Chair of the ccNSO Council

2 3

FW: [SOAC-Leaders] Home | ICANN Public Meetings
by James M. Bladel May 5, 2017

May 5, 2017

For anyone who hasn’t already seen this announcement regarding ICANN62 in Panama… J. From: <soac-leaders-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Wednesday, May 3, 2017 at 2:01 Subject: [SOAC-Leaders] Home | ICANN Public Meetings https://meetings.icann.org/en/ Recent Announcements Date Change for ICANN62 in June 2018 to be held in Panama<https://www.icann.org/news/announcement-2017-05-02-en> The ICANN Board has approved Panama as the location in Latin America to host ICANN's 62nd public meeting. Previously scheduled for the week of 18 June, this Policy Forum has been moved to 25-28 June to respect the Muslim Eid al-Fitr holiday... 02 May 2017 ICANN Publishes ICANN58 By the Numbers Report<https://www.icann.org/news/announcement-2-2017-04-24-en> Today, ICANN published the results of the ICANN58 By the Numbers report that details the technical, demographic and attendance statistics. This report summarizes our statistical data from ICANN's second Community Forum of the new meeting strategy.... 24 April 2017 Puerto Rico and Barcelona Identified as ICANN Meeting Sites for 2018<https://www.icann.org/news/announcement-2-2016-12-22-en> 22 Dec 2016 MORE ANNOUNCEMENTS FOR ICANN MEETINGS ><https://meetings.icann.org/en/announcements> ________________________________ [https://meetings.icann.org/sites/default/files/standards_of_behavior_button…]<https://www.icann.org/sites/default/files/assets/expected-standards-22aug16…> Click here<https://www.icann.org/news/announcements> for ICANN announcements. Latest blog posts can be found here<https://www.icann.org/news/blog>. Are you a Journalist? Find helpful information here.<https://www.icann.org/resources/pages/press-2014-03-17-en> ________________________________ Up Next: [https://meetings.icann.org/sites/default/files/resize/dark_blue-275x156.png]<https://meetings.icann.org/en/johannesburg59> Hosted by Sent from my iPhone David A. Olive Senior Vice President, Policy Development Support Managing Director, ICANN Regional Headquarters –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) Direct Line: +90.212.999.6212<tel:+90.212.999.6212> Mobile: + 1. 202.341.3611<tel:+%201.%20202.341.3611> Mobile: +90.533.341.6550<tel:+90.533.341.6550>

1 0

FW: [SOAC-Leaders] Fwd: SOACs Feedback on the Draft Gender Diversity & Participation Survey by 20 May
by James M. Bladel May 5, 2017

May 5, 2017

Councilors, see below. ICANN Staff is preparing a community-wide survey on Gender Diversity and Participation. Before the survey launches, they are seeking feedback from SO/ACs on the draft (linked below). Please review, and submit any thoughts or comments you’d like to share on this upcoming survey. Thank you, J. From: <soac-leaders-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Wednesday, May 3, 2017 at 16:08 Cc: Sally Costerton <sally.costerton(a)icann.org>, Ergys Ramaj <ergys.ramaj(a)icann.org> Subject: [SOAC-Leaders] Fwd: SOACs Feedback on the Draft Gender Diversity & Participation Survey by 20 May Ergys Ramaj Dear Community Leaders: Please review this message from Sr. Director, Public Responsibility As you are aware, the ICANN organization is planning to launch a survey on Gender Diversity and Participation in the ICANN community. The purpose is to determine current perceptions of gender diversity within the ICANN community and to identify potential barriers to participation. The document has gone through several rounds of reviews and is ready to be shared with SOACs for additional input. One important point is to clarify how this survey is different and/or complements the work currently taking place in the Work Stream 2 (WS2) Diversity subgroup<https://community.icann.org/display/WEIA/Diversity>. The questionnaire recently sent to the SOACs by the WS2 Diversity subgroup focuses specifically on SOACs current processes and procedures. On the other hand, the Gender Diversity and Participation survey aims to assess perceptions about gender and participation across all of the ICANN community. It also focuses specifically on gender as one aspect of diversity, following community calls for data pertaining specifically to gender. Other elements of diversity are being discussed in the WS2 Diversity subgroup and may be explored with future surveys. Before we launch the survey, we would appreciate feedback from the SOACs by 20 May 2017. The current draft has benefitted from insights and input provided by members of the ICANN organization, Board, and WS2 Diversity subgroup. Here is a link to the survey: https://docs.google.com/document/d/1kEd5LMwMiKau0skX-MGBOZd6BFgcQTq6qdvHA40… — Comments/suggestions/questions could be made on the document or emailed directly to me. Shortly following SOACs review, the survey will be advertised across the community. Responses will be anonymous, and survey responses will be used in accordance with ICANN’s Privacy Policy<https://www.icann.org/resources/pages/privacy-2012-12-21-en>. The data will be analyzed to identify perceived gaps, trends, and potential next steps; a final report with the findings will be widely disseminated, and next steps will be up to the community. Looking forward to any thoughts you may have and many thanks in advance. Best, Ergys

1 0

GAC/Board discussion about Copenhagen Communique
by Austin, Donna May 4, 2017

May 4, 2017

Hi All This from the GAC website. 27 April 2017 GAC and ICANN Board conference call recording<http://ftp.adigo.com/clients/icann/20170427_GAC_ICANN_Board.zip> Adobe Connect recording<https://participate.icann.org/p34pzh2hdws/?OWASP_CSRFTOKEN=b58fa272a54279dc…> Call Notes<https://gacweb.icann.org/download/attachments/27132037/NOTES%20OF%20BOARD%2…> Unfortunately, it would appear that our input on the GAC communique was too late to be taken into account for these discussions, which are only intended to be an opportunity for the Board to better understand the communique before preparing their formal response. However, I expect that the Board will consider the GNSO Council input when developing their response to the GAC communique. Donna

1 0

Reminder: Document and Motion deadline Monday, 8 May 2017 at 23:59 UTC for the GNSO Council Meeting 18 May 2017 at 12:00 UTC
by Nathalie Peregrine May 4, 2017

May 4, 2017

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 8 May 2017 at 23:59 UTC) of the GNSO Council Meeting on 18 May 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/eQLfAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Re: [council] Board Seat #14 Election
by Marika Konings May 4, 2017

May 4, 2017

Paul, we are trying to confirm what is at a minimum required under the new ICANN Bylaws. In the past both a communication as well as the adoption of a motion have been used to confirm the nomination. Now the GNSO Chair also needs to notify the EC Administration in addition to the ICANN Board Secretary. In case a motion is required, it will obviously need to wait until the next Council meeting which has been scheduled for 18 May. If a letter from the GNSO Chair is sufficient, following the notification that has been received from the NCPH, staff can work with James to get this done as soon as possible. Best regards, Marika On 5/3/17, 19:04, "council-bounces(a)gnso.icann.org on behalf of icannlists" <council-bounces(a)gnso.icann.org on behalf of icannlists(a)winston.com> wrote: Do we need a GNSO Motion to make this formal, or does it just happen? If so, is today the deadline? Best, Paul -----Original Message----- From: council-bounces(a)gnso.icann.org [mailto:council-bounces@gnso.icann.org] On Behalf Of James M. Bladel Sent: Wednesday, May 03, 2017 2:30 PM To: GNSO Council List <council(a)gnso.icann.org> Subject: [council] FW: Board Seat #14 Election Councilors – Please see below for an announcement from Tapani. Thank you, J. On 5/3/17, 7:47 , "Tapani Tarvainen" <ncsg(a)tapani.tarvainen.info> wrote: Dear James, On behalf of NCPH I'd like to inform you that NCPH has elected Matthew Shears <matthew(a)intpolicy.com> to the Board, replacing Markus Kummer on seat #14. The election was conducted by vote among NCPH councillors, with the following result: Total Ballots Cast (including duplicates): 13 Ballots Counted (excluding duplicates): 12 Voters Who Haven't Voted: 1 Board Seat 14 1: 11 votes [] Matthew Shears 2: 1 vote [] Markus Kummer 3: 0 votes [] Abstain Sincerely, Tapani Tarvainen Non-Commercial Stakeholder Group Chair _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations. _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

2 1

Path forward for CCWG-IG
by James M. Bladel May 4, 2017

May 4, 2017

Colleagues – At our meeting at ICANN57 (Hyderabad) the GNSO Council extended its support as a Chartering Organization for this CCWG, but tasked the leadership of this group to review its charter, and come to ICANN58 (Copenhagen) with a report of its findings and, potentially, a revised charter. (https://gnso.icann.org/en/council/resolutions#20161107-3) As a result, the CCWG presented an updated charter shortly before our meeting in Copenhagen, but the Council did not have sufficient time to consider it during our Public Meeting at ICANN58 (http://mm.icann.org/pipermail/council/2017-March/019816.html) Finally, we briefly discussed this topic during our last meeting on 20 APR, but no action was taken. (https://gnso.icann.org/en/meetings/agenda-council-20apr17-en.htm, Item #8). I propose that we target our next meeting (18 MAY) for a decision on this revised charter, and the GNSO’s continued participation as a Chartering Organization in the CCWG. With this in mind, I ask all Councilors to discuss the revised charter with their respective SG/C (and here on the Council list) with the goal of submitting a relevant motion supporting or withdrawing from this CCWG by our Motion & Document deadline (currently 8 MAY). Thank you, J.

4 5

MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names
by James M. Bladel May 4, 2017

May 4, 2017

Councilors – Attached and copied below, please find an amended version of the Motion to Initiate Policy Amendment Process on Specific Red Cross Names that was discussed during our last meeting. Recall that, during our last GNSO Council call on 20 April, the Council agreed to defer this Motion to an electronic vote, in order to allow for certain updates to be made to the text of the motion. Also note that the Council agreed to proceed with an electronic vote outside a regularly scheduled Council meeting. The updated language of the motion has been reviewed and approved by me as its proposer, and Michele and Rubens as its seconders. It includes some minor clarifications received as feedback from the ICRC representatives, but does not include any items that materially changed the scope of the affected strings, or any other items that were not discussed previously in Copenhagen. This email will also serve as notice that, as Council Chair, I am hereby formally providing all Councilors with the requisite minimum 7 days’ advance notice of the electronic vote, in accordance with Section 4.10.2.d. of the GNSO Operating Procedures (https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf) The 4-day voting period will begin at 23:59 UTC on Tuesday 2 May 2017 and close at 23:59 UTC on Saturday 6 May 2017. (Please be reminded that the GNSO Operating Procedures require that electronic voting be an open vote, and its outcome be published and recorded, with accompanying voter statements, if any, as minutes for purposes of formal record keeping.) Thank you, J. ------------------ James Bladel GNSO Chair _______________________ Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names - Deferred to electronic vote Submitted by: James Bladel Seconded: Rubens Kuhl, Michele Neylon WHEREAS, in November 2013, the GNSO completed a Policy Development Process (PDP) which resulted in a number of consensus recommendations for protecting the identifiers of International Governmental Organizations and International Non-Governmental Organizations, including the International Red Cross and Red Crescent Movement (Movement), at the top and second level in all generic top-level domains (gTLDs) (PDP Working Group Final Report: https://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf, with Minority Statements: https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13-…<https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13-…)>); WHEREAS, the GNSO Council approved all the PDP consensus recommendations on 20 November 2013 (http://gnso.icann.org/en/council/resolutions#20131120-2<http://gnso.icann.org/en/council/resolutions#20131120-2)>) and, following a mandatory public comment period on the final PDP recommendations, sent its Recommendations Report to the ICANN Board on 23 January 2014 (https://gnso.icann.org/en/issues/council-board-igo-ingo-23jan14-en.pdf<https://gnso.icann.org/en/issues/council-board-igo-ingo-23jan14-en.pdf)>); WHEREAS, on 30 April 2014 the Board adopted those of the GNSO’s PDP recommendations that were consistent with GAC advice on the topic, which in relation to the Movement were for the terms “Red Cross”, “Red Crescent”, “Red Crystal”, and “Red Lion & Sun” (referred to as “Scope 1 Identifiers” by the PDP Working Group) to be reserved at the top and second levels, with an Exception Procedure to be designed for the affected organization (http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2…<http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2…)>); WHEREAS, between June 2014 and January 2015 the Board and the GNSO Council engaged in discussions of the remaining inconsistencies between GAC advice and GNSO policy, which in relation to the Movement concerned the names of 189 National Red Cross and Red Crescent Societies, and the names and acronyms of the International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies (referred to as “Scope 2 Identifiers” by the PDP Working Group); WHEREAS, at ICANN57 in November 2016 the Board proposed that the GAC and the GNSO engage in a facilitated, good faith discussion to attempt to resolve the remaining inconsistencies between GAC public policy advice and GNSO consensus policy recommendations regarding the “Scope 2 Identifiers” of the Movement; WHEREAS, representatives from the GAC and the GNSO engaged in such a facilitated, good faith discussion at ICANN58 in March 2017 during which the following matters were noted: (1) The public policy considerations associated with protecting the Movement’s identifiers in the domain name system (DNS); (2) The GAC’s rationale for seeking permanent protection for the terms most closely associated with the Movement and its respective components is grounded in the protections of the designations “Red Cross”, “Red Crescent”, “Red Lion and Sun”, and “Red Crystal” under international treaty law and under multiple national laws; (3) The list of names of the Red Cross and Red Crescent National Societies is a finite, limited list of specific names of the National Societies recognized within the Movement (http://www.ifrc.org/Docs/ExcelExport/NS_Directory.pdf ); (4) There are no other legitimate uses for these terms; and (5) The GAC had provided clarification following the completion of the GNSO PDP, via its March 2014 Singapore Communique, on the finite scope of the specific list of Movement names for which permanent protections were being requested (https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…<https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…)>); WHEREAS, following the GAC-GNSO discussion, the Board passed a resolution on 16 March 2017 requesting that the GNSO initiate its process for Amendments or Modifications of Approved Policies, as described in Section 16 of the GNSO PDP Manual (https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf<https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf)>), to consider amending the GNSO’s approved policy concerning the specific names of the Red Cross and Red Crescent National Societies and the specific names International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies (collectively, Recommendation 5 in Section 3.1 of the PDP Working Group Final Report): and WHEREAS, the GNSO Council agrees that the aforementioned set of exceptional circumstances provides a justifiable basis for the Council to take this extraordinary step to reconsider the policy recommendation and that this is not to be viewed as the Council’s consent to reopen PDP recommendations in all cases where GNSO-developed policy is in discord with GAC advice: RESOLVED, 1.The GNSO Council hereby initiates the process described in Section 16 of the GNSO PDP Manual; accordingly, the GNSO Council requests that the PDP Working Group be reconvened for the purpose of consultation by the GNSO Council on the following proposed amendment to Recommendation 5 in Section 3.1 of the PDP Working Group Final Report: (a) The full names of the 190 Red Cross National Societies and the full names of the International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies are to be placed into Specification 5 of the Base gTLD Registry Agreement, with an exception procedure to be created for cases where the relevant Red Cross Red Crescent Movement organization wishes to apply for their protected string at the second level; (b) In placing the specified identifiers into Specification 5 of the Registry Agreement, this should apply to an exact match of the full name of the relevant National Society recognized within the International Red Cross and Red Crescent Movement (in English and the official languages of its state of origin), the full names of the International Committee of the Red Cross and of the International Federation of Red Cross and Red Crescent Societies (in the six official United Nations languages) and a defined limited set of variations of these names; and (c) In considering the proposed amendment, account is to be duly taken of the matters noted during the GAC-GNSO facilitated discussion at ICANN58 as well as of the GAC’s public policy advice to reserve the finite list of names of the Red Cross and Red Crescent National Societies, as recognized within the International Red Cross and Red Crescent Movement, in all gTLDs. 2. In accordance with Section 16 of the PDP Manual, the GNSO Council directs ICANN staff to post the proposed amendment to Recommendation 5 for public comment, for a period of 30 days commencing from the date of the first meeting of the reconvened PDP Working Group. 3. In accordance with Section 16 of the PDP Manual, the GNSO Council intends to put the proposed amendment to a vote following consultation with the PDP Working Group and the conclusion of the requisite public comment period. The GNSO Council notes that approval of the proposed amendment requires a Supermajority Vote of both Houses in favour of the amendment. 4. The Council thanks all of those who participated in the talks at ICANN58 in Copenhagen, and in particular Bruce Tonkin for moderating the discussion.

7 11

FW: Board Seat #14 Election
by James M. Bladel May 4, 2017

May 4, 2017

Councilors – Please see below for an announcement from Tapani. Thank you, J. On 5/3/17, 7:47 , "Tapani Tarvainen" <ncsg(a)tapani.tarvainen.info> wrote: Dear James, On behalf of NCPH I'd like to inform you that NCPH has elected Matthew Shears <matthew(a)intpolicy.com> to the Board, replacing Markus Kummer on seat #14. The election was conducted by vote among NCPH councillors, with the following result: Total Ballots Cast (including duplicates): 13 Ballots Counted (excluding duplicates): 12 Voters Who Haven't Voted: 1 Board Seat 14 1: 11 votes [] Matthew Shears 2: 1 vote [] Markus Kummer 3: 0 votes [] Abstain Sincerely, Tapani Tarvainen Non-Commercial Stakeholder Group Chair

2 1

FW: [soac-chairs] Jordan Carter - ccNSO appointed co-chair of the CCWG-Accountability
by James M. Bladel May 3, 2017

May 3, 2017

Councilors – See below for an announcement from Katrina: The ccNSO has appointed Jordan Carter (.NZ) to replace Mathieu. Thank you, J. From: <soac-chairs-bounces(a)icann.org> on behalf of Katrina Sataki <katrina(a)nic.lv> Date: Wednesday, May 3, 2017 at 8:17 Subject: [soac-chairs] Jordan Carter - ccNSO appointed co-chair of the CCWG-Accountability Dear Thomas and Leon, As you know, the ccNSO Council received a letter of resignation from Mathieu Weill effective 28 April. In his letter Mathieu announced that he was stepping down from the position of the ccNSO appointed co-chair of the CCWG Accountability. I am pleased to inform you that the ccNSO Council has asked Jordan Carter (.nz) to replace Mathieu as the ccNSO appointed co-chair of the CCWG Accountability effective immediately, and Jordan kindly accepted the challenge. As to the replacement of Mathieu as a member of the CCWG, we will inform you at a later stage after we have concluded our call for volunteer process. On behalf of the ccNSO Council, ]{atrina Sataki Chair

1 0

Update: Notification of Electronic vote: Motion to Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names: 3 May 2017 - 7 May 2017
by Nathalie Peregrine May 3, 2017

May 3, 2017

Dear Councilors, The GNSO Council email ballot on the motion to initiate a policy amendment process of specific Red Cross Names will be launched shortly. Considering the friendly amendment made to Resolved Clause 2, (please see updated motion here: (https://community.icann.org/x/fwLfAw) which has been accepted by the Motion seconders, the electronic vote will now start a day later. The vote opens at 23:59 UTC on Wednesday 3 May 2017 and closes at 23:59 UTC on Sunday 7 May 2017. Please make sure that you receive your ballot, from tally(a)icann.org<mailto:tally@icann.org>, and if you do not please let me know immediately: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please remember that if you are off email, you can cast your vote by voice, but please provide me with a telephone number before 1 May. Please be sure to mark only one response: · In favour, · Not in favour, · Abstain Please also note the following applicable procedures: o The Operating Procedures do not permit absentee voting for either motion. Under Section 4.5 of the GNSO Operating Procedures, an abstention counts as a vote “not in favour”. The ballot includes a text box for you to state your reason(s) if you wish, should you decide to abstain from voting on either motion. o The voting threshold required for the motion to pass successfully is a simple majority of the Council. o In accordance with the rules for a vote outside a Council meeting, this ballot will be an open vote (i.e. not secret) and we will record and publish the outcomes as required by the GNSO Operating Procedures. Please let me know if you have any questions. Thank you. Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Timing of Vote (Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names)
by Mary Wong May 3, 2017

May 3, 2017

Dear all, Following consultation with James as the GNSO Chair, staff will hold off from sending out ballots for the electronic vote on this motion for at least the next 24 hours. This step is being taken to allow Michele and Rubens, as seconders of the motion, to indicate whether or not they accept the proposed amendment (below) as friendly, and Paul and others to provide follow up comments. Michele and/or Rubens – please note, and thank you. Thanks and cheers Mary From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Tuesday, May 2, 2017 at 18:56 To: icannlists <icannlists(a)winston.com>, Mary Wong <mary.wong(a)icann.org>, Rafik Dammak <rafik.dammak(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] [Ext] Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Paul – The process outlined in Section 16 ultimately leaves the decision to the Council on whether/how to amend a previous PDP, taking in to account input from Public Comment and in consultation with the previous PDP working group. But as I noted below, it isn’t our intention to “fix” the PDP’s recommendations with the language in the motion, but instead to give some guidance to the re-convened PDP working group, and for the Public Comment and Council to consider their recommended amendments (if any). I can see your concern is that, if we hold a comment period on the proposed amendment in the motion, while at the same time asking the PDP WG to reconvene and consider this same language, it gives the perception that the PDP WG is simply being asked to rubber stamp the predetermined outcome. And this was not the intention behind including the amendment in the motion. To make this explicitly clear, I’m proposing that we delay the Public Comment period on the proposed motion until –after- the reconvened PDP WG has delivered their recommendations. This would change Resolved #2 to read: 2. In accordance with Section 16 of the PDP Manual, the GNSO Council directs ICANN staff to post the recommendations of the reconvened PDP Working Group, and its proposed amendment(s) to Recommendation 5, if any, for public comment for a period of 30 days following the conclusion of the PDP WG. Please indicate whether this address your/IPC concerns, and I’ll ask that the Seconders consider this amendment as Friendly. Thank you, J. From: icannlists <icannlists(a)winston.com> Date: Tuesday, May 2, 2017 at 16:43 To: Mary Wong <mary.wong(a)icann.org>, "James M. Bladel" <jbladel(a)godaddy.com>, Rafik Dammak <rafik.dammak(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: RE: [council] [Ext] Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Thanks Mary. James, the concerns we are hearing from our folks deal with whether or not the work of the revived WG will be taken seriously. The motion seems to indicate that the public comment period for the work of the Small Group will run simultaneously with the work of the revived WG. What is the WG comes to conclusions which are not consistent with the Small Group’s conclusions? Will the WG’s conclusions be given full weight? Is there any mechanism for the work of the revived WG to be published for comment? If not, why would revived WG members cooperate if they are just going to be expected to be a rubber stamp? Best, Paul From: council-bounces(a)gnso.icann.org [mailto:council-bounces@gnso.icann.org] On Behalf Of Mary Wong Sent: Wednesday, April 26, 2017 5:52 PM To: James M. Bladel <jbladel(a)godaddy.com>; Rafik Dammak <rafik.dammak(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] [Ext] Re: MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Hello everyone – staff confirms James’ understanding of when and how the limited set of variations of the 190 Red Cross National Society names. The desire to have a single, limited list of specific variants of those 190 names is hopefully reflected in the language of the Board request as well as the current GNSO Council motion. Regarding the number of Red Cross National Societies: The number 189 was used in the Whereas clauses of the motion because there were 189 such societies at the time. The 190th Red Cross National Society (Tuvalu) only became part of the International Red Cross Red Crescent Movement in December 2015. In this regard, Councilors may find it helpful to know that stringent criteria apply to the formation and recognition of a Red Cross National Society. For example, it can only be formed in a State that is party to the Geneva Conventions (currently, 196), and it must be formally recognized by the International Committee of the Red Cross in order to become a component of the Movement. Perhaps one way to avoid confusion is to use the phrase “then-189” in the Whereas clauses and “now-190” in the Resolved portion? On the motion: As James noted, this motion covers the kick-off of the potential amendment process. At the end of the consultations with the reconvened PDP Working Group and following review of the public comments received, the Council will still have to vote on whether to adopt the proposed amendment – and that motion can carry only by Supermajority vote. I hope this is helpful. Cheers Mary From: <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Date: Wednesday, April 26, 2017 at 11:30 To: Rafik Dammak <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [Ext] Re: [council] MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Hello Rafik. I’ll try to address your questions below, but hoping Staff (Mary) will correct me if I get something wrong. A tighter definition for “limited set of variations” will be part of the work of the amendment (if any) resulting from the reconstituted PDP WG. But speaking generally, we noted that some groups had a formal name that was significant different than the name that it used commonly online For example, a national organization might be formally recognized as “The Red Cross of Canada” but was more commonly known as “Canadian Red Cross.” (example only, I have no idea if this organization fits the problem statement). The idea is that definitive articles and prepositions like “The” or “of” may or may not be included in the formal name, or dropped from the common name. Note that this is different than language variations / translations, and is significantly less than what the GAC/ICRC was requesting (which was a much larger list of variants and all permutations). As for the shift in numbers: The original PDP was focused on 189 organizations, but we were informed in Copenhagen that a new org was recently recognized, bringing the current number to 190. I agree that we should standardize all language on this latter figure. Good catch. And finally, a note for all Councilors: As you discuss this motion amongst your SG/C, please remind them that all we are considering is a motion that initiates a process, and that this process includes additional deliberations of the PDP WG, a Public Comment period, and a final Council vote on any resulting recommendations, assuming they differ from the original PDP conclusions. It is therefore not necessary (and perhaps not appropriate) to try and “fix” these concerns in the motion itself. But instead, the motion should launch the process, and the process can address the more substantive questions & concerns. In short, let’s have some confidence that the Working Group will conduct a thorough and comprehensive review of the issues, and take every opportunity to course-correct them if they do not. I hope this is helpful. Thank you, J. ------------------ James Bladel GNSO Chair From: Rafik Dammak <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>> Date: Tuesday, April 25, 2017 at 19:51 To: "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] MOTION FOR ELECTRONIC (EMAIL) VOTE - Initiate Amendment Process on Specific Red Cross Names Hi James, quick question with regard to Resolved.1.b which mentions "a defined limited set of variations of these names" how and who will decide for those variations? btw I just noticed that in the whereas we have "189 National Red Cross and Red Crescent Societies," and in resolved "190 Red Cross National Societies", shouldn't be the same number (the latter is missing "Red Crescent" mention, a matter of consistency within the motion)? Best, Rafik 2017-04-26 7:04 GMT+09:00 James M. Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>: Councilors – Attached and copied below, please find an amended version of the Motion to Initiate Policy Amendment Process on Specific Red Cross Names that was discussed during our last meeting. Recall that, during our last GNSO Council call on 20 April, the Council agreed to defer this Motion to an electronic vote, in order to allow for certain updates to be made to the text of the motion. Also note that the Council agreed to proceed with an electronic vote outside a regularly scheduled Council meeting. The updated language of the motion has been reviewed and approved by me as its proposer, and Michele and Rubens as its seconders. It includes some minor clarifications received as feedback from the ICRC representatives, but does not include any items that materially changed the scope of the affected strings, or any other items that were not discussed previously in Copenhagen. This email will also serve as notice that, as Council Chair, I am hereby formally providing all Councilors with the requisite minimum 7 days’ advance notice of the electronic vote, in accordance with Section 4.10.2.d. of the GNSO Operating Procedures (https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf)[gnso.icann.…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. The 4-day voting period will begin at 23:59 UTC on Tuesday 2 May 2017 and close at 23:59 UTC on Saturday 6 May 2017. (Please be reminded that the GNSO Operating Procedures require that electronic voting be an open vote, and its outcome be published and recorded, with accompanying voter statements, if any, as minutes for purposes of formal record keeping.) Thank you, J. ------------------ James Bladel GNSO Chair _______________________ Initiation of Policy Amendment Process on Specific Red Cross and Red Crescent Names - Deferred to electronic vote Submitted by: James Bladel Seconded: Rubens Kuhl, Michele Neylon WHEREAS, in November 2013, the GNSO completed a Policy Development Process (PDP) which resulted in a number of consensus recommendations for protecting the identifiers of International Governmental Organizations and International Non-Governmental Organizations, including the International Red Cross and Red Crescent Movement (Movement), at the top and second level in all generic top-level domains (gTLDs) (PDP Working Group Final Report: https://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>, with Minority Statements: https://gnso.icann.org/en/issues/igo-ingo-final-minority-positions-10nov13-…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>); WHEREAS, the GNSO Council approved all the PDP consensus recommendations on 20 November 2013 (http://gnso.icann.org/en/council/resolutions#20131120-2[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…>) and, following a mandatory public comment period on the final PDP recommendations, sent its Recommendations Report to the ICANN Board on 23 January 2014 (https://gnso.icann.org/en/issues/council-board-igo-ingo-23jan14-en.pdf[gnso…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…>); WHEREAS, on 30 April 2014 the Board adopted those of the GNSO’s PDP recommendations that were consistent with GAC advice on the topic, which in relation to the Movement were for the terms “Red Cross”, “Red Crescent”, “Red Crystal”, and “Red Lion & Sun” (referred to as “Scope 1 Identifiers” by the PDP Working Group) to be reserved at the top and second levels, with an Exception Procedure to be designed for the affected organization (http://www.icann.org/en/groups/board/documents/resolutions-30apr14-en.htm#2…<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_groups…>); WHEREAS, between June 2014 and January 2015 the Board and the GNSO Council engaged in discussions of the remaining inconsistencies between GAC advice and GNSO policy, which in relation to the Movement concerned the names of 189 National Red Cross and Red Crescent Societies, and the names and acronyms of the International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies (referred to as “Scope 2 Identifiers” by the PDP Working Group); WHEREAS, at ICANN57 in November 2016 the Board proposed that the GAC and the GNSO engage in a facilitated, good faith discussion to attempt to resolve the remaining inconsistencies between GAC public policy advice and GNSO consensus policy recommendations regarding the “Scope 2 Identifiers” of the Movement; WHEREAS, representatives from the GAC and the GNSO engaged in such a facilitated, good faith discussion at ICANN58 in March 2017 during which the following matters were noted: (1) The public policy considerations associated with protecting the Movement’s identifiers in the domain name system (DNS); (2) The GAC’s rationale for seeking permanent protection for the terms most closely associated with the Movement and its respective components is grounded in the protections of the designations “Red Cross”, “Red Crescent”, “Red Lion and Sun”, and “Red Crystal” under international treaty law and under multiple national laws; (3) The list of names of the Red Cross and Red Crescent National Societies is a finite, limited list of specific names of the National Societies recognized within the Movement (http://www.ifrc.org/Docs/ExcelExport/NS_Directory.pdf[ifrc.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ifrc.org_Docs_Excel…> ); (4) There are no other legitimate uses for these terms; and (5) The GAC had provided clarification following the completion of the GNSO PDP, via its March 2014 Singapore Communique, on the finite scope of the specific list of Movement names for which permanent protections were being requested (https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gacweb.icann.org_downl…>); WHEREAS, following the GAC-GNSO discussion, the Board passed a resolution on 16 March 2017 requesting that the GNSO initiate its process for Amendments or Modifications of Approved Policies, as described in Section 16 of the GNSO PDP Manual (https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf[gnso.ic…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>), to consider amending the GNSO’s approved policy concerning the specific names of the Red Cross and Red Crescent National Societies and the specific names International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies (collectively, Recommendation 5 in Section 3.1 of the PDP Working Group Final Report): and WHEREAS, the GNSO Council agrees that the aforementioned set of exceptional circumstances provides a justifiable basis for the Council to take this extraordinary step to reconsider the policy recommendation and that this is not to be viewed as the Council’s consent to reopen PDP recommendations in all cases where GNSO-developed policy is in discord with GAC advice: RESOLVED, 1.The GNSO Council hereby initiates the process described in Section 16 of the GNSO PDP Manual; accordingly, the GNSO Council requests that the PDP Working Group be reconvened for the purpose of consultation by the GNSO Council on the following proposed amendment to Recommendation 5 in Section 3.1 of the PDP Working Group Final Report: (a) The full names of the 190 Red Cross National Societies and the full names of the International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies are to be placed into Specification 5 of the Base gTLD Registry Agreement, with an exception procedure to be created for cases where the relevant Red Cross Red Crescent Movement organization wishes to apply for their protected string at the second level; (b) In placing the specified identifiers into Specification 5 of the Registry Agreement, this should apply to an exact match of the full name of the relevant National Society recognized within the International Red Cross and Red Crescent Movement (in English and the official languages of its state of origin), the full names of the International Committee of the Red Cross and of the International Federation of Red Cross and Red Crescent Societies (in the six official United Nations languages) and a defined limited set of variations of these names; and (c) In considering the proposed amendment, account is to be duly taken of the matters noted during the GAC-GNSO facilitated discussion at ICANN58 as well as of the GAC’s public policy advice to reserve the finite list of names of the Red Cross and Red Crescent National Societies, as recognized within the International Red Cross and Red Crescent Movement, in all gTLDs. 2. In accordance with Section 16 of the PDP Manual, the GNSO Council directs ICANN staff to post the proposed amendment to Recommendation 5 for public comment, for a period of 30 days commencing from the date of the first meeting of the reconvened PDP Working Group. 3. In accordance with Section 16 of the PDP Manual, the GNSO Council intends to put the proposed amendment to a vote following consultation with the PDP Working Group and the conclusion of the requisite public comment period. The GNSO Council notes that approval of the proposed amendment requires a Supermajority Vote of both Houses in favour of the amendment. 4. The Council thanks all of those who participated in the talks at ICANN58 in Copenhagen, and in particular Bruce Tonkin for moderating the discussion. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.

3 3

Action Items: GNSO Council meeting 20 April 2017
by Nathalie Peregrine May 2, 2017

May 2, 2017

Dear Councilors, Apologies for the delay in sending this, it was stuck in my Drafts folder and I only noticed today. Please find the action items, below and as attachment, arising from the GNSO Council meeting on 20 April 2017. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. The next GNSO Council meeting is on the 18 May 2017. ACTION ITEMS FROM GNSO COUNCIL MEETING 20 APRIL 2017 Item 2: Opening Remarks / Review of Projects & Action List Open Action Item from ICANN58: * Councilors Erika Mann and Keith Drazek to circulate updated draft on proposed Council action following the letter from the Thick Whois IRT on privacy issues Item 4. COUNCIL VOTE – Approval of GNSO Council Review of the GAC Communique from Copenhagen Action items: * GNSO Councilors to provide final input on draft GNSO Council Review of the GAC Communique (DONE) * Council Chairs and staff to prepare letter to the ICANN Board summarizing GNSO Council input; letter to be sent in time for the Board-GAC meeting on 27 April 2017 (DONE) Item 5. COUNCIL VOTE – Initiation of GNSO Process for Amending Approved GNSO Policy Recommendations Relating to Certain Red Cross Movement Names Immediate Action Items: * GNSO Council Chairs and staff to circulate updated motion to the Council list for review (DONE) * GNSO Council Chair to formally announce dates and times of electronic balloting period pursuant to GNSO Operating Procedures for Voting Outside a Meeting (DONE) * ICANN staff to conduct electronic vote and announce voting results (IN PROCESS) Action Items (if Vote is Successful): * ICANN staff to reconvene original PDP Working Group * ICANN staff to post proposed policy amendment for public comment for 30 days commencing from the date of the first meeting of the reconvened PDP Working Group * GNSO Council to vote on final proposal following close of public comment period and receipt of input from the reconvened PDP Working Group Item 6: COUNCIL VOTE – GNSO Council Comments on the Proposed ICANN Budget for Financial Year (FY) 2018 Action Items: * ICANN staff to submit approved comments to the public comment forum (DONE) Item 7: COUNCIL VOTE – Approval of GNSO Nominees for the Registration Directory Services Review Team Action Items: * ICANN staff to communicate the names of the GNSO-endorsed candidates to staff supporting the RDS Review Team (RDS-RT) (DONE) * ICANN staff to inform the endorsed candidates that the GNSO Council expects that, if selected for the RDS-RT, the nominee will represent the views of the entire GNSO community in their work on the RDS-RT, and will provide regular feedback as a group on the discussions taking place as well as the positions being taken by GNSO representatives on the RDS-RT (IN PROCESS) * ICANN staff to request that staff colleagues supporting the RDS-RT to notify the unsuccessful applicants who did not receive endorsement (if any) for this RDS-RT, thanking them for their interest (DONE) Item 8: COUNCIL DISCUSSION – Updated Charter for the Cross Community Working Group on Internet Governance Action Items: * Councilors to work with staff to compile a list of questions to be sent to the CCWG-IG * Topic to be added to the May Council meeting agenda either as a further discussion item or a motion on the GNSO’s next steps on this topic Item 9: COUNCIL DISCUSSION – PLANNING FOR ICANN59 IN JOHANNESBURG, JUNE 2017 Action Items: * Council chairs to work with staff to update GNSO block schedule based on overall meeting schedule updates As a reminder, all Action items in progress can be found posted on the wiki page here: https://community.icann.org/x/RgZlAg[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Please let me know if I missed anything or if you have questions. Thank you. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0