May 2020 - council - lists.icann.org

FW: We seek public comments: ccPDP3 Initial Proposals for Process to Retire ccTLDs
by philippe.fouquart＠orange.com May 6, 2020

May 6, 2020

Dear councilors, Please note the following consultation from our ccNSO colleagues. Regards, Philippe From: Ccnso-council [mailto:ccnso-council-bounces@icann.org] On Behalf Of Joke Braeken Sent: Wednesday, May 06, 2020 10:29 AM To: ccnso-members(a)icann.org; cctldcommunity(a)cctld-managers.org; cctldworld(a)icann.org; ccnso-council Subject: [ccnso-council] We seek public comments: ccPDP3 Initial Proposals for Process to Retire ccTLDs Dear All, The ccNSO Policy Development Process 3 (ccPDP3) working group, tasked with developing and proposing policy for the retirement of country code Top-Level Domains (ccTLDs), is seeking input and feed-back from the broader community on its proposed process to retire ccTLDs, when the country code is removed from list of country codes in the ISO 3166 standard. Current Status The Interim Paper is the first step in documenting the recommended policy for the retirement process of ccTLDs. Description The working group tasked with developing and proposing policy for the retirement of country code Top-Level Domains (ccTLDs) is seeking input and feedback from the broader community on its proposed process to retire ccTLDs, when the country code is removed from list of country codes in the ISO 3166 standard. The purpose of the policy proposals is to provide clear and predictable guidance and to document a process that is orderly and reasonable up and to, but excluding, the removal of a ccTLD from the DNS Root Zone file. The ISO 3166-1 list is dynamic and country codes are added and removed on a regular basis. When a new ISO 3166-1 Alpha-2 code element (Alpha-2 code) is added a ccTLD corresponding to that Alpha-2 code can be added to the Root by the IANA Naming Functions Operator (IFO). However, as was identified in 2011 by the ccNSO Delegation and Redelegation Working Group, there is no formal policy available forthe removal of a ccTLD from the Root Zone after a country code is removed fromthe ISO 3166-1 list of country names. The proposals are focused on the following items: * Definition of event that causes the start of the retirement process of a ccTLD and the event that closes the process * Description of the retirement process * Duration of the process * Retirement Plan * Oversight of process and identification of decisions during process that should be subject to a review mechanism. The working group would appreciate feedback on each and every item identified above, specifically: * Do you consider the proposed approach, definition or description reasonable? * Do you suggest an alternative definition or approach? In addition, and as part of developing the process, the working group has completed a series of stress tests. The method, description of tests and results are included in the Interim Paper. The working group would appreciate your view whether the stress testing of the proposals is adequate and complete. The working group would also be interested in suggestions for additional stress tests. Next Steps After closure of the Public Comment period, the working group will review the comments received and take into account in developing a final set of policy recommendations. Close Date 10 July 2020, 23:59 UTC Read more https://www.icann.org/public-comments/ccnso-pdp3-retire-cctlds-2020-05-05-e…<https://www.icann.org/public-comments/ccnso-pdp3-retire-cctlds-2020-05-05-e…> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

FW: [Ext] Approval ccNSO and GNSO Councils for amendment SLA for the ccTLD Creation and Transfer Process
by Drazek, Keith May 5, 2020

May 5, 2020

Hi all, This will be added as an action item to our May agenda. Regards, Keith On 21/02/2020, 16:43, "Lars-Johan Liman" <liman(a)netnod.se> wrote: To: Katrina Sataki, Chair of the ccNSO & Keith Drazek, Chair of the GNSO Cc: Göran Marby, President & CEO ICANN & Kim Davies, President PTI Re: Approval ccNSO and GNSO Councils for amendment SLA for the ccTLD Creation and Transfer Process Date: 20 February 2020 Dear Katrina and Keith, I am writing you to seek approval of the country code Names Supporting Organization and Generic Names Supporting Organization Councils for the IANA Naming Function Service Level Agreement (SLA) for the ccTLD Creation and Transfer Process. As you may recall the Customer Standing Committee and Public Technical Identifiers (PTI) recently agreed on a procedure to amend SLAs (see: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste… ). Accordingly, - in case of the change of the SLA item and threshold values, and after a public comment and agreement on the new SLA between PTI and the Customer Standing Committee (CSC) – the CSC should seek approval from the ccNSO and GNSO Councils on the amended SLA. After both Councils have approved the new SLA, it will be implemented according to the implementation plan. Recently, the CSC and PTI have agreed to change the SLA for the ccTLD Creation and Transfer Process (for details you are referred to the attached document: Service levels for the ccTLD Creation and Transfer Process, version 9 January 2020). Background for the request is that the current SLA measures the processing time from beginning to end without differentiating between the responsibilities of the ccTLD Manager and PTI and the time it takes to complete a step. Under the proposed SLA, the following will be measured and monitored: 1. The time it takes PTI staff to evaluate and to respond to each submission of the supporting documentation 2. The time it takes to author the delegation or transfer report for review by the ICANN Board of Directors, after all relevant material has been submitted by the ccTLD manager 3. Counting the number of transactions with the customer as indication of quality of the request. For more details you are referred to the attached document. The change request was initiated by the CSC and PTI, and, after completing a set of required steps including a public comment period, is now ready for approval by the ccNSO and GNSO Councils, which is required before implementation will start. On behalf of the CSC Lars-Johan Liman, Chair Appendices: PDF-version of this letter, Annex with detailed proposal.

