April 2017 - council - lists.icann.org

FW: Participation in the ccNSO PDP WG on Retirement of ccTLDs
by James M. Bladel 13 Apr '17

13 Apr '17

Councilors – See note below from Katrina Sataki, chair of the ccNSO, inviting members of the GNSO Community are invited to participate in an upcoming ccNSO PDP working group. Please distribute to your SGs/Cs. Thank you, J. From: Katrina Sataki <katrina(a)nic.lv> Date: Thursday, April 13, 2017 at 7:49 To: "James M. Bladel" <jbladel(a)godaddy.com> Cc: 'Ben Fuller' <ben(a)fuller.na>, 'Nathalie Peregrine' <nathalie.peregrine(a)icann.org>, 'Marika Konings' <marika.konings(a)icann.org> Subject: Participation in the ccNSO PDP WG on Retirement of ccTLDs Dear James, On behalf of the ccNSO Council I would like to invite individual members from the GNSO to participate in the ccNSO PDP Working Group on the Retirement of ccTLDs. Participants are entitled to participate on equal footing with members, unless the charter states otherwise. In addition, participants are not expected to represent the view or views of your group, they participate in their personal capacity. We expect that the WG will be hold its first meeting at the end of May 2017. The group will meet in person during ICANN 59 in Johannesburg. If someone from the GNSO is interested, please let me or the ccNSO Secretariat (ccnsosecretariat(a)icann.org) know. Kindest regards, ]{atrina Chair of the ccNSO --- Background --- At its meeting on 13 March 2017 the ccNSO Council initiated its 3rd ccNSO policy development process (ccPDP). This ccPDP is intended to develop and recommend policies for the: - Retirement of ccTLDs - Review mechanism with respect to decisions on delegation, transfer, revocation and retirement of ccTLDs. Under the ccPDP the focus will first be on the retirement of ccTLDs. Only after completion of the development work relating to retirement, work on the review mechanism will begin. As part of the decisions on the initiation, the ccNSO Council has also adopted the charter for the working group on retirement of the ccTLDs (https://ccnso.icann.org/workinggroups/charter-wg-retirement-cctlds-10apr17-…). The goal of the working group (WG) is to report on and recommend a policy for the retirement of the delegated Top Level Domains associated with the country codes assigned to countries and territories listed in the ISO 3166-1 within the framework of the ccNSO Policy Development Process. We are now in the process to seek volunteers for the WG, including participants and observers (see charter section 2.1.2). By applying all commit to participate actively and regularly in the work of the WG and express to have at least a basic understanding of the Reference Material*. By applying, members, participants and observers also commit to the charter of the WG, including but not limited to its Internal decision making and standards of behavior. * Reference Material - RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt ) - The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ) - ISO 3166 standard (http://www.iso.org/iso/country_codes) - CWG-Stewardship Final Report, Annex O: ccTLD Appeals Mechanism Background and supporting Findings Sections 1414- 1428, (https://community.icann.org/download/attachments/53779816/FinalTransitionPr… ). Issue paper to explore retirement of ccTLDs (January 2017): https://community.icann.org/download/attachments/64068742/Issues%20to%20exp…

1 0

FW: [Soac-infoalert] ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now.
by James M. Bladel 13 Apr '17

13 Apr '17

Councilors – Please save the date for the next ICANN Quarterly Stakeholder call (27 APR), and share with your SG/Cs as needed. Thanks— J. From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Thursday, April 13, 2017 at 4:11 Subject: [Soac-infoalert] ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now. [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-04-12-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now. 12 April 2017 ICANN has announced its FY17 Q3 Stakeholder Call, which will take place on 27 April 1500 UTC. The call will focus on how ICANN has implemented community policy for the quarter ending 31 March 2017, as well as provide an update from our European engagement team. This European update is part of a new format to spotlight regional activities. Please click here[survey.clicktools.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__survey.clicktools.com_a…> to register for the call and receive instructions on how to join. If you are unable to access the form, please email us<mailto:icann.communications@icann.org> your full name and an email address to be registered. The call is open to anyone and live interpretation will be offered in Arabic, Chinese, English, French, Portuguese, Russian and Spanish. There will be a question & answer (Q&A) session and all materials (recordings, transcripts and presentations) will be made available on the ICANN website[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. ?These calls were organized to enhance ICANN's accountability and transparency efforts. They are also a great way for you to stay informed on what the organization has done in line with ICANN's mission of keeping the Internet secure, stable and interoperable. More information Please visit the Reporting page[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on the ICANN website for more information, including recordings of previous calls. The presentation will be posted 24-48 hours in advance. ______________________________________________

1 0

FW: [Soac-infoalert] ICANN News Alert -- Deferral of Country Code Names Supporting Organization Review
by James M. Bladel 12 Apr '17

12 Apr '17

Councilors, FYI. Personally, I wasn’t aware that these reviews could be deferred. Thanks— J. From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Tuesday, April 11, 2017 at 0:31 Subject: [Soac-infoalert] ICANN News Alert -- Deferral of Country Code Names Supporting Organization Review [CANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2017-04-06-en ________________________________ Deferral of Country Code Names Supporting Organization Review 6 April 2017 Open Date: 6 April 2017 Close Date: 19 May 2017 Originating Organization: Multi Stakeholder Strategy and Strategic Initiatives Categories/Tags: Reviews/Improvements Brief Overview: The ccNSO Review, scheduled to start in August 2017, is proposed to be deferred by 12 months, in response to community concerns about bandwidth. As per ICANN's Bylaws, Article 4, Section 4.4 (a), organizational reviews, such as the ccNSO Review, 'shall be conducted no less frequently than every five years, based on feasibility as determined by the Board.' The Final Report of the previous ccNSO Review was submitted to the Board on 4 March 2011. Following an initial deferral, due to the IANA Transition, the ICANN Board, based on explicit feedback from the ccNSO Chair, proposes to defer the upcoming ccNSO Review until August 2018. The ccNSO will use the time until the start of the next ccNSO Review to conduct an evaluation of the implementation status of the recommendations that arose from the previous Review. Link: https://www.icann.org/public-comments/ccnso-review-deferral-2017-04-06-en

8 10

Fwd: [Soac-infoalert] President's Corner: Catching up with Stakeholders - ICANN
by James M. Bladel 12 Apr '17

12 Apr '17

Councilors - See below for a new blog post from Göran. Thanks -- J. From: David Olive <david.olive(a)icann.org><mailto:david.olive@icann.org> Date: April 11, 2017 at 13:39:08 Subject: [Soac-infoalert] President's Corner: Catching up with Stakeholders - ICANN https://www.icann.org/news/blog/president-s-corner-catching-up-with-stakeho… President's Corner: Catching up with Stakeholders <https://www.icann.org/news/blog/president-s-corner-catching-up-with-stakeho…><https://www.icann.org/news/blog/president-s-corner-catching-up-with-stakeho…><https://www.icann.org/news/blog/president-s-corner-catching-up-with-stakeho…><https://www.icann.org/news/blog/president-s-corner-catching-up-with-stakeho…><https://www.icann.org/news/blog/president-s-corner-catching-up-with-stakeho…><https://www.icann.org/news/blog/president-s-corner-catching-up-with-stakeho…> It was great to see so many of you in person during ICANN58 in Copenhagen. With more than 2,500 registered attendees, and more than 300 sessions, we were all very busy, and I thank you all for your hard work and focus. I also want to thank our generous hosts from Copenhagen’s business and government communities, who helped make the meeting possible. We released the ICANN58 survey results<https://www.icann.org/news/announcement-2017-04-03-en> last week, as well as the Post-ICANN 58 Policy Report<https://www.icann.org/en/system/files/files/post-copenhagen58-policy-report…>, if you want to read up on what took place during the meeting. And if you haven’t had a chance, I highly encourage you to read the ICANN Org Report to the Board<https://www.icann.org/static_documents/executive-team-reports-march-2017-pu…> that we prepared before the meeting. We’ve been busy working through our FY18 planning and reviewing the public comments<https://www.icann.org/public-comments/fy18-budget-2017-03-08-en> for the budget as they come in. That public comment period is closing on 28 April, so if you are interested in submitting comments, please make sure you do so before then. I recently attended World Hosting Days<http://worldhostingdays.com/global/>(WHD), an annual industry event, which was held in Germany this year. I met with many stakeholders and visited the WHD exhibition, where many ICANN contracted parties and stakeholders had booths showcasing their latest innovations and offerings. While there, I participated in a Q&A session where we touched on the importance of ICANN’s work to the operations and business future for hosting companies, and discussed subjects ranging from IPv6 to the KSK Rollover. I also got to take part in one of the world’s leading and fastest-growing civil society-led conferences, RightsCon<https://www.rightscon.org/>. Outside of the Internet Governance Forum (IGF), RightsCon is the largest gathering of civil society stakeholders that are active in Internet issues. I joined a panel titled “Taking Forward the Multistakeholder Debate<https://events.bizzabo.com/RightsCon/agenda/session/177214>,”that featured an excellent discussion about where and how multistakeholder approaches can be applied, with frequent reference to ICANN’s model, including our successes, challenges and desire for continuous improvement. The ICANN community was well represented at RightsCon. The Non-Commercial Users Constituency (NCUC) sponsored their own panel on domain industry developments. Members of At-Large, ICANN fellows, the Regional Internet Registries (RIRs), the Governmental Advisory Committee(GAC) and numerous business stakeholders – including major Internet companies and Internet Service Providers – were all well represented. At ICANN’s booth, community members and staff kept busy, engaging and interacting all throughout the conference. We held an informal meet-up with ICANNstakeholders, making use of the comfortable bean bag chairs and enjoying the informal setting; for me, this was a highlight. I also had the pleasure of meeting with members of the American Registry for Internet Numbers (ARIN) at ARIN39<http://www.cvent.com/events/arin-39-public-policy-and-members-meeting/event…>and the North American Regional At Large Organization (NARALO) while in New Orleans last week. It was very rewarding for me to interact with these two key community groups and participate in brainstorms, sessions and Q&As. 2017 has been a busy year for me, as I strive to meet and work with members of the multistakeholder community all around the world. In the next few months, I will be in Beijing meeting with members of the multistakeholder community, at a Board workshop in Geneva, the Global Domains Division (GDD) Summit in Madrid, and soon after to a regional RIR meeting with LACNIC in Iguazu Falls, Brazil. And of course, I hope to see many of you, whether in person or remotely, participating at ICANN59<https://meetings.icann.org/en/johannesburg59> in Johannesburg, South Africa. Sent from my iPhone David A. Olive Senior Vice President, Policy Development Support Managing Director, ICANN Regional Headquarters –Istanbul

1 0

*Updated Proposed Final Agenda GNSO Council Meeting 20 April 2017 at 21:00 UTC
by Terri Agnew 11 Apr '17

11 Apr '17

Dear councilors, Please find the Proposed Final Agenda for the GNSO Council Meeting on 20 April 2017 at 21: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 20 April 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/vsbRAw 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: 21:00 UTC: http://tinyurl.com/lnp3e4l 14:00 Los Angeles; 17:00 Washington; 22:00 London; (next day) 00:00 Istanbul; 07: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 16 February 2017, posted on 8 March 2017. Minutes of the meeting of the GNSO Council on 15 March 2017, posted on 6 April 2017 Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg> . Item 3. Consent Agenda (5 mins) 3.1 – Confirming of Council liaison appointments At the Council’s Wrap Up Session at ICANN58 in Copenhagen in March 2017, it was noted that several Cross Community Working Groups, GNSO Working Groups and Implementation Review Teams no longer had Council liaisons, due either to a Councilor’s resignation or the ending of a Councilor’s term on the Council. In response to a Call for Volunteers, the following Councilors volunteered to serve as Council liaisons to the respective groups noted against their names: * Thick WHOIS Implementation Review Team (IRT): Susan Kawaguchi * Translation & Transliteration of gTLD Registration Data IRT: ____________ * GNSO Rights & Obligations under the Revised ICANN Bylaws Drafting Team: _____________ * Cross Community Working Group on Internet Governance: Julf Helsingius Here the Council is expected to confirm the appointments of the above-named Councilors as Council liaisons to the respective groups. Item 4. COUNCIL VOTE – Approval of GNSO Council Review of the GAC Communique from Copenhagen (20 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… <https://gacweb.icann.org/download/attachments/27132037/GAC%20ICANN%2058%20C…)> &modificationDate=1490215932389&api=v2), 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. This draft was circulated to the Council mailing list on [INSERT DATE AND LINK TO DRAFT]. Here the Council will discuss the draft Council feedback, and vote on whether or not to approve it for transmission to the ICANN Board. 4.1 – Presentation of motion <https://community.icann.org/x/wsbRAw> (Stephanie Perrin) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Initiation of GNSO Process for Amending Approved GNSO Policy Recommendations Relating to Certain Red Cross Movement Names (20 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. Here the Council will consider whether or not to initiate the Section 16 process as requested by the Board, which will include reconvening the original PDP Working Group for consultation purposes as well as conducting a public comment period on the proposed amendments prior to a formal Council vote on the proposed amendments. 5.1 – Presentation of the motion <https://community.icann.org/x/wsbRAw> (James Bladel) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – GNSO Council Comments on the Proposed ICANN Budget for Financial Year (FY) 2018 (15 minutes) Following initial community review, a revised proposed Budget and Operating Plan for FY2018 was published for public comments on 13 March 2017 (https://www.icann.org/public-comments/fy18-budget-2017-03-08-en). At its Wrap Up Session at ICANN58 in Copenhagen, the GNSO Council agreed to form a small team of volunteers to draft comments on the revised Budget for Council consideration. At the Council’s request, ICANN’s Finance Team conducted a webinar on 4 April 2017 covering those aspects of the proposed Budget of interest to the GNSO community (https://gnso.icann.org/en/meetings/presentation-gnso-update-04apr17-en.pdf). A draft of the proposed Council comments was circulated to the GNSO Council on 10 April 2017. Here the Council will discuss the draft comments, and vote on whether or not to submit them as a Council comment to the public comment forum. 6.1 – Presentation of the motion <https://community.icann.org/x/wsbRAw> (James Bladel) 6.2 – Council discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL VOTE – Approval of GNSO Nominees for the Registration Directory Services Review Team (10 minutes) In January 2017, ICANN launched a Call for Volunteers for the forthcoming second Review Team (RT) to be formed to conduct a review of Registration Directory Services (formerly the WHOIS Review). Under the Bylaws, the each Supporting Organization and Advisory Committee may nominate up to 7 candidates for the RT, with its first 3 preferred candidates being guaranteed a spot on the RT. The GNSO’s Standing Selection Committee (established by the GNSO Council in March 2017: https://gnso.icann.org/en/council/resolutions#20170315-2) met to discuss those volunteers who had indicated they wished to be nominated by the GNSO, and has reached full consensus on a slate of 7 nominees. The list was circulated to the Council on 10 April 2017. Here the Council will vote on whether to approve the slate of nominees proposed by the Standing Selection Committee. 7.1 – Presentation of the motion <https://community.icann.org/x/wsbRAw> (Julf Helsingus) 7.2 – Council discussion 7.3 – Council vote (voting threshold: simple majority) Item 8: COUNCIL DISCUSSION – 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 discuss its potential next steps in relation to the GNSO’s continued participation as a Chartering Organization of this CCWG. 8.1 – Status summary (GNSO Council chairs) 8.2 – Council discussion 8.3 – Next steps Item 8: COUNCIL DISCUSSION – PLANNING FOR ICANN59 IN JOHANNESBURG, JUNE 2017 (15 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 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, and Review of All Rights Protection Mechanisms in All gTLDs, all of whose leadership teams have submitted requests for specific sessions. 8.1 – Summary of planning activities to date (GNSO Council chairs) 8.2 – Council discussion 8.3 – Council confirmation of sessions for the three PDP Working Groups 8.4 – Next steps Item 9: 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 21:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-7 14:00 San José, Costa Rica UTC-6 15:00 Iowa City, USA (CST) UTC-5 16:00 New York/Washington DC, USA (EST) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-3 18::00 London, United Kingdom (GMT) UTC+1 22:00 Bonn, Germany (CET) UTC+2 23:00 Cairo, Egypt, (EET) UTC+2 23:00 Istanbul, Turkey (TRT) UTC+3 00:00 (21 April 2017) Singapore (SGT) UTC +8 05:00 (21 April 2017) Tokyo, Japan (JST) UTC+9 06:00 (21 April 2017) Sydney/Hobart, Australia (AEDT) UTC+11 07:00(21 April 2017) ---------------------------------------------------------------------------- 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 http://tinyurl.com/lnp3e4l Thank you. 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 interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…> GNSO Newcomer pages

1 0

Fwd: Fwd: MOTION: Re: DRAFT of GNSO Response to GAC Communique (and Re: PROPOSING MOTION RE: GAC Copenhagen Communique)
by Stephanie Perrin 11 Apr '17

11 Apr '17

Councillors: Please find attached a motion for the acceptance of the GNSO response to the GAC Communique. Also attached is a draft response, but regrettably I do not believe this is the latest version, which will follow shortly. Regards, Stephanie Perrin

2 1

FW: Call for volunteers - GNSO Council liaisons
by James M. Bladel 11 Apr '17

11 Apr '17

Thanks, Marika. Colleagues - as Marika noted, this is item 3 (Consent Agenda) at our next meeting. Thank you, J. From: <council-bounces(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Monday, April 10, 2017 at 7:46 To: GNSO Council List <council(a)gnso.icann.org> Subject: [council] Call for volunteers - GNSO Council liaisons Dear All, An open action item from the wrap up session at ICANN58 was to solicit new volunteers for the role of Council liaison to the following initiatives: · Cross-Community Working Group on Internet Governance · GNSO Rights & Obligations under the Revised ICANN Bylaws Drafting Team · Translation/Transliteration of Internationalized Registration Data Implementation Review Team · Thick WHOIS Implementation Review Team – Volunteer: Susan Kawaguchi Please indicate on the mailing list if you are interested to take on this role (thank you to Susan for already volunteering for the Thick WHOIS IRT!). The objective is to confirm the new liaisons at the upcoming Council meeting. As a reminder, the GNSO Working Group Guidelines describe the role of a liaison as follows: The role of the Liaison consists of reporting to the CO [Chartering Organization] on a regular basis on the progress of the Working Group; assisting the Chair as required with his/her knowledge of WG processes and practices; taking back to the CO any questions or queries the WG might have in relation to its charter and mission; and, assisting or intervening when the WG faces challenges or problems. The Liaison is expected to play a neutral role, monitor the discussions of the Working Group and assist and inform the Chair and the WG as required. The CO is therefore strongly encouraged to appoint an individual to the role of liaison who is expected to remain neutral and fulfill the role as described above. Furthermore, in the context of an Implementation Review Team (IRT) there are potential additional responsibilities for the liaison as outlined in the IRT Principles and Guidelines (see https://gnso.icann.org/en/council/irt-principles-guidelines-23aug16-en.pdf). 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

Motion - Adoption of the GNSO Review of the GAC Copenhagen Communique
by James M. Bladel 10 Apr '17

10 Apr '17

Councilors – Attached and copied below, please find a placeholder motion for consideration during our meeting on 20 APR. The motion concerns adoption of our response to the GAC’s Copenhagen Communique, and the team drafting this response should have final language posted to the list by mid week. Thank you, J. ---------------------------------------------- PROPOSED MOTION: Adoption of the GNSO Review of the GAC Copenhagen Communiqué for submission to the ICANN Board 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 [include link]) 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.

1 1

MOTION - Adoption of the GNSO Council Comment on FY18 Budget and Operating Plan
by James M. Bladel 10 Apr '17

10 Apr '17

Councilors – Attached and copied below, please find a motion for consideration during our 20 APR meeting to adopt the Draft GNSO Comment on ICANN’s FY18 Budget and OpPlan. The Draft Comment is also attached. Thank you, J. ------------------- Whereas, 1. Following initial community review, a revised proposed Budget and Operating Plan for FY2018 was published for public comments on 13 March 2017 (https://www.icann.org/public-comments/fy18-budget-2017-03-08-en). 2. At its Wrap Up Session at ICANN58 in Copenhagen, the GNSO Council agreed to form a small team of volunteers to draft comments on the revised Budget for Council consideration (https://www.icann.org/public-comments/fy18-budget-2017-03-08-en). 3. At the Council’s request, ICANN’s Finance Team conducted a webinar on 4 April 2017 covering those aspects of the proposed Budget of interest to the GNSO community (https://gnso.icann.org/en/meetings/presentation-gnso-update-04apr17-en.pdf). 4. A draft of the proposed Council comments was circulated to the GNSO Council on [INSERT DATE]. 5. The GNSO is a Decisional Participant within the new Empowered Community, and the GNSO Council recognizes (a) that the Empowered Community’s powers as contained in the revised ICANN Bylaws includes the ability to veto budgets adopted by the ICANN Board; and (b) the importance of fully understanding the funding and expenses of ICANN’s operations. Resolved, 1. The GNSO Council approves the FY18 Draft Budget comments prepared on behalf of the GNSO Council, and instructs ICANN staff to formally submit the approved comment to the Public Comment Forum. 2. The GNSO Council thanks the volunteers who prepared the comments and ICANN staff who provided invaluable assistance to the volunteers in the drafting of the comments.

1 0

MOTION: Initiation of Policy Amendment Process on Specific Red Cross Names
by James M. Bladel 10 Apr '17

10 Apr '17

Councilors – Attached and copied below, please find a motion for consideration during our 20 APR meeting, to invoke the process to amend the PDP recommendations associated with Red Cross names. Additionally, Staff has prepared a Briefing Paper on how this amendment process works, and this is also attached. Thank you, J. ------------------------------------------------ DRAFT GNSO COUNCIL RESOLUTION – INITIATION OF POLICY AMENDMENT PROCESS ON SPECIFIC RED CROSS NAMES 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-…); WHEREAS, the GNSO Council approved all the PDP consensus recommendations on 20 November 2013 (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); 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…); 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 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 and specific list of Movement names for which permanent protections were being requested (https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…); and 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), 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): 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 by the International Red Cross and Red Crescent Movement (in English and the official languages of its state of origin), the full names International Committee of the Red Cross and 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 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. 1. 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. 1. 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. 1. The Council thanks all of those who participated in the talks at ICANN58 in Copenhagen, and in particular Bruce Tonkin for moderating the discussion.

1 0