May 2019 - council - lists.icann.org

Action all: Please register to get ready for ICANN65 Prep Week
by Nathalie Peregrine May 29, 2019

May 29, 2019

Dear all, As per the announcement below, please register and submit your questions or comments regarding any of the subject matters covered by the 8 webinars taking place during Prep Week, by Friday 7 June 2019 via this form: https://docs.google.com/forms/d/18IzOJlVHNwXoViSKXZrjM-iW1BZqinyXYoV_R-1rGf… Tuesday, 11 June 16:00 UTC | ICANN Org Multistakeholder Strategy and Strategic Initiatives (MSSI) Update 23:00 UTC | ICANN65 Security Update Wednesday, 12 June 16:00 UTC | ICANN Org Global Domains Division (GDD) – Community Briefing on Raising Awareness about Registrant Issues and Challenges 23:00 UTC | Update on Evolving ICANN's Multistakeholder Model of Governance Thursday, 13 June 16:00 UTC | ICANN Org Policy Team: Policy Updates 23:00 UTC | Nominating Committee Review Implementation Working Group Update Monday, 17 June 16:00 UTC | ICANN Org FY21-25 Operating & Financial Plan and Open Data Program Updates 21:00 UTC | Generic Names Supporting Organization (GNSO) Policy Update Full announcement can be found here: https://www.icann.org/news/announcement-2019-05-23-en 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 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

Audio and zoom recording with chat transcript/ GNSO Council meeting on Tuesday, 28 May 2019 at 21:00 UTC
by Terri Agnew May 29, 2019

May 29, 2019

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and chat of the GNSO Council meeting held on Tuesday, 28 May 2019 at 21:00 UTC. Audio Recording: https://gnso.icann.org/sites/default/files/policy/2019/audio/audio-council-… Zoom Recording: https://icann.zoom.us/recording/share/G8wO5OTLSGMDezNXkgOKLc12eOX4hiMND-rGU… (includes visual and rough transcript. To access the rough transcript, select the Audio Transcript tab) Zoom chat at: https://icann.zoom.us/recording/download/WvGFkwCMpsB4SqrXhc0wWgSAKO108jiDpd… All on page: https://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> With kind regards, Terri

1 0

Re: [council] IGO Curative Rights: Materials from March 2017 facilitated discussions and compilation of GAC advice on the overall topic of IGO protections (preventative and curative)
by Nathalie Peregrine May 28, 2019

May 28, 2019