2 2

Re: [council] [Ext] Re: Consensus Playbook
by Steve Chan May 4, 2020

May 4, 2020

Dear Tom, That is indeed how we’re looking at the phase now – this is the “soft launch” as the community gets a chance to review and digest. To your question about the project to improve the Multistakeholder Model, I know that the internal team working on that project is aware of the Consensus Playbook, as well as the likely connection to Issue 8 on Consensus. I’m not sure precisely how the playbook will be integrated, but I’m quite certain it will at least be a part of the solution there. As you’ve noted there are indeed next steps envisioned, but you’re right, we’re not quite there yet. Thanks for the initial round of feedback! Best, Steve From: Tom Dale <tomwdale(a)gmail.com> Date: Sunday, May 3, 2020 at 9:19 PM To: Steve Chan <steve.chan(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Ext] Re: [council] Consensus Playbook Thank you Steve. I assume this has now gone through the proverbial “soft launch”. I hope the following comments will help subsequent Council discussion. The materials are, in general, helpful, practical and tailored to the ICANN framework (or at least the pre-Covid19 framework – see below). Is good! Despite the intended “whole of ICANN” audience the main areas of potential use appear to be: GNSO PDPs – They are referenced most extensively in the document. Which makes sense if this is supposed to complement PDP3.0. It is also applicable to ccNSO PDPs, but there are not as many of those. CCWGs (or other forms of cross-community work which seem to have an endless choice of titles) – Although this does not seem to be explicit in the document. The Playbook’s assertion that it is for all participants, not just leaders, makes sense. Making it happen at the proverbial grassroots is another matter. Does this tie in with the MSM Evolution work (wherever that has got to)? There are some brief references to virtual as opposed to face-to-face meetings. I think if the post-COVID19 ICANN community has more of the former and fewer of the latter (and we don’t know that yet) then it would be worth exploring specific challenges of consensus-building across timezones, e-mail misunderstandings and simply getting agreement among people who may never meet in person. As for next steps – I note that the e-mail sent to PDPs states “We anticipate additional opportunities for the ICANN community to discuss the contents and practical utility of the playbook.” Are there any specific plans for such opportunities yet, or is it (perfectly understandably) a matter of taking its place in a long line of current issues? Hope this is helpful Regards Tom From: council <council-bounces(a)gnso.icann.org> on behalf of Steve Chan <steve.chan(a)icann.org> Date: Wednesday, 22 April 2020 at 7:36 am To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Consensus Playbook Dear Councilors, Originated from the Council’s PDP 3.0 initiative and a subsequent Additional Budget Request, the Consensus Playbook has been completed for the ICANN community to reference and use. This Consensus Playbook aims to provide community volunteers with practical tools and best practices for building consensus, bridging differences, and breaking deadlocks within ICANN processes. It does not seek to change the definition of consensus, the methods of decision making as prescribed in each community group’s rules and procedure, or create any new requirements. The Consensus Playbook was developed by the Consensus Building Institute (CBI), an external vendor contracted by ICANN org, with the requirement of broad applicability across the community, beyond just GNSO PDP working groups. CBI interviewed fourteen (14) ICANN community leaders across ICANN’s SOs and ACs, who shared their extensive consensus building experience in leading and participating in working groups and community groups. The playbook is quite detailed and provides guidance from the beginning to the end of the consensus building process. It stresses that consensus building should be treated as a journey and that it does not just take place at the end of deliberations. To that end, I’d like to draw attention to Appendix A, which serve as a reference guide to help inform you which “plays” within the playbook are applicable to the various phases of the community’s work. The Consensus Playbook, as developed by CBI, was designed for the ICANN community and is only permitted to be used by the ICANN community in support of ICANN related work. The playbook shall not be used for any non-ICANN related purposes. If you have any questions, please let us know. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

1 0

[ICANN Community Leaders] 4 May 2020
by Andrea Glandon May 4, 2020

May 4, 2020

