January 2022 - council - lists.icann.org

Draft minutes of the GNSO Council meeting 20 January 2022
by Nathalie Peregrine 24 Jan '22

24 Jan '22

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting held on Thursday, 20 January 2022. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 03 February 2022. Thank you. Kind Regards, Nathalie

1 0

Action Items | GNSO Council meeting 20 January 2022
by Nathalie Peregrine 24 Jan '22

24 Jan '22

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday, 22 January 2022. Please refer to the Action Item page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> for updates on item completion progress. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. Item 4: COUNCIL DISCUSSION - Recurring Updates on the SubPro ODP Action Items:The GNSO liaison to the ODP will communicate the input to the Org ODP team after the 20 January Council meeting, including a request for a Project Plan from ICANN Org and suggestions for improvements. Item 5: COUNCIL DISCUSSION - System for Standardized Access/Disclosure (SSAD) Operational Design Phase and Next Steps and Preparation for the Consultation With the ICANN Board Action Items: GNSO Council Leadership to develop proposed assignment for a small team of GNSO Council members and EPDP Phase 2 Team members to analyze and review the ODA and provide input to the full GNSO Council for consideration and discussion. Sebastien Ducos has volunteered to do an initial review to identify any initial gaps or concerns but welcomes the assistance of members of the EPDP Phase 2 Team. Item 6: COUNCIL DISCUSSION - Next Steps for Strategic Planning Session Action Items Action Items: See the updates to the action items at: https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-gnso-cou…. GNSO Council will revisit the status of a number of identified AIs at the February Council meeting. Item 7: ANY OTHER BUSINESS 7.4 Acknowledgement of GNSO contact to the Universal Acceptance Steering Group (UASG). Action Items: The GNSO Secretariat will send an acknowledgement on behalf of the GNSO Council to Christian Dawson of the ISPCP for volunteering to be the GNSO contact to the Universal Acceptance Steering Group. 7.5 - Draft letter small team Modifying Consensus Policies (circulated 18 Jan 2022) Action Items: If no objections are received by 30 January 2022, this letter will be sent to ICANN org. Thank you! Nathalie

1 0

Reminder: Liaison to the GAC and Review of the GAC Communiqué
by philippe.fouquart＠orange.com 24 Jan '22

24 Jan '22