Dear all, As a follow up to Mary’s email, please find the agenda for the Extraordinary GNSO Council meeting posted here<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>, and all documents being discussed here<https://community.icann.org/display/gnsocouncilmeetings/Documents+28+May+20…>. Staff will not be able to share all documents in the Zoom room during the call so please have the two above wiki pages open to be able to consult them at your convenience. Thank you! Nathalie From: council <council-bounces(a)gnso.icann.org> on behalf of Mary Wong <mary.wong(a)icann.org> Date: Tuesday, May 28, 2019 at 10:14 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] IGO Curative Rights: Materials from March 2017 facilitated discussions and compilation of GAC advice on the overall topic of IGO protections (preventative and curative) Dear Councilors, In preparation for your discussion regarding possible engagement with the GAC on the topic of IGO protections, you may find the following links helpful. These constitute the background documents and recordings for the facilitated discussion that took place at ICANN58 in Copenhagen in March 2017 on this topic (i.e. Problem Statement, Briefing Paper, facilitator’s slides and the transcript of the session: https://icann58copenhagen2017.sched.com/event/9sZA/gnso-gac-facilitated-dia… [icann58copenhagen2017.sched.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann58copenhagen2017.…>). As you go through the materials, please note the following: * The background summaries relate to the topic as matters stood in March 2017; as such, for Curative Rights, there have been subsequent developments that are not mentioned in the documents (e.g. subsequent GAC advice; finalization of the Curative Rights recommendations, etc.). * At the time, the IGO-INGO Curative Rights PDP Working Group had just published its Initial Report for public comment – as such, what became Recommendations 1-5 comprised, at the time, some preliminary recommendations that were later modified by the Working Group. * The facilitated discussion began with, and focused largely on, “preventative” protections for IGOs – this remains an outstanding topic for which the Board had indicated it wished to resolve in the same timeframe as the curative rights issue. For completeness, please also find attached the latest compilation of GAC communications and advice on the topic of IGO protections up to October 2018 (from the Barcelona meeting). Consequent to the March 2017 facilitated discussions in Copenhagen on the topic of IGO protections, you may wish to note the following: * The Copenhagen Communique (March 2017) advised the ICANN Board to: I. Pursue implementation of (i) a permanent system of notification to IGOs regarding second-level registration of strings that match their acronyms in up to two languages and (ii) a parallel system of notification to registrants for a more limited time period, in line with both previous GAC advice and GNSO recommendations; II. Facilitate continued discussions in order to develop a resolution that will reflect (i) the fact that IGOs are in an objectively unique category of rights holders and (ii) a better understanding of relevant GAC Advice, particularly as it relates to IGO immunities recognized under international law as noted by IGO Legal Counsels; and III. Urge the Working Group for the ongoing PDP on IGO-INGO Access to Curative Rights Protection Mechanisms to take into account the GAC’s comments on the Initial Report. * The Johannesburg Communique (June 2017) expressed concern over the possibly divergent path that the Curative Rights PDP looked to be taking, and advised the Board that the GAC’s continued belief was that the appropriate second-level dispute resolution mechanism should: I. be modeled on, but separate from, the existing Uniform Dispute Resolution Policy (UDRP) II. provide standing based on IGOs’ status as public intergovernmental institutions, and III. respect IGOs’ jurisdictional status by facilitating appeals exclusively through arbitration. * The Abu Dhabi Communique (November 2017) contained the statement that the GAC: “remains open to working with the GNSO to try to find a mutually agreeable resolution to this issue [and] also recalls the values of openness, transparency and inclusion, and representativeness and process integrity, that are respectively enshrined in ICANN’s Bylaws and GNSO Operating Procedures … “ * The Panama Communique (June 2018) advised the ICANN Board to: “ … work with the GNSO and the GAC following the completion of the ongoing PDP on IGO-INGO access to curative rights protection mechanisms to ensure that GAC advice on protection of IGO acronyms, which includes the available “small group” proposal, is adequately taken into account also in any related Board decision”. * The Barcelona Communique (October 2018) advised the Board to: “facilitate a substantive, solutions-oriented dialogue between the GNSO and the GAC in an effort to resolve the longstanding issue of IGO protections, on which it reaffirms its previous advice, notably with respect to the creation of a curative mechanism and maintenance of temporary protections”. Finally, while not constituting formal GAC advice, the Kobe Communique (March 2019) contained a note that “during the Kobe Meeting the GAC has had fruitful exchanges with the GNSO Council regarding the possibility of restarting the PDP on curative protections, under conditions amenable to all interested parties, including IGOs and interested GAC members, with a view to achieving mutually acceptable results. At that meeting, the GAC indicated that there should be a timeline with a targeted date associated with such a course of action.” Best regards, Steve & Mary

1 0

Re: [council] IGO Curative Rights: Materials from March 2017 facilitated discussions and compilation of GAC advice on the overall topic of IGO protections (preventative and curative)
by Mary Wong May 28, 2019

May 28, 2019

