January 2022 - council - lists.icann.org

Confirmation of GNSO Representative on the Empowered Community Administration
by Nathalie Peregrine 20 Oct '22

20 Oct '22

Dear John, Please find the attached a letter with the motion passed at the GNSO Council meeting on 29 November 2018. The Council confirmed the appointment of the GNSO Chair, currently Keith Drazek, representing the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN66. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. 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 4

FW: Moving ahead with the WS2 Community Coordination Group | Response Requested by Friday, 11 February 2022
by philippe.fouquart＠orange.com 14 Feb '22

14 Feb '22

Dear Councilors, Dear SG/C leaders, With some delay - and my apologies for this - please note the following and therefore to the SG/C a reminder to appoint/confirm a representative for this group if you haven't already. On Council's side, in addition to looking for a rep (volunteer welcome) and to avoid duplication of the work, we may want to think about how we may articulate our potential inputs to this, and future work under the GNSO Council Committee for Overseeing and Implementing Continuous Improvement, which in principle was intended to cover such non PDP related work. The discussion that we will have soon on the completion of the pilot's first task for this CCOICI would be a good opportunity to discuss this too. Regards, Philippe Orange Restricted De : soac-chairs <soac-chairs-bounces(a)icann.org> De la part de Chantelle Doerksen via soac-chairs Envoyé : mardi 25 janvier 2022 18:54 À : soac-chairs(a)icann.org Cc : Mary Wong <mary.wong(a)icann.org>; Mariana Marinho <mariana.marinho(a)icann.org>; Alperen Eken <alperen.eken(a)icann.org>; Alice Jansen <alice.jansen(a)icann.org>; Giovanni Seppia <giovanni.seppia(a)icann.org> Objet : [soac-chairs] Moving ahead with the WS2 Community Coordination Group | Response Requested by Friday, 11 February 2022 Dear SOAC Chairs, We are reaching out to you about proceeding to form the community group that will serve as an information sharing and coordinating forum for the community's implementation of certain specific recommendations from the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Work Stream 2 (WS2). As suggested in the most recent summary of the scope of work for the WS2 Community Coordination Group, we would like to request that each Supporting Organization, Advisory Committee, Regional At-Large Organization, and GNSO Stakeholder Group confirm their appointment of a representative (and alternate, if appropriate). Background In relation to a timeline, ICANN org had suggested that each SO/AC/RALO/SG complete its appointment of its primary and secondary representatives by late January or early February 2022, with the aim of having the WS2 Community Coordination Group hold an initial call before ICANN73.The initial call will allow the group to familiarize itself with its scope of work, discuss a potential timeline and a cadence for its calls. Subsequent calls would then involve discussion as to the order in which the community would approach implementing the relevant recommendations. These recommendations are Recommendation 1.1 (on proposed elements of diversity), Recommendation 1.7 (on a process for handling complaints about diversity), and Recommendation 2.3 (on a standalone framework for exercising Empowered Community powers). We understand that there may be other recommendations that can benefit from information sharing purposes as well, but wanted to flag these specific recommendations to you as those that require cross-community coordination. For quick reference, we have attached the most recent version of the WS2 Community Coordination Group Proposal for your easy reference. Next steps Given the time that has elapsed since the proposal for a WS2 Community Coordination Group was first raised with you as SOAC Chairs, we would like to ask that each SO, AC, RALO, and GNSO Stakeholder Group confirm their representative, and if appropriate, alternate, to the Group by no later than Friday, 11 February 2022. Please share the name(s) with everyone on this list, and also with your respective support staff for coordination purposes. Going forward, we envision that the work of this group will be transparent and available to the public. This means that call materials (recordings, action items, etc.), reports, and any decisions will be made available via a wiki space being created for record keeping purposes. Please let us know if you have any questions or concerns. We look forward to hearing from you. Best, Mary and Chantelle _______________________________ Chantelle Doerksen Policy Development Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) _________________________________________________________________________________________________________________________ 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.

2 2

GNSO Comment on FY23 Budget and FY 23-27 OFP
by John McElwaine 09 Feb '22

09 Feb '22

