January 2020 - council - lists.icann.org

Reminder: please register for the pre-ICANN67 webinars!
by Nathalie Peregrine Jan. 28, 2020

Jan. 28, 2020

Dear all, Prep Week is the initiative from ICANN org that consolidates all pre-ICANN Public Meeting webinars into one week. With this initiative, we not only hope to improve community preparation, but also to increase awareness of plenary topics and enhance briefings and readout sessions. ICANN67 Prep Week will take place from 18-24 February 2020 offering 9 webinar sessions. Please register here: https://meetings.icann.org/en/cancun67-prep-week Thank you! Nathalie Nathalie Peregrine Manager, Operations 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 visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 1

Volunteer(s) needed! ICANN66 GNSO Informal Council dinner
by Nathalie Peregrine Jan. 28, 2020

Jan. 28, 2020

Dear councilors, ICANN67 is 39 days away and, as per tradition, the GNSO Informal Council dinner will need a councilor or councilors to sponsor the event. The dinner is scheduled to take place on Sunday 8th March 2020 from 19:00 local time onwards. Staff is on hand of course to assist the councilor-sponsor with venue research, RSVP gathering, payment organising and liaising with the selected venue once it is confirmed. As a reminder, each councilor will pay for his or her food and drink in advance generally, the councilor-sponsor may have to provide a deposit ahead of time to secure the booking. Please let me know if you would like to take part in organizing this event, or if you are familiar with Cancún, you may have venues to suggest. Thank you! Kind regards, Nathalie Nathalie Peregrine Manager, Operations 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

Council Leadership/Liaison Call with RPM PDP WG Co-Chairs
by Drazek, Keith Jan. 27, 2020

Jan. 27, 2020

Hi all, Just a quick reminder that the Council leadership team and John McIlwaine will be meeting on Thursday with the Co-Chairs of the RPM PDP WG to discuss their Project Change Request. If anyone has further input or questions for us prior to that discussion, please advise via email. Thanks and regards, Keith

1 0

Upcoming deadline: GNSO Council input required
by Nathalie Peregrine Jan. 27, 2020

Jan. 27, 2020

Dear all, Please note there is a deadline coming up for documents requiring GNSO Council input or relay to the SGs and Cs for input. Please see these documents posted here<https://community.icann.org/display/gnsocouncilmeetings/Documents+for+GNSO+…>. Thank you! Nathalie Nathalie Peregrine Manager, Operations 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 visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

FW: [ICANN Community Leaders] 27 January 2020
by Julie Bisland Jan. 27, 2020

Jan. 27, 2020