Apologies, attachment now, well, attached! From: council <council-bounces(a)gnso.icann.org> on behalf of Mary Wong <mary.wong(a)icann.org> Date: Tuesday, May 28, 2019 at 16:14 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] IGO Curative Rights: Materials from March 2017 facilitated discussions and compilation of GAC advice on the overall topic of IGO protections (preventative and curative) Dear Councilors, In preparation for your discussion regarding possible engagement with the GAC on the topic of IGO protections, you may find the following links helpful. These constitute the background documents and recordings for the facilitated discussion that took place at ICANN58 in Copenhagen in March 2017 on this topic (i.e. Problem Statement, Briefing Paper, facilitator’s slides and the transcript of the session: https://icann58copenhagen2017.sched.com/event/9sZA/gnso-gac-facilitated-dia… [icann58copenhagen2017.sched.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann58copenhagen2017.…>). As you go through the materials, please note the following: * The background summaries relate to the topic as matters stood in March 2017; as such, for Curative Rights, there have been subsequent developments that are not mentioned in the documents (e.g. subsequent GAC advice; finalization of the Curative Rights recommendations, etc.). * At the time, the IGO-INGO Curative Rights PDP Working Group had just published its Initial Report for public comment – as such, what became Recommendations 1-5 comprised, at the time, some preliminary recommendations that were later modified by the Working Group. * The facilitated discussion began with, and focused largely on, “preventative” protections for IGOs – this remains an outstanding topic for which the Board had indicated it wished to resolve in the same timeframe as the curative rights issue. For completeness, please also find attached the latest compilation of GAC communications and advice on the topic of IGO protections up to October 2018 (from the Barcelona meeting). Consequent to the March 2017 facilitated discussions in Copenhagen on the topic of IGO protections, you may wish to note the following: * The Copenhagen Communique (March 2017) advised the ICANN Board to: I. Pursue implementation of (i) a permanent system of notification to IGOs regarding second-level registration of strings that match their acronyms in up to two languages and (ii) a parallel system of notification to registrants for a more limited time period, in line with both previous GAC advice and GNSO recommendations; II. Facilitate continued discussions in order to develop a resolution that will reflect (i) the fact that IGOs are in an objectively unique category of rights holders and (ii) a better understanding of relevant GAC Advice, particularly as it relates to IGO immunities recognized under international law as noted by IGO Legal Counsels; and III. Urge the Working Group for the ongoing PDP on IGO-INGO Access to Curative Rights Protection Mechanisms to take into account the GAC’s comments on the Initial Report. * The Johannesburg Communique (June 2017) expressed concern over the possibly divergent path that the Curative Rights PDP looked to be taking, and advised the Board that the GAC’s continued belief was that the appropriate second-level dispute resolution mechanism should: I. be modeled on, but separate from, the existing Uniform Dispute Resolution Policy (UDRP) II. provide standing based on IGOs’ status as public intergovernmental institutions, and III. respect IGOs’ jurisdictional status by facilitating appeals exclusively through arbitration. * The Abu Dhabi Communique (November 2017) contained the statement that the GAC: “remains open to working with the GNSO to try to find a mutually agreeable resolution to this issue [and] also recalls the values of openness, transparency and inclusion, and representativeness and process integrity, that are respectively enshrined in ICANN’s Bylaws and GNSO Operating Procedures … “ * The Panama Communique (June 2018) advised the ICANN Board to: “ … work with the GNSO and the GAC following the completion of the ongoing PDP on IGO-INGO access to curative rights protection mechanisms to ensure that GAC advice on protection of IGO acronyms, which includes the available “small group” proposal, is adequately taken into account also in any related Board decision”. * The Barcelona Communique (October 2018) advised the Board to: “facilitate a substantive, solutions-oriented dialogue between the GNSO and the GAC in an effort to resolve the longstanding issue of IGO protections, on which it reaffirms its previous advice, notably with respect to the creation of a curative mechanism and maintenance of temporary protections”. Finally, while not constituting formal GAC advice, the Kobe Communique (March 2019) contained a note that “during the Kobe Meeting the GAC has had fruitful exchanges with the GNSO Council regarding the possibility of restarting the PDP on curative protections, under conditions amenable to all interested parties, including IGOs and interested GAC members, with a view to achieving mutually acceptable results. At that meeting, the GAC indicated that there should be a timeline with a targeted date associated with such a course of action.” Best regards, Steve & Mary

1 0

IGO Curative Rights: Materials from March 2017 facilitated discussions and compilation of GAC advice on the overall topic of IGO protections (preventative and curative)
by Mary Wong May 28, 2019

May 28, 2019

Dear Councilors, In preparation for your discussion regarding possible engagement with the GAC on the topic of IGO protections, you may find the following links helpful. These constitute the background documents and recordings for the facilitated discussion that took place at ICANN58 in Copenhagen in March 2017 on this topic (i.e. Problem Statement, Briefing Paper, facilitator’s slides and the transcript of the session: https://icann58copenhagen2017.sched.com/event/9sZA/gnso-gac-facilitated-dia…) As you go through the materials, please note the following: * The background summaries relate to the topic as matters stood in March 2017; as such, for Curative Rights, there have been subsequent developments that are not mentioned in the documents (e.g. subsequent GAC advice; finalization of the Curative Rights recommendations, etc.). * At the time, the IGO-INGO Curative Rights PDP Working Group had just published its Initial Report for public comment – as such, what became Recommendations 1-5 comprised, at the time, some preliminary recommendations that were later modified by the Working Group. * The facilitated discussion began with, and focused largely on, “preventative” protections for IGOs – this remains an outstanding topic for which the Board had indicated it wished to resolve in the same timeframe as the curative rights issue. For completeness, please also find attached the latest compilation of GAC communications and advice on the topic of IGO protections up to October 2018 (from the Barcelona meeting). Consequent to the March 2017 facilitated discussions in Copenhagen on the topic of IGO protections, you may wish to note the following: * The Copenhagen Communique (March 2017) advised the ICANN Board to: I. Pursue implementation of (i) a permanent system of notification to IGOs regarding second-level registration of strings that match their acronyms in up to two languages and (ii) a parallel system of notification to registrants for a more limited time period, in line with both previous GAC advice and GNSO recommendations; II. Facilitate continued discussions in order to develop a resolution that will reflect (i) the fact that IGOs are in an objectively unique category of rights holders and (ii) a better understanding of relevant GAC Advice, particularly as it relates to IGO immunities recognized under international law as noted by IGO Legal Counsels; and III. Urge the Working Group for the ongoing PDP on IGO-INGO Access to Curative Rights Protection Mechanisms to take into account the GAC’s comments on the Initial Report. * The Johannesburg Communique (June 2017) expressed concern over the possibly divergent path that the Curative Rights PDP looked to be taking, and advised the Board that the GAC’s continued belief was that the appropriate second-level dispute resolution mechanism should: I. be modeled on, but separate from, the existing Uniform Dispute Resolution Policy (UDRP) II. provide standing based on IGOs’ status as public intergovernmental institutions, and III. respect IGOs’ jurisdictional status by facilitating appeals exclusively through arbitration. * The Abu Dhabi Communique (November 2017) contained the statement that the GAC: “remains open to working with the GNSO to try to find a mutually agreeable resolution to this issue [and] also recalls the values of openness, transparency and inclusion, and representativeness and process integrity, that are respectively enshrined in ICANN’s Bylaws and GNSO Operating Procedures … “ * The Panama Communique (June 2018) advised the ICANN Board to: “ … work with the GNSO and the GAC following the completion of the ongoing PDP on IGO-INGO access to curative rights protection mechanisms to ensure that GAC advice on protection of IGO acronyms, which includes the available “small group” proposal, is adequately taken into account also in any related Board decision”. * The Barcelona Communique (October 2018) advised the Board to: “facilitate a substantive, solutions-oriented dialogue between the GNSO and the GAC in an effort to resolve the longstanding issue of IGO protections, on which it reaffirms its previous advice, notably with respect to the creation of a curative mechanism and maintenance of temporary protections”. Finally, while not constituting formal GAC advice, the Kobe Communique (March 2019) contained a note that “during the Kobe Meeting the GAC has had fruitful exchanges with the GNSO Council regarding the possibility of restarting the PDP on curative protections, under conditions amenable to all interested parties, including IGOs and interested GAC members, with a view to achieving mutually acceptable results. At that meeting, the GAC indicated that there should be a timeline with a targeted date associated with such a course of action.” Best regards, Steve & Mary

1 0

Prep for Council Call in 1 hour
by Drazek, Keith May 28, 2019

May 28, 2019

Hi all, Attached is a document to help guide and inform our discussion during today's special Council call. Thanks and I look forward to speaking with you shortly. Best, Keith

1 0

[ICANN Community Leaders] 27 May Update
by Nathalie Peregrine May 27, 2019

May 27, 2019

[http://r20.rs6.net/on.jsp?ca=fea07009-4a89-4e4e-8b92-99524be8dedc&a=1122025…] Monday, 27 May 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. TABLE OF CONTENTS Information Sharing · NEW: Evolving the Governance of the Root Server System · NEW: Get Ready for ICANN65 Prep · NEW: ICANN Publishes a Revised Draft Strategic Plan for Fiscal Years 2021-2025 · IN TWO DAYS: End of Rejection Action Petition Period · REMINDER: CCT-RT Recommendations · LOOKING AHEAD: ICANN66 Travel Support Timeline ICANN65 Planning · NEW: Sign up for the Engagement Booth at ICANN65 · SAVE THE DATE: ICANN65 Community Leadership Reception · REMINDER: Invitation to Meet with Brian Cute in Marrakech · REMINDER: Meet with the ATRT3 Review Team Public Comment · Evolving ICANN's Multistakeholder Model · Label Generation Rules for the Root Zone Version 3 (RZ-LGR-3) · Study on Technical Use of Root Zone Label Generation Rules · Process Proposal for Streamlining Organizational Reviews · Evolving the Governance of the Root Server System Information Sharing NEW: Evolving the Governance of the Root Server System Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Please read the latest blog post [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> by ICANN President and CEO Göran Marby; ICANN Board Technical Committee Chair Akinori Maemura, and RSSAC Co-Chairs Fred Baker and Brad Verd about the new Public Comment proceeding on evolving the governance of the Root Server System (RSS). BACKGROUND Supporting the evolution of RSS governance contributes to the commitment of ICANN to strengthen the security, stability, and resiliency of the Domain Name System. It also enables direct interaction between the ICANN community and the RSOs. Furthermore, it ensures that global root service remains accountable and sustainable into the future. Evolving the governance of the RSS will result in significant changes to the ICANN community and ICANN org. The community-driven process to develop a final governance model envisions considerable work and commitment of resources. Any budgetary and financial implications will be handled through ICANN processes that ensure accountability and transparency. NEW: Get Ready for ICANN65 Prep Week Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING ICANN released the schedule for ICANN65 Prep Week [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. The Prep Week will feature eight webinars, including updates on several community-led projects. This initiative aims to streamline the pre-ICANN Public Meeting experience to enable more substantive conversations during sessions, increase awareness of cross-community and high-interest topics, and enhance briefings and readout sessions. Register and submit any questions via this form [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> by Friday, 7 June 2019. All registered attendees will receive participation details days before the webinar dates. NEW: ICANN Publishes Revised Draft Strategic Plan for Fiscal Years 2021-2025 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING This Revised Draft Strategic Plan [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> reflects comments received during a public consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> held between December 2018 and February 2019 on the Draft Strategic Plan for Fiscal Years 2021–2025, and at a public session [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> held at ICANN64 in Kobe, Japan. A summary of how comments were considered in the Revised Plan is available in a document that lists, sorted by contributor, comments received and ICANN organization's responses. The summary document can be found on the Strategic Plan Public Comments proceedings page [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. The Public Comment process and session at ICANN64 yielded helpful and specific clarifications, but no fundamental substantive changes or feedback. Therefore, as a next step, the Revised Draft Plan will be presented to the ICANN Board in June 2019 for consideration and adoption. The affordability of this Strategic Plan will be considered as part of the Five-Year Operating and Financial Plan currently under development. IN TWO DAYS: End of Rejection Action Petition Period Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Under the ICANN Bylaws, the ICANN Board's approval of the FY20 Operating Plan and Budget and updates to the Five-Year Operating Plan on Wednesday, 8 May 2019 triggered a Rejection Action Petition Period for the Empowered Community. This 21-day period will end at 23:59 PDT (Los Angeles being the location of the principal ICANN office) on Wednesday, 29 May 2019, or 06:59 UTC on Thursday, 30 May 2019. The ICANN Bylaws also require that Decisional Participants in the Empowered Community “promptly inform their constituents” of the delivery of the relevant ICANN Board notices. Please refer to Annex D of the ICANN Bylaws [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> for additional details on the Rejection Process, including all pertinent deadlines and requirements for Rejection Action Petitions. REMINDER: CCT-RT Recommendations Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING The ICANN Board passed a resolution on 1 March 2019 that calls for a set of Competition, Consumer Trust, and Consumer Choice Review Team (CCT-RT) Final Recommendations to be passed through, in whole or in part, to community groups. Notifications will be circulated to the community group the CCT-RT identified for the fourteen passed through recommendations. As articulated in the Board resolution, "passing through these CCT-RT recommendations is not a directive that the groups identified should formally address any of the issues within those recommendations. It is within the purview of each group to identify whether work will be taken on and the topics that the group will address". BACKGROUND The CCT-RT released its Final Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> on 8 September 2018. It contains 35 recommendations and is the culmination of nearly three years of work, reviewing how the expansion of top-level domain names impacted competition, consumer trust, and choice. More information [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> about the CCT Review and Specific Reviews. The ICANN Board took action [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> on each of the 35 recommendations produced by the CCT-RT on 1 March 2019 and was informed by public comment [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> input received on the Final Report. The Board’s decisions on each recommendation are documented here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> and a blog post about the Board action can be found here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> for more context. LOOKING AHEAD: ICANN66 Travel Support Timeline Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING All travel support requests are now due 120 days prior to the next ICANN Public Meeting. This was previously a 90-day deadline. Therefore, the deadline for ICANN66 travel support is Friday, 5 July 2019. If applicable, community groups will need to adjust their election timelines accordingly to ensure new leaders are eligible in time for the ICAN66 travel support deadline. ICANN65 Planning NEW: Sign up for the Engagement Booth at ICANN65 Executive: Sally Costerton, Senior Advisor to the President and CEO; Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING I know everyone is busy preparing for ICANN65, but I want to make you aware that you are welcome to come and do outreach at the ICANN Engagement Booth at ICANN65. The ICANN Engagement Booth is in place for newcomers, ICANN org, and the ICANN community to engage in discussions. It is supported by volunteers from the community, including members of ICANN's Supporting Organizations and Advisory Committees. It would be beneficial to have the presence of seasoned ICANN community members to share their knowledge. We would like to offer one-hour slots during ICANN65. Please click here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to sign up for a slot. Thank you, Deborah Escalera SAVE THE DATE: ICANN65 Community Leadership Reception Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Save the date for the ICANN65 Community Leadership Reception with members of the ICANN Board and Executive Team on Sunday, 23 June 2019, 18:00-20:00 CET in Marrakech, Morocco. Details will be confirmed as the date approaches. REMINDER: Invitation to Meet with Brian Cute in Marrakech Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING A high interest topic session on this the future of the multistakeholder model of governance [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> is planned for ICANN65. Facilitator Brian Cute is interested in updating the community on the work that has been done to date and discuss how a work plan to address the community-identified issues will be developed following ICANN65. Community leaders interested in scheduling time to meet with Brian Cute in Marrakech can email <evolvingmsm(a)icann.org>. REMINDER: Meet with the ATRT3 Review Team at ICANN65 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All SO/AC Chairs INFORMATION SHARING The third Accountability and Transparency Review Team (ATRT3) will meet in Marrakech to advance its work. As some of the team will be in Marrakech we would like to ask for a 30 to 40-minute slot on your community group's agenda, if possible. Community input is key to the success of this process. If you are able to accommodate us on your agenda, please send us an email to <atrt3-coordination(a)icann.org> to let us know a day and time that would suit. We will send you a preliminary set of questions ahead of the meeting to aid the discussion. We also welcome any questions you wish to raise in advance. Our goal for Marrakech is to: - Socialize our terms of reference and scope; - Conduct investigation of identified objectives - Seek input from the community to help us shape our findings and draft recommendations. BACKGROUND The ATRT review is mandated by ICANN Bylaws Section 4.6 (b) to examine ICANN’s execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community. Prior to meeting in Marrakech, the review team met on 3-5 April in Los Angeles for its first substantive meeting to develop our terms of reference and work plan, in response to the Board Resolution (2018.10.25.15) requesting that “ATRT3 adopt its Terms of Reference and Work Plan within 60 days of convening its first meeting, and submit these documents to the Board and to the leadership of the Supporting Organizations and the Advisory Committees, to confirm that the team's scope and timeline are consistent with the requirements of the ICANN Bylaws and ICANN community expectations.” We look forward to hearing from you. Many thanks and best regards, Cheryl Langdon-Orr and Pat Kane, ATRT3 Co-Chairs Public Comment Evolving ICANN's Multistakeholder Model [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 4 June 2019 Label Generation Rules for the Root Zone Version 3 (RZ-LGR-3) [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 4 June 2019 Study on Technical Use of Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Sunday, 30 June 2019 Process Proposal for Streamlining Organizational Reviews [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 15 July 2019 Evolving the Governance of the Root Server System [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 9 August 2019 Volume 1, Issue 22 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 30 May 2019 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 our service provider [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

ICANN 65 -- Updated Block Schedule with HIT/CC Sessions
by Drazek, Keith May 24, 2019

May 24, 2019

Hi all, Just a quick note to alert you to the updated ICANN 65 block schedule with the final HIT/CC sessions. The link is here: https://meetings.icann.org/sites/default/files/65-blockschedule_v3.1.pdf The four HIT sessions are as follows: 1. DNS over HTTPS (DoH) 2. Impact of GDPR and EPDP Phase 1 Recommendation on Existing Policies & Procedures 3. Evolution of the Multi-Stakeholder Model 4. Policy Around Universal Acceptance and Next Steps The GNSO is the lead coordinator on #2 above, for the obvious reasons. I proposed this session as a consolidated session to capture the proposals submitted by various groups concerning impacts of GDPR and to address Recommendation 27 from the EPDP Phase 1 report that calls for this review. We will need to coordinate with ICANN Org and the Phase 1 IRT on this project, and the HIT/CC session should provide a baseline for discussion and also give the community an opportunity to weigh in with their views. As I noted separately, we were able to reduce the overall number of HIT/CC sessions from 7 to 4 and narrowed the list of proposals down from 12. This was needed in light of the already tight schedule for a Policy Forum. Regards, Keith

1 0

Final Proposed Agenda GNSO Council Meeting - 28 May 2019 at 21:00 UTC
by Nathalie Peregrine May 24, 2019

May 24, 2019

Dear all, Please below find the final proposed agenda for the GNSO Council Meeting on 28 May 2019 at 21:00 UTC. Final GNSO Council Agenda 28 May 2019 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/p4GjBg<https://community.icann.org/display/gnsocouncilmeetings/Documents+28+May+20…> This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf> v3.3, updated on 30 January 2018 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: https://tinyurl.com/yxwsy8v5 14:00 Los Angeles; 17:00 Washington; 22:00 London; 02:00 Islamabad; 06:00 Tokyo; 07:00 Melbourne GNSO Council Meeting Audio Cast Listen in browser: http://stream.icann.org:8000/stream02 Listen in application such as iTunes: http://stream.icann.org:8000/stream02.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 (10 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes <https://gnso.icann.org/sites/default/files/policy/2019/minutes/minutes-coun…> of the GNSO Council meeting on the 18th April were posted on the 4th May 2019 Minutes of the GNSO Council meeting on the 16th May will be posted on the 31st May 2019 Item 2: COUNCIL DISCUSSION - Expedited PDP on the Temporary Specification Phase 1 (50 minutes) On 15 May, the ICANN Board informed<https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-t…> the GNSO Council of the Board’s action in relation to the GNSO’s Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data policy recommendations. The Board did not adopt two of the recommendations in full, where the Board has identified that portions of those recommendations are not in the best interests of the ICANN Community or ICANN and is initiating the consultation process between the Board and the GNSO Council. This concerns recommendation #1, purpose 2 and recommendation #12, deletion of data in the Organization field. As required under the ICANN Bylaws at Annex A-1,Section 6.b, a Board Statement is attached as Annex A to the letter, articulating the reasons for the Board’s determination on these two items. As per the Bylaw requirements (Annex A-1, Section 6.c), “the Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement.” During this meeting, the Council shall review the Board Statement and consider next steps. See also Annex A-1, Section 6. Board Approval Process below for further details. Section 6. Board Approval Processes The Board will meet to discuss the EPDP recommendation(s) as soon as feasible, but preferably not later than the second meeting after receipt of the Recommendations Report from the Staff Manager. Board deliberation on the EPDP Recommendations contained within the Recommendations Report shall proceed as follows: a. Any EPDP Recommendations approved by a GNSO Supermajority Vote shall be adopted by the Board unless, by a vote of more than two-thirds (2/3) of the Board, the Board determines that such policy is not in the best interests of the ICANN community or ICANN. If the GNSO Council recommendation was approved by less than a GNSO Supermajority Vote, a majority vote of the Board will be sufficient to determine that such policy is not in the best interests of the ICANN community or ICANN. b. In the event that the Board determines, in accordance with paragraph a above, that the proposed EPDP Recommendations are not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council. c. The Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement. The Board shall determine the method (e.g., by teleconference, email, or otherwise) by which the Council and Board will discuss the Board Statement. At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board, including an explanation for the then-current recommendation. In the event that the Council is able to reach a GNSO Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than two-thirds (2/3) of the Board determines that such guidance is not in the interests of the ICANN community or ICANN. For any Supplemental Recommendation approved by less than a GNSO Supermajority Vote, a majority vote of the Board shall be sufficient to determine that the guidance in the Supplemental Recommendation is not in the best interest of the ICANN community or ICANN. 2.1 – Introduction of topic (Council leadership) 2.2 – Council discussion 2.3 – Next steps Item 3: COUNCIL DISCUSSION – IGO-INGO Access to Curative Rights Protection Mechanisms (25 minutes) On 9 July 2018, the PDP WG submitted its Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/igo-ingo-…> to the GNSO Council for its consideration, which contains five consensus recommendations, along with three Working Group member minority statements, documenting their disagreement either with one or more of the final recommendations or other parts of the Final Report. On its 19 July Council meeting, the Council resolved<https://gnso.icann.org/en/council/resolutions#201806> to accept the Final Report from the IGO-INGO Access to Curative Rights Mechanisms PDP Working Group, where it noted that it would consider the topic of curative rights protections for IGOs in the broader context of the appropriate overall scope of protection for all IGO identifiers. On 9 October 2018, the Council held a question and answer webinar to review the recommendations and to ask itself a series of questions, 1) Does the Council believe that the PDP has addressed the issues that it was chartered to address (i.e. What questions/topics was the Working Group chartered to consider, did it consider those charter topics/questions, and did it do so in a legitimate way)?; 2) Has the PDP followed due process?; and 3) Did the PDP Working Group address GAC advice on the topic? A motion to consider the Final Report was originally submitted on the 24 October 2018 Council meeting agenda but was withdrawn due to concerns around both the process followed by the PDP, as well as the substance of the PDP WG’s recommendations. Council leadership and staff developed a summary document (Summary Paper<https://gnso.icann.org/en/drafts/igo-ingo-crp-access-final-28nov18-en.pdf> and Slide Deck<https://gnso.icann.org/en/drafts/igo-ingo-crp-procedural-options-council-29…>) that lists issues raised by Councilors, options available, and potential considerations. During the November meeting, the Council considered a set of available options and briefly discussed possible next steps. On 20 December 2018, Council leadership circulated a proposal<https://mm.icann.org/pipermail/council/2018-December/022153.html> for next steps. Council leadership has since sent a reply<https://gnso.icann.org/en/correspondence/gnso-council-to-ismail-14jan19-en.…> to the GAC, in response to a letter received during ICANN63. On the 24 January 2018 Council meeting, the Council discussed the proposal prepared by Council leadership. On 14 February 2019, the Council further discussed next steps and agreed to consult with the Governmental Advisory Committee, both before and at ICANN64. The GNSO Council and GAC had productive discussions, where the Council discussed procedural options that it is considering. The GAC’s Kobe Communique <https://gac.icann.org/contentMigrated/icann64-kobe-communique> noted the GAC’s “fruitful exchanges with the GNSO Council regarding the possibility of restarting the PDP on curative protections, under conditions amenable to all interested parties, including IGOs and interested GAC members, with a view to achieving mutually acceptable results [with] a timeline with a targeted date associated with such a course of action.” Based on the Council discussions and consultation with the GAC, the Council believes that it has thoroughly considered the available options. On 18 April 2019, the Council resolved<https://gnso.icann.org/en/council/resolutions#201904> to approve recommendations 1-4 and refer recommendation 5 to be considered by the RPMs PDP as part of its Phase 2 work. As part of its Consent Agenda, on 16 May 2019, the Council confirmed the transmission of the Recommendations Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/council-r…> to the ICANN Board. On 23 May, the GAC sent a letter<https://gnso.icann.org/en/correspondence/ismail-to-drazek-23may19-en.pdf> to the GNSO Council, noting that approving recommendations 1-4 and referring recommendation 5 to the RPMs PDP is contrary to longstanding GAC Advice. The GAC therefore hopes the Council can confirm its willingness to participate in a Board facilitated discussion and requests response by 31 May 2019. Here, the Council will consider the letter received from the GAC and consider the best path forward. 3.1 – Introduction of topic (Council leadership) 3.2 – Council discussion 3.3 – Next steps Item 4: 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/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRT) UTC-3 18:00 London, United Kingdom (GMT) UTC+1 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+2 23:00 Moscow, Russia (MSK) UTC +3 (+1 day) 00:00 Islamabad, Pakistan (PKT) UTC+5 (+1 day) 02:00 Singapore (SGT) UTC+8 (+1 day) 05:00 Tokyo, Japan (JST) UTC+9 (+1 day) 06:00 Melbourne, Australia (AEDT) UTC+10 (+1 day) 07:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 27 of October 2019, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 03 of November 2019 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/yxwsy8v5

1 0

Updated Action Items: GNSO Council meeting 16 May 2019
by Nathalie Peregrine May 24, 2019

May 24, 2019

Dear councilors, Please find below the updated action item list, with additional action item pertaining to the Evolution of the Multistakeholder Model of Governance (agenda item 9). The wiki page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> has also been updated accordingly. Thank you! Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, May 21, 2019 at 10:23 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] Action Items: GNSO Council meeting 16 May 2019 Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council call held on the 16 May 2019. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please ensure your wiki logins are up to date as all Action Items have been assigned to councilors and/or staff and posted on the Action Item wiki page here<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. If you are logged into the wiki when you go to that page, your name will be highlighted alongside the action item assigned to you. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. ACTION ITEMS FROM THE GNSO COUNCIL MEETING 16 MAY 2019 Item 3: Consent Agenda Action items: * Staff to inform CCWG on New gTLD Auction Proceeds of the confirmation of Julf Helsingius to serve on the working group. [COMPLETED] * Staff to communicate the IGO-INGO Access to Curative Rights Protection Mechanisms PDP Recommendations Report to ICANN Board Operations. Item 4: COUNCIL DISCUSSION - Amendments 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 Action items: * Staff to circulate call for volunteers for Review of All Rights Protection Mechanisms in All gTLDs Phase 2 charter amendments. Item 5: COUNCIL DISCUSSION - Discussion of the Inter-Registrar Transfer Policy (IRTP) Policy Status Report Action items: * Rubens Kuhl, as Council liaison, to reach out to the IRT for the EPDP Phase 1 to have a conversation and gain a better understanding of how to address recommendation 24 and the Form of Authorization issue stemming from the Temporary Specification. * Council to determine next steps for the Transfer Policy, which could include the chartering of a narrowly focused EPDP. IItem 6: COUNCIL DISCUSSION – Legislative / Regulatory Report Outcomes: * Global Engagement to take into account feedback, in particular, inclusion of rationale for including a piece of legislation on the legal / regulatory tracker. Item 7: COUNCIL UPDATE – GNSO Input to the Independent Review Process Standing Panel Action items: * Councilors to reach out to their respective groups to communicate additional call for volunteers for additional members to serve on the IRP Implementation Oversight Team. Item 8: COUNCIL DISCUSSION - Non-registry GNSO Liaison to the Customer Standing Committee Action items: * Council to determine their approach for the non-registry GNSO liaison to the Customer Standing Committee (CSC), which could include supporting James Gannon to serve a second term or to seek additional candidates. Item 9: Evolution of the Multistakeholder Model of Governance Action items: Staff to investigate the anticipated timing, funding and expected deliverables for the Evolution of the Multistakeholder Model of Governance project. Item 10: AOB Action items: * Council leadership and staff to schedule an extraordinary Council meeting to discuss the Board adoption of the EPDP policy recommendations. 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…>

2 1