Dear GNSO Council, I am forwarding a draft of the Council's comment on the Fiscal Years 23-27 Operating and Financial Plan and FY 23 Budget. As is usual in this process, we have a clock ticking on this comment period, which closes 07 February 22, so the SCBO wanted to get you a draft to review as soon as it was ready. We have one more SCBO call scheduled this Wednesday morning and I will get an updated version circulated to Councilors by EOD on Wednesday. In the meantime, if you have any questions or revisions to this draft, please feel free to share those. Kind regards, John [https://www.nelsonmullins.com/img/ecard-logo-125.png] JOHN C. MCELWAINE PARTNER john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> LIBERTY CENTER | SUITE 600 151 MEETING STREET | CHARLESTON, SC 29401 T 843.534.4302 F 843.722.8700 101 CONSTITUTION AVENUE, NW | SUITE 900 WASHINGTON, D.C., 20001 T 202.689.2939 F 202.689.2860 NELSONMULLINS.COM<https://www.nelsonmullins.com> VCARD<https://www.nelsonmullins.com/people/john-mcelwaine/vcard> VIEW BIO<https://www.nelsonmullins.com/people/john-mcelwaine> Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message.

3 4

Reminder: Document and Motion deadline | Monday, 7 February 2022 at 23:59 UTC for GNSO Council Meeting 17 February 2022 at 06:00 UTC
by Nathalie Peregrine 04 Feb '22

04 Feb '22

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 7 February 2022 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 17 February 2022 at 06: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/gtEGCw Thank you. Nathalie

1 1

Update on the UDRP Policy Status Report
by Steve Chan 31 Jan '22

31 Jan '22

Dear Councilors, please see the email below, sent on behalf of our colleagues from the Global Domains & Strategy team. Best, Steve Dear Councilors, We are writing to provide an update on the Uniform Dispute Resolution Procedure Policy (UDRP) Policy Status Report (PSR). The purpose of the PSR is to provide an overview of the policy and to support assessment of the policy’s effectiveness. On 27 October 2021, ICANN org presented<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> to the GNSO Council a revised proposal for the PSR framework, noting that the GNSO Council comments<https://docs.google.com/document/d/1WPQE4i3NMcJjO-r7BzJpuy8Ow04mMEQpZOWWpd5…> that it had transmitted on 7 October 2021 regarding the proposed framework would be taken onboard for the UDRP PSR. Following the update to the Council, ICANN org began gathering relevant information related to the UDRP and is currently drafting the PSR. As mentioned, the PSR includes background on the UDRP processes and procedures, publicly available data on UDRP complaints and decisions, and analyses of relevant elements. ICANN org is also working with all six UDRP Providers to ensure the data being presented in the report is accurate and complete. Thus far, three UDRP Providers have reviewed the UDRP data that ICANN org had collected from their websites. We are aiming to share with the Council a preview draft of the PSR in February 2022 - prior to it being published for public comment - to ensure the substance covered aligns with your expectations. However, once we have more clarity as to when we will have received the requested data from the UDRP Providers, we will provide you with another update on progress, currently we expect this to take place in mid- to late-January 2022. Please let us know if you have questions or need additional information. Steven Chan  Senior 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<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 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…>

2 1

Small Team Convened to Propose Next Steps Regarding DNS Abuse
by Steve Chan 31 Jan '22

31 Jan '22

Dear Councilors, As many of you will recall, the GNSO Council agreed to convene a small team to consider next steps regarding DNS abuse. This email is to simply let you all know that an assignment form on the topic has been prepared by Council leadership and staff and is available on the Council’s Wiki page dedicated to its small teams, here: https://community.icann.org/x/qAWlCg. In addition, this small team is the process of scheduling its first meeting, so if any other Councilors are interested in joining the effort, it is not too late. Just respond to this email or send a note to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we can get you signed up. Best, Steve Steven Chan  Senior Director, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 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

Re: [council] SSAD ODA review - small team assignment
by philippe.fouquart＠orange.com 31 Jan '22

31 Jan '22