[http://r20.rs6.net/on.jsp?ca=df3fc111-20fd-4012-aec3-053320fdd22a&a=1122025…] Monday, 4 May 2020 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing · NEW: Webinar to Discuss the Draft PTI FY21-24 Strategic Plan · REMINDER: Revisions to ICANN Board’s Proposed Global Public Interest (GPI) Framework · REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process ICANN68 Planning · REMINDER: ICANN68 Publication Support Public Comment · CLOSES TODAY: Phase 1 Initial Report of the Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process · CLOSES TOMORROW: Addendum to the Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 · Guidelines for Developing Reference Label Generation Rules (LGRs) for the Second Level Version 2 · ICANN Africa Regional Plan for Fiscal Years 2021-2025 · Draft PTI FY21-24 Strategic Plan Information Sharing New: Webinar to Discuss the Draft PTI FY21-24 Strategic Plan From: David Conrad, Chief Technology Officer (CTO) Public Technical Identifiers (PTI), the ICANN affiliate responsible for performance of the IANA functions, invites the community to engage with IANA staff and members of the PTI Board to discuss the development of its first comprehensive strategic plan. When the PTI board and IANA staff attended ICANN66, they shared a timeline for the publication of the draft strategic plan that included face-to-face engagement during ICANN67 in Cancún, Mexico. Due to the COVID-19 outbreak and change to a remote participation-only meeting, we will now host two interactive webinars in parallel with a Public Comment proceeding that is running from 20 April to 1 June 2020. Webinar #1 Thursday, 14 May, 14:00-15:00 UTC Remote Participation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Passcode: 30i524!6 Webinar #2 Thursday, 14 May, 23:00-00:00 UTC (Friday, 15 May 2020) Remote Participation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Passcode: a10s646$" REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process Announcement [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> On 31 March 2020, ICANN opened a call for Expressions of Interest for panelists to serve on the omnibus Standing Panel for ICANN's Independent Review Process (IRP). Candidates for the IRP omnibus Standing Panel should review the Expressions of Interest document [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>before submission. The document includes the following information: · Panel Position Description · Required or Highly Preferred Skills · Required or Highly Preferred Experience · Time Commitment · Compensation and Selection Expressions of Interest should be submitted to irp-standingpanel-eoi2020(a)icann.org<mailto:IRP-Standingpanel-EOI2020@icann.org> by 23:59 UTC on Friday, 31 July 2020. ICANN68 Planning REMINDER: ICANN68 Publication Support Executive: David Olive, Senior Vice President, Policy Development Support Design and Translation Deadline If you require design assistance for your publication, you need to provide all the text, images, layout, and publication type/size requirements (i.e. newsletter vs. 1-pager vs. trifold, etc.). You will receive a maximum of 2 iterations of the publication. Please provide everything by Wednesday, 13 May 2020. Please keep in mind that all materials, new or updated, need to be evergreen. Translation-only Deadline If your publication requires translation, please provide the final material(s) by Monday, 25 May 2020. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org<mailto:chantelle.doerksen@icann.org> and liana.teo(a)icann.org<mailto:liana.teo@icann.org>. Public Comment CLOSES TODAY: Phase 1 Initial Report of the Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 4 May 2020 CLOSES TOMORROW: Addendum to the Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 5 May 2020 Guidelines for Developing Reference Label Generation Rules (LGRs) for the Second Level Version 2 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 12 May 2020 ICANN Africa Regional Plan for Fiscal Years 2021-2025 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Wednesday, 27 May 2020 Draft PTI FY21-24 Strategic Plan [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 1 June 2020 Volume 2, Issue 36 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 7 May 2020

1 0

Consensus Playbook
by Steve Chan May 4, 2020

May 4, 2020

Dear Councilors, Originated from the Council’s PDP 3.0 initiative and a subsequent Additional Budget Request, the Consensus Playbook has been completed for the ICANN community to reference and use. This Consensus Playbook aims to provide community volunteers with practical tools and best practices for building consensus, bridging differences, and breaking deadlocks within ICANN processes. It does not seek to change the definition of consensus, the methods of decision making as prescribed in each community group’s rules and procedure, or create any new requirements. The Consensus Playbook was developed by the Consensus Building Institute (CBI), an external vendor contracted by ICANN org, with the requirement of broad applicability across the community, beyond just GNSO PDP working groups. CBI interviewed fourteen (14) ICANN community leaders across ICANN’s SOs and ACs, who shared their extensive consensus building experience in leading and participating in working groups and community groups. The playbook is quite detailed and provides guidance from the beginning to the end of the consensus building process. It stresses that consensus building should be treated as a journey and that it does not just take place at the end of deliberations. To that end, I’d like to draw attention to Appendix A, which serve as a reference guide to help inform you which “plays” within the playbook are applicable to the various phases of the community’s work. The Consensus Playbook, as developed by CBI, was designed for the ICANN community and is only permitted to be used by the ICANN community in support of ICANN related work. The playbook shall not be used for any non-ICANN related purposes. If you have any questions, please let us know. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

2 1

Re: [council] New document: GNSO Council input required
by Flip Petillion May 1, 2020

May 1, 2020

Hi Nathalie, I would like to note 1) the absence of PPSAI on this project plan, as well as 2) the timing of resuming IGO work. Best regards, Stay safe and enjoy the long weekend, Flip Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_1366071745]<http://www.petillion.law/> Attorneys – Advocaten - Avocats From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Thursday, 16 April 2020 at 20:00 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] New document: GNSO Council input required Dear all, Please note the GNSO Draft Framework for Project Planning has been posted on the wiki, with a two-week deadline for input. Please find it posted here<https://community.icann.org/display/gnsocouncilmeetings/Documents+for+GNSO+…> and provide input on the GNSO Council mailing list. 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…>