FYI: From: SO-AC-SG-CLeaders <so-ac-sg-cleaders-bounces(a)icann.org> on behalf of ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, January 27, 2020 at 9:58 AM To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> Subject: [ICANN Community Leaders] 27 January 2020 [http://r20.rs6.net/on.jsp?ca=e2633b9d-75b2-442e-8cd5-ed99910d8bb6&a=1122025…] Monday, 27 January 2020 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing · NEW: Nomination Period for ICANN Community Excellence Award 2020 Now Open · NEW: CSC Findings on PTI Performance for December 2019 · DUE FRIDAY: FY21 SO/AC Additional Budget Request Process · DUE FRIDAY: ICANN Fellowship Program Mentors · REMINDER: Register for ICANN67 Prep Week Webinars ICANN67 Planning · TRANSLATION DEADLINE TODAY: ICANN67 Publication Support · REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Public Comment · CLOSES FRIDAY: Proposal for Future Root Zone KSK Rollovers · CLOSES FRIDAY: Third Accountability and Transparency Review Team (ATRT3) Draft Report · Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 · Proposed Amendment 3 to the .COM Registry Agreement · Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group · Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget Information Sharing NEW: Nomination Period for ICANN Community Excellence Award 2020 Now Open From: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING The nomination period for the ICANN Community Excellence Award 2020 is now open. Formerly known as the Multistakeholder Ethos Award, the ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within ICANN’s multistakeholder model. Learn more about the nomination process [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> and submit your nominations here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. NEW: CSC Findings on PTI Performance for December 2019 From: Lars-Johan Liman, CSC Chair INFORMATION SHARING It is my pleasure as chair of the Customer Standing Committee (CSC), to provide you our latest monthly findings on the performance of Public Technical Identifiers (PTI) over December 2019. I am pleased to inform you that the CSC has concluded that PTI’s overall performance over December 2019 was “Excellent” - PTI met 100% of the service level agreements (SLA) over the month of December 2019. The related PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Please note that PTI has completed implementation of the new SLA, IDN Tables Processing Times, and has completed its first round of recording data. Accordingly, this SLA is included in the report over December 2019 that was presented to us. I am also very pleased to provide you an update on the outstanding amendment to the SLA: ccTLD Creation/Transfer – Validation and Reviews. In accordance with the SLA amendment process [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>, the CSC has formally agreed to the amendment of the SLA. After formal approval by PTI, the CSC will request the ccNSO and GNSO Councils to approve the changes. The SLA changes are explained in more detail in the CSC Findings Report. BACKGROUND Generally, the CSC regular meeting is scheduled on or around the 15th every month, and the CSC findings report on the PTI performance is sent out shortly after that meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. We welcome any comments on our reporting to you. The CSC became effective 1 October 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. DUE FRIDAY: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer INFORMATION SHARING The Fiscal Year 2021 (FY21) Supporting Organization and Advisory Committee (SO/AC) Additional Budget Request process has begun. This additional budget approval process is part of the overall ICANN annual budgeting process that is for the review of specific requests from the community that are not already included in the budget but serve to further the key objectives of the requesting community group. Your active participation and adherence to procedural guidelines is greatly appreciated. Information concerning the FY21 SO/AC Additional Budget Request process, including timeline and request template can be found on the Finance [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>community wiki [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Additional Budget Requests are due Friday, 31 January 2020. Please email any questions that you may have to planning(a)icann.org<mailto:planning@icann.org>. We look forward to your continued engagement on the SO/AC Additional Budget Request process for FY21. DUE FRIDAY: ICANN Fellowship Program Mentors Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. SOs/ACs should first select their respective Fellowship Program mentor by Friday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. REMINDER: Register for ICANN67 Prep Week Webinars Executive: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING ICANN org released the schedule for ICANN67 Prep Week [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>, which features a series of nine webinars to prepare the community ahead of the upcoming Community Forum. Register and submit questions by Friday, 14 February 2020. ICANN67 Planning REMINDER: ICANN67 Publication Support Executive: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING TODAY: Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials required design assistance, please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives INFORMATION SHARING ICANN org will hold Strategic Outlook Trends Identification sessions with the community at ICANN67. To prepare for that exercise, ICANN org will be seeking community feedback on possible formats and arrangements which will be sent through each community group’s leadership. The Strategic Outlook program [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> is a joint effort among ICANN org, the community, and ICANN Board to identify and track trends that relate to ICANN and its mission and to make sure that relating opportunities and challenges are incorporated into ICANN's current and future strategy. New trends or shifts in existing trends impacting the operating plans (five-year or annual), and/or budget, will be factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. Public Comment CLOSES FRIDAY: Proposal for Future Root Zone KSK Rollover [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 CLOSES FRIDAY: Third Accountability and Transparency Review Team (ATRT3) Draft Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 11 February 2020 Proposed Amendment 3 to the .COM Registry Agreement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 14 February 2020 Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 14 February 2020 Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 25 February 2020 NEW: Second Security, Stability, and Resiliency (SSR2) Review Team Draft Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Wednesday, 4 March 2020 Volume 2, Issue 8 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 30 January 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

Fwd: [Ext] Thank you and good luck
by Nathalie Peregrine Jan. 25, 2020

Jan. 25, 2020

Dear all, Please see the message from Heather below. Safe travels home! - - - Nathalie Peregrine Manager, Operations 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]<https://urldefense.proofpoint.com/v2/url?u=http-3A__applewebdata__EB3A6F47-…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…> Begin forwarded message: From: haforrestesq <haforrestesq(a)gmail.com> Date: 24 January 2020 at 17:30:39 GMT-8 To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Subject: [Ext] Thank you and good luck Dear amazing Councilors, Imagine hitting the ground after 15 hours in the air to your wonderful video! Absolutely no thanks necessary - I would gladly travel anywhere to help you whenever you think I can be useful. You have my most heartfelt wishes for the fortitude and resolve that it will take to tackle that scary spreadsheet! Yours always, Heather Sent from my Xperia by Sony smartphone