[with attachment] Dear All, Following our meeting with the ICANN Board last week, the leadership team has worked with the staff support team to develop the attached small team assignment to continue our analysis and review of the Operational Design Assessment (ODA) to help inform the Council's discussion with the ICANN Board. We expect the small team to commence its work in the course of next week so to this end, we would like you to identify if there are any additional volunteers, beyond those who already expressed an interest and are already identified in the assignment document. Please do so by Friday 4 February by sending a message to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. I would like to ask Justine and Jeff, our ALAC liaison and GNSO Liaison to the GAC, to share this message with their respective EPDP Phase 2 representatives. I will do the same with the SSAC and the ICANN Board. We do recognize that there is broad interest in this topic and want to make sure that the different perspectives are heard, but at the same time, we hope that the size of this small team remains manageable. Small team members will be working with their respective groups and channeling their inputs, so we are looking at a maximum of 1 person to hold the pen and join small team meetings. In the interest of transparency, the mailing list will be publicly archived and open to observers, with all meetings recorded. As discussed, the small team is expected to analyze the ODA and provide its expertise and perspectives to help inform the Council's deliberations on potential next steps and its engagement with the ICANN Board for the potential gaps that we talked about on Thursday. To assist in this process, we have identified a number of questions for the small team (see attachment). To be clear, the small team is not consensus-driven, if there is no common view on these questions within the small team, it is expected to document the different perspectives for Council consideration. We appreciate that this will require additional time and effort from those volunteering for the small team, but we welcome the opportunity to engage with all of you as well as the ICANN Board on this important topic to determine the path forward. Thanks. Philippe _________________________________________________________________________________________________________________________ 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

SSAD ODA review - small team assignment
by philippe.fouquart＠orange.com 31 Jan '22

31 Jan '22

Dear All, Following our meeting with the ICANN Board last week, the leadership team has worked with the staff support team to develop the attached small team assignment to continue our analysis and review of the Operational Design Assessment (ODA) to help inform the Council's discussion with the ICANN Board. We expect the small team to commence its work in the course of next week so to this end, we would like you to identify if there are any additional volunteers, beyond those who already expressed an interest and are already identified in the assignment document. Please do so by Friday 4 February by sending a message to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. I would like to ask Justine and Jeff, our ALAC liaison and GNSO Liaison to the GAC, to share this message with their respective EPDP Phase 2 representatives. I will do the same with the SSAC and the ICANN Board. We do recognize that there is broad interest in this topic and want to make sure that the different perspectives are heard, but at the same time, we hope that the size of this small team remains manageable. Small team members will be working with their respective groups and channeling their inputs, so we are looking at a maximum of 1 person to hold the pen and join small team meetings. In the interest of transparency, the mailing list will be publicly archived and open to observers, with all meetings recorded. As discussed, the small team is expected to analyze the ODA and provide its expertise and perspectives to help inform the Council's deliberations on potential next steps and its engagement with the ICANN Board for the potential gaps that we talked about on Thursday. To assist in this process, we have identified a number of questions for the small team (see attachment). To be clear, the small team is not consensus-driven, if there is no common view on these questions within the small team, it is expected to document the different perspectives for Council consideration. We appreciate that this will require additional time and effort from those volunteering for the small team, but we welcome the opportunity to engage with all of you as well as the ICANN Board on this important topic to determine the path forward. Thanks. Philippe _________________________________________________________________________________________________________________________ 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] Monday, 31 January 2022 | TODAY: ICANN73 Design Deadline
by Julie Bisland 31 Jan '22