Dear Councilors, We have one on-going action item on our list that has been standing there for some time: leadership and liaison circulated a few ideas in November with the following email (url also in the AI list). Given the absence of feedback on this, there seems to be no appetite to pursue this further. Unless someone expressed a different view by the end of the week we will then close the AI. Thank you. Regards, Philippe De : FOUQUART Philippe INNOV/NET Envoyé : lundi 29 novembre 2021 10:00 À : council(a)gnso.icann.org Cc : gnso-secs(a)icann.org Objet : Liaison to the GAC and Review of the GAC Communiqué Dear Councilors, Leadership would like to start a conversation on a number of items that are related to the role of the GNSO Council Liaison to the GAC as well as the GNSO Council review of the GAC Communiqué. As you may recall, there are a number of recommendations that Jeff put forward in the report he shared with the Council in October (see https://mm.icann.org/pipermail/council/2021-October/025067.html), which in summary focused on; 1. If and how the GNSO should or could be more responsive to the GAC; 2. Interaction of GAC-GNSO bilateral meetings; 3. How to focus more on agreements instead of differences; 4. Include more substantive responses in the GNSO Council review of the GAC Communiqué, and; 5. GNSO to provide its own policy reports / talking points to the GAC prior to ICANN Meetings. Similarly, questions arose during the small team work on the review of the GAC Communiqué about the intent and objective of this exercise. The attached small team assignment form provides some additional detail about the current objective as well as the way the review has been conducted over the last 5+ years. However, as the origin of the review dates back to 2015, it is probably time to review whether it is still fit for purpose, and if not, consider if/how it can be adjusted. In relation to this specific item, leadership would propose that a first step in this process would be to reach out informally to the GNSO appointed Board members to see if this review still serves its original purpose as the concept was developed at the time in response to a suggestion from a Board member. Based on that feedback, the Council can then consider how to proceed. In relation to the other items, Jeff made some specific proposals but we would also like to hear from you whether: 1. You agree that further work is needed on items 1-5 above; 2. If yes, identify if/how this can be achieved. To facilitate your input, we've created a google doc that you can use to share your thoughts, see https://docs.google.com/document/d/1NdMrEL54iqJRvQTZ1qN7JgkrEvvAw5Dm/edit. Once we have sufficient input received, we can schedule this for further discussion during one of our upcoming Council meetings. Best regards, Sébastien, Tomslin & 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

TR: SubPro ODP Update 1-24-22
by philippe.fouquart＠orange.com 24 Jan '22

24 Jan '22

Dear Councilors, Please see Jeff's update on the SubPro ODP following our call on Thursday. Regards, Philippe Orange Restricted De : Jeff Neuman <jeff(a)jjnsolutions.com> Envoyé : lundi 24 janvier 2022 15:14 À : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>; Sebastien(a)registry.godaddy; Tomslin Samme-Nlar (mesumbeslin(a)gmail.com) <mesumbeslin(a)gmail.com> Cc : Steve Chan <steve.chan(a)icann.org>; SubPro ODP Mailman List <subpro-odp(a)icann.org> Objet : SubPro ODP Update 1-24-22 Please forward on to the Council Dear GNSO Council Leadership, On Friday, January 21, 2022, I had my third call with Karen Lentz and ICANN's SubPro ODP Team (which also include Steve and Emily from the Policy Team). As the call occurred the day after the GNSO council meeting, the first part of the agenda covered a discussion about both the answers to Question Set #1 and the desire for the ODP team to provide a high level project plan to the council with monthly updates so that the council can track the progress of the ODP. The ODP Team understood the request from Council and committed to providing the first high level project plan by the document deadline for the next GNSO Council meeting in February. We next discussed the ODP team's desire to hold a public session at ICANN 73 in March. Like all requested sessions at ICANN, the OPD Team put in its request for a meeting, but whether that is scheduled is up to the meetings team. It is likely that such a meeting would cover progress against the project plan, a discussion about key assumptions (possible an updated version of _____________), And an interactive question and answer session. The ODP Team intends to publish a second blog post prior to ICANN 73 as well as materials for the ICANN meeting. Next, Karen provided a recap of the most recent board resolution approving the RPM final report recommendations and the plan to include certain of the recommendations into the work of the SubPro ODP. Most of the applicable recommendations really just reaffirmed the implementation of those RPMs in the 2012 round. Finally, I asked whether there were items that could be worked on by the GNSO in parallel with the ODP. In other words, we know that certain elements of the SubPro recommendations will require work from the community. These include things like: (a) the SPIRT mechanism for reviewing changes to the program, (b) the Pre-evaluation of back-end providers, (c) community outreach and (d) Applicant Support (to name a few. It was envisioned by the working group that those things would be worked on by implementation review teams (IRTs). When those recommendations were approved by the working group, there was no concept of an ODP and therefore the working group believed that IRTs would be created within a few months of the Final Report (assuming the Board approved the Recommendations). Now that there is an ODP, this has delayed any Board approval of the recommendations. But, this work still needs to be done by the community. The question I asked Karen to discuss with ICANN leadership is whether the Board could authorize the commencement of work on these subjects by the Community so that we can get a "head start" on that work (rather than waiting a full year until the Board is in a position to approve the recommendations - after the ODP). Karen said that they would take that issue back. Our next call is scheduled for February 7th 2022 and I will provide an update shortly after that call. Please let me know if you have any questions or comments. Sincerely, Jeff Neuman GNSO Liaison to SubPro ODP [cid:image001.png@01D81166.30F41AB0] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com _________________________________________________________________________________________________________________________ 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

Doodle Poll / GNSO Council Strategic Planning Session Catch Up call
by Julie Bisland 24 Jan '22

24 Jan '22

Dear all, Due to the 9th May 2022 holiday in Russia, we are circulating the below doodle poll to schedule a new time and date for the SPS follow up call. Please complete the doodle poll below as soon as possible. Doodle poll: https://doodle.com/poll/9ysqsr9upuz2yspr?utm_source=poll&utm_medium=link Thank you! Kind regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

FW: [Ext] Monday, 24 January 2022 | DUE TODAY: FY23 Additional Budget Request Submissions
by Julie Bisland 24 Jan '22

24 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 24, 2022 at 9:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Monday, 24 January 2022 | DUE TODAY: FY23 Additional Budget Request Submissions [https://r20.rs6.net/on.jsp?ca=00b9289a-0b18-485e-a6bf-ce28fb3b119c&a=112202…] Monday, 24 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=001HRfwvG4k7FI2ffJ2…> Table of Contents ICANN73 · NEW: ICANN73 Design and Translation Deadlines · REMINDER: ICANN73 Registration is Now Open · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Information Sharing · NEW: Approved ICANN Board Resolutions from Sunday, 16 January 2022 · WEDNESDAY: Join ICANN's Virtual Discussion on Internet-Related Legislation in Canada · THURSDAY: GNSO Council and ICANN Board Consultation Regarding SSAD Recommendations · 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 Additional Budget Request Process · TODAY: Deadline to Submit FY23 Requests · FY22 Decisions · FY23 Principles · 30 November 2021 Webinar Recordings 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 · NEW: ICANN Bylaws Amendments: ccNSO-Proposed Changes to Article 10 and Annex B · Proposal for Myanmar Script Root Zone Label Generation Rules ICANN73 NEW: ICANN73 Design and Translation Deadlines 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 in Now Open Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> Information Sharing NEW: Approved ICANN Board Resolutions from Sunday, 16 January 2022 On Sunday, 16 January 2022, the ICANN Board approved the following resolutions: · IT Outsource Contract Renewal and Contract · Rights Protection Mechanisms (RPMs) Policy Development Process Final Report · Consideration of Final Declaration in the Afilias Domains No. 3 Limited (Afilias) v. ICANN Independent Review Process (.WEB) · GAC Advice: ICANN72 Virtual Annual General Meeting Communiqué (October 2021) Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> WEDNESDAY: Join ICANN's Virtual Discussion on Internet-Related Legislation in Canada ICANN is pleased to announce a briefing and interactive discussion on proposed Canadian online harms legislation. This virtual event is an opportunity for stakeholders to learn more about the proposed legislation and its impact on the Internet from a technical perspective. When: Wednesday 26 January 2022, 14:00 EST/19.00 UTC French interpretation will be provided. Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…>. THURSDAY: GNSO Council and ICANN Board Consultation Regarding SSAD Recommendations The GNSO Council and the ICANN Board will meet on Thursday, 27 January 2022 at 21:00 UTC to begin its formal consultation on the detailed findings of the System for Standardized Access/Disclosure (SSAD) Operational Design Phase (ODP). The meeting is open to observers. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> Register now [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…>. 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=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…>. Submit your nominations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…>. Additional Budget Request Process Deadline to submit requests for FY23: TODAY, Monday, 24 January 2022 FY22 Decisions [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> FY23 Principles [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> 30 November 2021 Webinar Recordings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> Open for Submissions Date: Wednesday, 05 January 2022 Closed for Submissions Date: Tuesday, 15 February 2022 NEW: 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=001HRfwvG4k7FI2ffJ2…> 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=001HRfwvG4k7FI2ffJ2…> Open for submissions Date: Thursday, 13 January 2022 Closed for Submissions Date: Thursday, 03 March 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…>. Infographic: What is Public Comment? [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> Step-by-Step Public Comment Submission Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> Zoom Replay: Public Comment Submission Training [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> Zoom Replay: Public Comment User Experience Demonstration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> Volume 4, Issue 7 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…> | Next Issue: Thursday, 27 January 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001HRfwvG4k7FI2ffJ2…>

1 0

TR: [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart RE: EPDP Phase 2 Next Steps
by philippe.fouquart＠orange.com 22 Jan '22

22 Jan '22

Hi everyone, Please note the following, and as a result ignore the letter that I forwarded yesterday on Ph2. (You will probably receive this twice once the moderator has accepted my earlier email, which was blocked due to the number of recipients - I thought directly reposting was preferable) Have a nice weekend, Philippe Orange Restricted De : FOUQUART Philippe INNOV/NET Envoyé : samedi 22 janvier 2022 19:45 À : 'council(a)gnso.icann.org' <council(a)gnso.icann.org> Cc : 'gnso-SECS' <gnso-secs(a)icann.org>; 'margiemilam(a)fb.com' <margiemilam(a)fb.com>; 'marksv(a)microsoft.com' <marksv(a)microsoft.com>; 'brian.king(a)markmonitor.com' <brian.king(a)markmonitor.com>; 'karklinsj(a)gmail.com' <karklinsj(a)gmail.com>; 'franck_journoud(a)motionpictures.org' <franck_journoud(a)motionpictures.org>; 'stefan.filipovic01(a)gmail.com' <stefan.filipovic01(a)gmail.com>; 'fasonga(a)gmail.com' <fasonga(a)gmail.com>; 'thomas(a)rickert.law' <thomas(a)rickert.law>; 'stephanie.perrin(a)mail.utoronto.ca' <stephanie.perrin(a)mail.utoronto.ca>; 'milton(a)gatech.edu' <milton(a)gatech.edu>; 'julf(a)julf.com' <julf(a)julf.com>; 'aelsadr(a)tucows.com' <aelsadr(a)tucows.com>; 'volker.greimann(a)centralnic.com' <volker.greimann(a)centralnic.com>; 'jbladel(a)godaddy.com' <jbladel(a)godaddy.com>; 'matt(a)brandsight.com' <matt(a)brandsight.com>; 'mmcross(a)amazon.com' <mmcross(a)amazon.com>; 'alan(a)donuts.email' <alan(a)donuts.email>; 'mcanderson(a)verisign.com' <mcanderson(a)verisign.com>; 'sdelbianco(a)netchoice.org' <sdelbianco(a)netchoice.org>; 'bruna.mrtns(a)gmail.com' <bruna.mrtns(a)gmail.com>; 'plommer(a)gmail.com' <plommer(a)gmail.com>; 'benakin(a)gmail.com' <benakin(a)gmail.com>; 'chair(a)rysg.info' <chair(a)rysg.info>; 'aheineman(a)godaddy.com' <aheineman(a)godaddy.com>; 'mason.cole(a)appdetex.com' <mason.cole(a)appdetex.com>; 'lschulman(a)inta.org' <lschulman(a)inta.org>; 'Wolf-Ulrich.Knoben(a)t-online.de' <Wolf-Ulrich.Knoben(a)t-online.de>; 'brenda.brewer(a)icann.org' <brenda.brewer(a)icann.org>; 'andrea.glandon(a)icann.org' <andrea.glandon(a)icann.org>; 'secretariat(a)rysg.info' <secretariat(a)rysg.info>; 'secretariat(a)icannregistrars.org' <secretariat(a)icannregistrars.org>; 'steve.chan(a)icann.org' <steve.chan(a)icann.org>; 'marika.konings(a)icann.org' <marika.konings(a)icann.org>; 'Julie.hedlund(a)icann.org' <Julie.hedlund(a)icann.org>; 'Berry.cobb(a)icann.org' <Berry.cobb(a)icann.org>; 'Mary.wong(a)icann.org' <Mary.wong(a)icann.org>; 'Caitlin.rubergen(a)icann.org' <Caitlin.rubergen(a)icann.org>; 'Emily.barabas(a)icann.org' <Emily.barabas(a)icann.org>; 'Ariel.liang(a)icann.org' <Ariel.liang(a)icann.org> Objet : TR: [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart RE: EPDP Phase 2 Next Steps Dear Councilors, Please note the following, and as a result ignore the letter that I forwarded yesterday on Ph2. Have a nice weekend, Philippe Orange Restricted De : Gnso-chairs <gnso-chairs-bounces(a)icann.org<mailto:gnso-chairs-bounces@icann.org>> De la part de Wendy Profit via Gnso-chairs Envoyé : vendredi 21 janvier 2022 23:17 À : gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Cc : Maarten Botterman <maarten.botterman(a)board.icann.org<mailto:maarten.botterman@board.icann.org>>; Secretary <secretary(a)icann.org<mailto:secretary@icann.org>>; Correspondence <Correspondence(a)icann.org<mailto:Correspondence@icann.org>>; Board Ops Team <board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>> Objet : Re: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart RE: EPDP Phase 2 Next Steps Dear GNSO Council Leadership, Please disregard the letter sent to you earlier today. It was sent in error. We will be finalizing the letter shortly and will send a revised version asap. Apologies for the inconvenience and any confusion this may cause. Thank you, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 From: Wendy Profit <wendy.profit(a)icann.org<mailto:wendy.profit@icann.org>> Date: Friday, January 21, 2022 at 12:21 PM To: "gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>" <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Cc: Maarten Botterman <maarten.botterman(a)board.icann.org<mailto:maarten.botterman@board.icann.org>>, Correspondence <Correspondence(a)icann.org<mailto:Correspondence@icann.org>>, Secretary <secretary(a)icann.org<mailto:secretary@icann.org>>, ICANN Board Ops <board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>> Subject: [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart RE: EPDP Phase 2 Next Steps Dear Philippe Fouquart, Please find the attached letter from ICANN Chair Maarten Botterman in response to your email regarding EPDP Phase 2 next steps and in advance of the GNSO + Board Consultation on 27 January 2022. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _________________________________________________________________________________________________________________________ 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

TR: [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart RE: EPDP Phase 2 Next Steps
by philippe.fouquart＠orange.com 22 Jan '22

22 Jan '22

Dear Councilors, Please note the following, and as a result ignore the letter that I forwarded yesterday on Ph2. Have a nice weekend, Philippe Orange Restricted De : Gnso-chairs <gnso-chairs-bounces(a)icann.org> De la part de Wendy Profit via Gnso-chairs Envoyé : vendredi 21 janvier 2022 23:17 À : gnso-chairs(a)icann.org; gnso-secs(a)icann.org Cc : Maarten Botterman <maarten.botterman(a)board.icann.org>; Secretary <secretary(a)icann.org>; Correspondence <Correspondence(a)icann.org>; Board Ops Team <board-ops-team(a)icann.org> Objet : Re: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart RE: EPDP Phase 2 Next Steps Dear GNSO Council Leadership, Please disregard the letter sent to you earlier today. It was sent in error. We will be finalizing the letter shortly and will send a revised version asap. Apologies for the inconvenience and any confusion this may cause. Thank you, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 From: Wendy Profit <wendy.profit(a)icann.org<mailto:wendy.profit@icann.org>> Date: Friday, January 21, 2022 at 12:21 PM To: "gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>" <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Cc: Maarten Botterman <maarten.botterman(a)board.icann.org<mailto:maarten.botterman@board.icann.org>>, Correspondence <Correspondence(a)icann.org<mailto:Correspondence@icann.org>>, Secretary <secretary(a)icann.org<mailto:secretary@icann.org>>, ICANN Board Ops <board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>> Subject: [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart RE: EPDP Phase 2 Next Steps Dear Philippe Fouquart, Please find the attached letter from ICANN Chair Maarten Botterman in response to your email regarding EPDP Phase 2 next steps and in advance of the GNSO + Board Consultation on 27 January 2022. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _________________________________________________________________________________________________________________________ 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

Reminder of Deadline: EPDP Phase 1, Rec. 12 Board Draft Board Response
by Caitlin Tubergen 21 Jan '22

21 Jan '22

Dear Councilors, We received no feedback on the draft Rec. 12 letter to the Board<https://docs.google.com/document/d/1SrGStrtUe8ZLZ2wLoUGDPK-8SYeXBnlmokmhWCT…> by the deadline of Monday, 17 January. Noting that yesterday was a holiday for some, if you would like to provide feedback, please do so as soon as possible, but no later than Wednesday, 19 January at 18:00 UTC. Thank you. Best regards, Caitlin From: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Friday, January 7, 2022 at 12:46 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: For your review: EPDP Phase 1, Rec. 12 Board Draft Board Response Dear Councilors, The EPDP Phase 1, Rec. 12 Small Team was tasked to review the Board’s understanding, as articulated in its most recent letter<https://gnso.icann.org/sites/default/files/file/field-file-attach/botterman…>, of the intent and impact of Recommendation 12 and (i) confirm the Board’s understanding or (ii) prepare clarification questions or concerns to submit to Becky Burr (the Rec. 12 board shepherd) in advance of the meeting between the Small Team and Becky. The Small Team agreed with the Board's assumptions, barring a few perceived textual imprecisions. The Small Team held a call with Becky Burr on Tuesday, 14 December, during which they discussed and clarified the Board’s assumptions. The draft letter to the Board captures the contents of that discussion, where Becky indicated the Small Team’s clarifications and proposed edits were acceptable. Here is a link to the draft board response: https://docs.google.com/document/d/1SrGStrtUe8ZLZ2wLoUGDPK-8SYeXBnlmokmhWCT…. Please review the draft response and provide any additional concerns or edits by Monday, 17 January. Thank you. Best regards, Caitlin -- Caitlin Tubergen Policy Director – GNSO ICANN

1 1

Draft GNSO Council Response to ICANN Board Regarding IDN Implementation Guidelines v4.0.
by Ariel Liang 21 Jan '22

21 Jan '22

Dear Councilors, On behalf of the GNSO Council leadership, staff is circulating the proposed GNSO Council response, developed by the leadership team, to the ICANN Board regarding the request for continued deferral of IDN Implementation Guidelines v4.0. Taking into account the presentation by RySG Councilors on 16 December 2021, this letter provides a direct response to the Board questions and suggested approach to move forward with the IDN Implementation Guidelines v4.0. Highlight of the letter: * The IDN implementation guidelines that overlap with IDNs EPDP charter questions and should continue being deferred are: 6a, 11, 12, 13, and 18 * While the RySG did not identify 6a as an overlapping item, upon further review by the GNSO Council leadership, it in fact overlaps with IDNs EPDP charter question c6. See annex of the letter for details. * Based on the understanding that non-overlapping guidelines are part of the currently applicable IDN Guidelines 3.0 and/or additional non-mandatory guidelines not covered in IDNs EPDP’s charter, the letter provides support for Board’s suggestion that those non-overlapping guidelines should move forward for Board adoption. In the absence of objections by Thursday, 20 January 2022, this letter will be sent to the ICANN Board as the GNSO Council response. Thank you for your review. Best Regards, Ariel Ariel Xinyue Liang Policy Sr. Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

2 3