1 0

Choosing an arbitrator | Practical Law
by Flip Petillion Jan. 24, 2020

Jan. 24, 2020

The article I was talking about. https://uk.practicallaw.thomsonreuters.com/w-018-5399?transitionType=Default Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_1788964323]<http://www.petillion.law/> Attorneys – Advocaten - Avocats

1 0

FOR YOUR REFERENCE: Applicable Bylaws concerning the Empowered Community rejection action use case scenario
by Mary Wong Jan. 24, 2020

Jan. 24, 2020

Dear Councilors, Please find below the relevant text from the ICANN Bylaws that I hope is helpful as a reference source for some of the questions that were raised during your Wednesday session concerning a possible Rejection Action Petition scenario for the Empowered Community. On the specific requirement that a Rejection Action Petition must (if it relates to an ICANN Budget) include rationale linking back to a public comment on the draft Budget, see Annex D, Section 2.2(c)(i)(A) (emphasis added): “Where the Rejection Action Petition Notice relates to an ICANN Budget, an IANA Budget, an Operating Plan or a Strategic Plan, the Rejection Action Petition Notice shall not be valid and shall not be accepted by the EC Administration unless the rationale set forth in the Rejection Action Petition Notice is based on one or more significant issues that were specifically raised in the applicable public comment period(s) relating to perceived inconsistencies with the Mission, purpose and role set forth in ICANN's Articles of Incorporation and Bylaws, the global public interest, the needs of ICANN's stakeholders, financial stability, or other matter of concern to the community … “ (Note: A different but equally specific requirement applies to Rejection Action Petitions concerning a Standard Bylaw Amendment - see Annex D, Section 2.2(c)(i)(B).) On indemnification, see Section 20.1 (https://www.icann.org/resources/pages/governance/bylaws-en/#article20) (emphasis added): “ICANN shall, to the maximum extent permitted by the (California Corporations Code), indemnify each of its agents against expenses, judgments, fines, settlements, and other amounts actually and reasonably incurred in connection with any proceeding arising by reason of the fact that any such person is or was an agent of ICANN, provided that the indemnified person's acts were done in good faith and in a manner that the indemnified person reasonably believed to be in ICANN's best interests and not criminal. For purposes of this Article 20, an "agent" of ICANN includes any person who is or was a Director, Officer, employee, or any other agent of ICANN (including a member of the EC, the EC Administration, any Supporting Organization, any Advisory Committee, the Nominating Committee, any other ICANN committee, or the Technical Liaison Group) acting within the scope of his or her responsibility … The Board may adopt a resolution authorizing the purchase and maintenance of insurance on behalf of any agent of ICANN against any liability asserted against or incurred by the agent in such capacity … “ Link to all the timelines and procedural steps applicable to Empowered Community processes, including the filing and disposition of Rejection Action Petitions: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD. Link to the Bylaws describing the Empowered Community and its powers: https://www.icann.org/resources/pages/governance/bylaws-en/#article6. Link to the GNSO-specific procedures and templates developed by the GNSO Bylaws Drafting Team headed by Heather: https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Deposito…. Thanks and cheers Mary

1 0

Recordings, attendance & Zoom chat/ GNSO Council meeting on Thursday, 23 January 2020 at 22:00 UTC.
by Terri Agnew Jan. 24, 2020

Jan. 24, 2020

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and chat of the GNSO Council meeting held on Thursday, 23 January 2020 at 22:00 UTC. Audio only: https://icann.zoom.us/rec/play/6cYuIe2tpm43HdSd5QSDUad_W9TvfKus0SVKq_ReyB3n… Zoom Recording (includes visual and rough transcript. To access the rough transcript, select the Audio Transcript tab): https://icann.zoom.us/rec/share/3sdtPpvWrV1IU4ngs0rgXPAxP6PVaaa80XAWr6FemR1… Zoom chat: https://icann.zoom.us/rec/download/tJQtfuv6_Do3S9KT5QSDUfMqW468LK6sgydN_vde… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> With kind regards, Terri

1 0

GNSO Council resolutions and vote 23 January 2020
by Terri Agnew Jan. 24, 2020

Jan. 24, 2020

Dear all, Please find below the resolutions and council vote from the GNSO Council at its meeting on Thursday 20 January 2020 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page. 20200123 – 1 Consent agenda: 2 items Nomination of a Mentor for the ICANN Fellowship Program Whereas, 1. On 13 November 2019, the ICANN Fellowship Program invited ICANN's Supporting Organizations and Advisory Committees to nominate one individual each (total of 7) to serve on the capacity of Fellowship Program mentor for three consecutive ICANN meetings, beginning with ICANN68 (see https://www.icann.org/news/announcement-2019-11-13-en) 2. On 3 December 2019, the GNSO launched an Expression of Interest (EOI) process to solicit volunteers for the GNSO-nominated mentor position (see https://gnso.icann.org/en/announcements/announcement-03dec19-en.htm) 3. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing applications and recommending one individual for the GNSO to nominate. 4. The SSC reviewed the applications received, taking into account the criteria outlined in the EOI announcement. 5. The SSC submitted its full consensus recommendation to the GNSO Council on 13 January 2020, by way of submission of the relevant motion. 6. The GNSO Council considered the recommendations of the SSC. Resolved, 1. The GNSO nominates Amr Elsadr to serve as a ICANN Fellowship Program mentor for three consecutive ICANN meetings, beginning with ICANN68. 2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to staff supporting the ICANN Fellowship Program. 3. The GNSO Council instructs the GNSO Secretariat to inform the nominated candidate that he or she has been selected. 4. The GNSO Council requests the GNSO Secretariat to send a response to those applicants who were not nominated, thanking them for their interest and encouraging them to apply for future opportunities as they arise. Confirmation of Johan Helsingius as the Chair and Carlton Samuels as Vice-Chair for the GNSO Standing Selection Committee (SSC). Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> 20200123-2 Addendum to the Review of All Rights Protection Mechanisms in All gTLDs Charter to Integrate Recommendation 5 From IGO-INGO Access to Curative Rights Protection Mechanisms Final Report WHEREAS: 1. On 9 July 2018, the Policy Development Process (PDP) Working Group on International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) Access to Curative Rights Protection Mechanisms submitted its Final Report<https://gnso.icann.org/en/issues/igo-ingo-crp-access-final-17jul18-en.pdf> to the GNSO Council. The Final Report contains five policy recommendations on which the Working Group reached consensus. 2. On 19 July 2018, the GNSO Council acknowledged<https://gnso.icann.org/en/council/resolutions#20180719-1> receipt of the PDP Final Report, noted that, "[i]n view of the need to consider the topic of curative rights protections for IGOs in the broader context of appropriate overall scope of protection for all IGO identifiers (including IGO acronyms), the GNSO Council intends to review this Final Report … with a view toward developing a possible path forward that will also facilitate the resolution of the outstanding inconsistencies between GAC advice and prior GNSO policy recommendations on the overall scope of IGO protections"; 3. Between July 2018 and March 2019, the GNSO Council discussed the PDP Final Report at various meetings and considered the procedural options available to it under the GNSO's Operating Rules and ICANN Bylaws 4. On 18 April 2019, the GNSO Council resolved to approve, and recommend that the ICANN Board adopt, Recommendations 1, 2, 3 & 4 of the PDP Final Report. 5. The GNSO Council elected not to approve Recommendation 5 of the PDP Final Report and directed the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and: a. accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain circumstances; b. does not affect the right and ability of registrants to file judicial proceedings in a court of competent jurisdiction; c. preserves registrants' rights to judicial review of an initial UDRP or URS decision; and d. recognizes that the existence and scope of IGO jurisdictional immunity in any particular situation is a legal issue to be determined by a court of competent jurisdiction. 6. The GNSO Council had engaged with the GAC on several occasions during its deliberations on the PDP Final Report, including at the joint GAC-GNSO meeting at ICANN65 in Kobe, Japan, where the GNSO Council had sought the GAC’s feedback on the GAC's willingness to participate in a targeted effort focusing on the issue of curative rights for IGOs and possibly drawing on the community's recent experiences with the Expedited PDP on the Temporary Specification and Work Track 5 of the GNSO New gTLD Subsequent Procedures PDP 7. At ICANN65 in Marrakech, members of the GNSO Council met with certain members of the GAC and IGOs, where there appeared to be agreement from the GAC/IGOs to support the chartering of this separate work. On 20 August, the GAC sent a letter<https://www.icann.org/en/system/files/correspondence/ismail-to-chalaby-20au…> to the ICANN Board, affirming, “its willingness to participate in such chartering effort.” Dialogue between the GNSO Council, GAC, and IGOs continued at ICANN66 in Montreal, followed by further discussions within the Council. 8. The GNSO Council, in consultation with the GAC and IGOs, has prepared the necessary amendments to the RPMs Charter, in the form of an Addendum to that Charter (“Addendum”). RESOLVED: 1. The GNSO Council adopts the amendments to the RPMs Charter to create an IGO Work Track, as reflected in the Addendum<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpms-char…>. 2. The GNSO shall collaborate with each GNSO Stakeholder Group, Constituency, SO and AC to expeditiously issue a call for Members and Observers to join the IGO Work Track, each in accordance with its own rules. The GNSO Council specifically notes that Members and Observers, although appointed by community groups, must nevertheless meet the Membership Criteria as defined in the Addendum. 3. In accordance with the Addendum, the GNSO Council shall conduct an Expressions of Interest process as soon as is reasonably possible, in order to identify and confirm a single, qualified Work Track Chair, consistent with the criteria as defined in the Addendum. 4. The GNSO Council directs the Work Track Chair and Members to conduct its work in as efficient and effective a manner as possible; and as such, monthly written updates shall be submitted to the GNSO Council by the IGO Work Track Chair and/or Council liaison to the Work Track. These updates must include a report as to the progress of the Work Track according to the timeline and milestones identified in its Work Plan. 5. The GNSO Council further directs the Work Track Chair and Members to develop a Work Plan and timeline for its work as a matter of priority and as its first order of business. To facilitate this effort, the GNSO Council instructs ICANN staff to prepare a draft Work Plan and timeline for the Work Track, based on the model adopted for the Expedited Policy Development Process on gTLD Registration Data. The GNSO Council requests that the Work Track Chair submit a proposed Work Plan and timeline to the GNSO Council within four (4) weeks of the first meeting of the Work Track. 6. To facilitate communications between the GNSO and the GAC on this topic, the GNSO Council directs the GNSO liaison to the GAC to provide regular progress reports to the GAC. 7. The GNSO Council thanks the members of the GNSO Council, as well as those from the GAC and IGOs, for their contributions in developing the Addendum. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…>

1 0