31 Jan '22

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, January 31, 2022 at 10:02 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Monday, 31 January 2022 | TODAY: ICANN73 Design Deadline [https://r20.rs6.net/on.jsp?ca=29ff2ec7-4330-42d4-8bfd-74ce49ee8c49&a=112202…] Monday, 31 January 2022 ICANN Community Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Table of Contents ICANN73 Planning · NEW: ICANN Community Groups and ICANN Board Joint Sessions during ICANN73 · TODAY: ICANN73 Design Deadline · REMINDER: ICANN73 Registration is Now Open · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Information Sharing · NEW: ICANN Government Engagement Publication-Country Focus Report: China Internet-Related Policy Initiatives and Laws · NEW: Calling for NextGen@ICANN Applications for ICANN74 · NEW: IETF Year in Review for 2021 · REMINDER: Nominations for ICANN Fellowship Program Mentors Now Open · REMINDER: Apply Now for ICANN and PTI Leadership Positions · REMINDER: ICANN Community Excellence Award Nomination Period Now Open Public Comment · ICANN Draft FY23-27 Operating and Financial Plan and Draft FY23 Operating Plan and Budget · Additional Unicode Scripts for Support in Internationalized Domain Names · ICANN Bylaws Amendments: ccNSO-Proposed Changes to Article 10 and Annex B · Proposal for Myanmar Script Root Zone Label Generation Rules · NEW: Name Collision Analysis Project (NCAP) Study 2 Documents ICANN73 Planning NEW: ICANN Community Groups and ICANN Board Joint Sessions during ICANN73 ICANN Board Chair Maarten Botterman has proposed the following topics to discuss with ICANN community groups during ICANN73: · What are your key priorities for ICANN work in 2022, how do these priorities help achieve ICANN’s common objectives as expressed in the FY 2021-2025 Strategic Plan, and how do you see the ICANN community, Board, and org moving forward together on a way to achieve these? · If any, what suggestions would you have to enhance ICANN’s effectiveness and efficiency with regards to the process of implementation after adoption of a PDP or Review recommendations? Please submit your topic of interest and/or questions to board-ops-team(a)icann.org no later than Friday, 17 February 2022. TODAY: ICANN73 Design Deadline Monday, 31 January 2022: Design 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 two iterations of the publication. Please provide everything by Monday, 31 January to chantelle.doerksen(a)icann.org. Please keep in mind that all materials, new or updated, need to be evergreen. Friday, 11 February 2022: Translation Deadline If your publication requires translation, please provide the final material(s) by Friday, 11 February to chantelle.doerksen(a)icann.org. This ensures that there is enough time to translate the publication. If your materials require 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. REMINDER: ICANN73 Registration is Now Open Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> for ICANN73 is now open, and you must register to participate. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply in advance of ICANN73, and those who meet the eligibility requirements will be selected to participate. The application process [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> opens Monday, 24 January 2022. The application deadline is Friday, 18 February 2022 at 23:59 UTC. The goal of this program is to facilitate participation in ICANN Public Meetings during the pandemic. It offers community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Information Sharing NEW: ICANN Government Engagement Publication-Country Focus Report: China Internet-Related Policy Initiatives and Laws This paper covers Internet-related policy initiatives and laws/regulations put forward by China between 16 December 2015 and 5 November 2021. It is part of a periodic series of country-specific reports that provide an overview of activities relevant to the Internet ecosystem and ICANN's mission. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> NEW: Calling for NextGen@ICANN Applications for ICANN74 The Internet Corporation for Assigned Names and Numbers (ICANN) is calling for applications for the NextGen@ICANN program. ICANN wants to hear from university students living and studying in Europe who are interested in the future of the Internet and in participating in the ICANN74 Policy Forum Meeting. ICANN74 is scheduled to be held in The Hague, Netherlands from 13 to 16 June 2022. If ICANN74 is held virtually, the NextGen@ICANN Program will also be held virtually. The NextGen application window will remain open until Friday, 11 March 2022. Successful candidates will be announced Friday, 25 March 2022 on the ICANN website. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> NEW: IETF Year in Review for 2021 The ICANN Office of the Chief Technology Office has published the IETF Year in Review for 2021. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> REMINDER: Nominations for ICANN Fellowship Program Mentors Now Open ICANN Supporting Organizations and Advisory Committees are invited to nominate volunteers to serve as Fellowship Program Mentors for ICANN75-ICANN77. Each group is welcome to nominate one individual for this role, for a total of up to seven mentors. Nominations should be submitted by Friday, 25 February 2022 to fellowshipconsultation(a)icann.org. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> REMINDER: Apply Now for ICANN and PTI Leadership Positions The ICANN Nominating Committee (NomCom) invites interested individuals to submit applications for key leadership positions within ICANN Supporting Organizations and Advisory Committees, the ICANN Board, and the Public Technical Identifiers (PTI) Board of Directors. Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the Internet's technical coordination and policy development. The deadline to submit applications [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> is Friday, 11 March 2022 at 23:59 UTC. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> REMINDER: ICANN Community Excellence Award Nomination Period Now Open The nomination period for the ICANN Community Excellence Award is now open. The deadline for submissions is Monday, 21 March 2022 and the winner(s) will be announced at ICANN74. Learn more about the nomination process [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…>. Submit your nominations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…>. Request for Proposals End User Survey [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Open for Submissions Date: Friday, 14 January 2022 Closed for Submissions Date: Friday, 07 February 2022 DEI Consulting Services [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Open for Submissions Date: Friday, 14 January 2022 Closed for Submissions Date: Friday, 11 February 2022 Public Comment ICANN Draft FY23-27 Operating and Financial Plan and Draft FY23 Operating Plan and Budget [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Open for Submissions Date: Tuesday, 07 December 2021 Closed for Submissions Date: Monday, 07 February 2022 Additional Unicode Scripts for Support in Internationalized Domain Names [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Open for Submissions Date: Wednesday, 05 January 2022 Closed for Submissions Date: Tuesday, 15 February 2022 ICANN Bylaws Amendments: ccNSO-Proposed Changes to Article 10 and Annex B [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Open for Submissions Date: Thursday, 21 January 2022 Closed for Submissions Date: Wednesday, 02 March 2022 Proposal for Myanmar Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Open for submissions Date: Thursday, 13 January 2022 Closed for Submissions Date: Thursday, 03 March 2022 NEW: Name Collision Analysis Project (NCAP) Study 2 Documents [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Open for Submissions Date: Thursday, 27 January 2022 Closed for Submissions Date: Friday, 18 March 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…>. Infographic: What is Public Comment? [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Step-by-Step Public Comment Submission Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Zoom Replay: Public Comment Submission Training [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Zoom Replay: Public Comment User Experience Demonstration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> Volume 4, Issue 9 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…> | Next Issue: Thursday, 03 February 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001NcyeSuYEfY7VA1PC…>

1 0

TR: [ICANN Community Leaders] PLEASE READ - ICANN73 Stakeholders/Board sessions
by philippe.fouquart＠orange.com 31 Jan '22

31 Jan '22

Dear Councilors, Please note, the following topics questions proposed by the Board for the meeting with the SG/C chairs, as well as this call for inputs before Feb 17th. Regards, Philippe Orange Restricted De : SO-AC-SG-CLeaders <so-ac-sg-cleaders-bounces(a)icann.org> De la part de Vinciane Koenigsfeld via SO-AC-SG-CLeaders Envoyé : samedi 29 janvier 2022 10:22 À : so-ac-sg-cleaders(a)icann.org Cc : Board Ops Team <board-ops-team(a)icann.org> Objet : [ICANN Community Leaders] PLEASE READ - ICANN73 Stakeholders/Board sessions Importance : Haute Sent on behalf of Maarten Botterman, Chair, ICANN Board of Directors Dear Constituency and Stakeholder Groups Chairs, *Please reply no later than Friday 17th February 2022* First and though we are already well settled into 2022, let me wish you All a Very Happy New Year ! I believe that we are all hopeful that this year will see the end of the Covid-19 pandemic and allow us to finally meet face-to-face again. I can barely believe that it has been two years since the Board had to take the difficult decision to turn ICANN67 into a fully virtual meeting. We were far from imagining then that ICANN73 would still be virtual. Yet, it is and we are here, all of us, united and committed to make it successful. At this point in time, our hope is to be able to gather in The Hague, in June, as planned. And right now The Netherlands is in a partial lock-down which makes it difficult to further preparations. Our continued aim is to organize hybrid and in-person meetings, in the best conditions, as soon as it will be possible. We will communicate on the status of those plans based on health and safety developments. Meanwhile, we are very much looking forward to meeting with you soon and in preparation for our first meeting of 2022, ICANN73 (7-10 March), the Board and I would like to propose the following topics for discussion during our time together: · What are your key priorities for ICANN work in 2022, how do these priorities help achieve ICANN's common objectives as expressed in the FY 2021-2025 Strategic Plan, and how do you see Community, Board and org moving forward together on a way to achieve these? · If any, what suggestions would you have to enhance ICANN's effectiveness and efficiency with regards to the process of implementation after adoption of a PDP or Review recommendations? We are now well-used to the suggestion to dedicate half of our time together to discuss this topic and half the time to discuss the topic of your choice or answer the questions you might have. We would therefore like to invite you to submit your topic of interest and/or questions (please consider the limited time) to our Board Operations team (board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>) no later than Friday 17 February 2022. Your suggested questions and/or topic for discussion will be published and circulated in the Policy digest, as always, which will facilitate transparency and allow the groups to deepen their own understanding of their peers' point of views on different issues. We look forward to hearing your thoughts, questions or topics of interest and to exchange with you constructively and virtually. Best regards, Maarten Botterman Chair, ICANN Board of Directors _________________________________________________________________________________________________________________________ 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