4 3

FW: [SOAC-Leaders-ICANNMeeting-Planning] Summary Notes & Action Items from today's ICANN68 Planning Call
by Drazek, Keith May 1, 2020

May 1, 2020

FYI From: SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning-bounces(a)icann.org> On Behalf Of David Olive Sent: Thursday, April 30, 2020 11:15 PM To: SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning(a)icann.org> Subject: [EXTERNAL] [SOAC-Leaders-ICANNMeeting-Planning] Summary Notes & Action Items from today's ICANN68 Planning Call ——————————- Summary Notes & Action Items from the ICANN68 Community Planning Call, 30 April 2020 Plenary & High Interest Sessions for ICANN68: * There continues to be general agreement that the plenary and cross-community sessions for the virtual Policy Forum should focus on priority policy matters and topics of high community interest. Topics that are more of an “update” can be scheduled as webinars during ICANN68 Prep Week. * The two topics for plenary sessions that drew the highest support (based on the latest survey) were DNS abuse and the Internet of Things (IoT). After some discussion, there was support for a 90-minute plenary session on DNS abuse that will also cover the topic of challenges posed by COVID-19. It was not clear if IoT as the second topic will also need a 90-minute session. * A third possible community session of interest is a 90-minute discussion between the community, ICANN org and the Board, about how to manage the community’s work in view of COVID-19 and the use of virtual meetings. * Tanzanica King will prepare a preliminary meeting schedule based on the groups’ session requests and these understandings. Other Action Items: * A separate call will be scheduled for the community planning group, outside of preparation for ICANN68, to begin discussions with ICANN org senior staff about a possible strategy for planning and specifying requirements for virtual meetings. Attached also please find the following: 1. Chat; 2. Slides; 3. Link to the audio recording in English: https://audio.icann.org/policy/icann68-policy-forum-production-30apr20-en.m…<https://secure-web.cisco.com/1mJ7UnGVNYWQ3iRiAWuSkUyAAxS7MTUO12QRUoD5whfp4_…> 4. Link to the audio recording in Spanish: https://audio.icann.org/policy/icann68-policy-forum-production-30apr20-es.m…<https://secure-web.cisco.com/1RaijlZiHsObT56evzdTRT4MdzSTrSY_6hxwtnyNK0m_W0…>

1 0

Webinar on the draft PTI FY21-FY24 Strategic Plan
by Steve Chan May 1, 2020

May 1, 2020

Dear Councilors, When Council leadership was planning the GNSO Working Sessions for ICANN67 in Cancun, they had agreed to have the IANA team and PTI Board present their draft FY21-FY24 Strategic Plan so that they could gather your feedback. Given the changes in how we are all able engage, the team will now host webinars on the topic. The webinars are scheduled for May 14th. Please see the recent announcement for details on how to participate: https://www.icann.org/news/announcement-2020-04-30-en. A Public Comment is also running https://www.icann.org/public-comments/draft-pti-fy21-24-strategic-plan-2020…. In addition to the webinars, they are also available to participate in Council meetings if desired, to discuss their future strategy or other IANA functions-related topics. If you’re interested in having them present, please let us know and we will be happy to help make the arrangements. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

1 0

Document and Motion deadline Monday 11th of May 2020 at 23:59 UTC for GNSO Council Meeting 21 May 2020 at 21:00 UTC
by Andrea Glandon May 1, 2020

May 1, 2020

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 11 May 2020 at 23:59 UTC) of the GNSO Council Meeting on Thursday 21 May 2020 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/pCWJBw Thank you. Kind Regards, Andrea Glandon GNSO SO/AC Support Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: acglandon76 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO [twitter.com]<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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0