October 2021 - council - lists.icann.org

Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders
by philippe.fouquart＠orange.com Oct. 14, 2021

Oct. 14, 2021

Hi everyone, This is a “last call” for your inputs on our session with the Board and the following - as the deadline is tomorrow. Thanks. Philippe From: FOUQUART Philippe INNOV/NET Sent: Friday, October 8, 2021 6:22 PM To: 'council(a)gnso.icann.org' <council(a)gnso.icann.org> Subject: RE: [council] ICANN72 Joint Session ICANN Board - Stakeholders Hi everyone, A reminder (arguably a bit close to the initial email but) to make sure you provide any comments you may have on the proposed approach for us to get back to the board by the due date – October 15th. Thank you. Best, Philippe From: FOUQUART Philippe INNOV/NET Sent: Wednesday, October 6, 2021 6:40 PM To: 'Pam Little' <pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; 'council(a)gnso.icann.org' <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: [council] ICANN72 Joint Session ICANN Board - Stakeholders Hi everyone, Thanks, Pam and Kurt for weighing in. Not having seen any further feedback, and having discussed further with Council leadership, I would like to suggest the following: 1. In relation to the Board’s question, it seems that some clarification in advance of the meeting may be helpful to ensure a productive discussion. As a result, we would like to suggest reaching out to the Board with the following follow-up questions / assumptions/ input: * The Council’s assumption is that the “we” in this question refers to the ICANN community as a whole, not just including the ICANN Board, ICANN org and the ICANN community. If that is an incorrect assumption, the Board should advise the Council accordingly. * When referring to “geopolitical” issues and mindful of the CEO’s recent blog post<https://www.icann.org/en/blogs/details/icann-president-and-ceo-goals-for-fi…>, does the Board have any specific examples (initiatives, proposals etc.) short-term and long-term in mind that they would like to address in priority? For those, on which specific issues and in what form would “we”, the ICANN community, work more closely with Governments globally, as well as educate, train and interact? * The Council would like to remind the Board of prior correspondence on this topic (see https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…) and would like to reiterate that it “would welcome further insight into ICANN org’s plans for consolidating, analysing and sharing inputs received from the community”. 2. In relation to the Board’s question to “submit your single topic of interest and/or questions”, we thought it might be helpful to ask the Board for a status update on GNSO Council approved policy recommendations/clarifications issues that are with the ICANN Board for a decision. These include: * Status of EPDP Phase 1 Recommendation #12 – see https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-… * Status of EPDP Phase 1 Recommendation #7 – see https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-… It might be possible to receive updates on the status of these items in advance of our meeting so that no time during the meeting needs to be spent on these. Furthermore, I presume that the Council might welcome an update on the expected timeline for implementation of the EPDP phase 1 recommendations and the potential impact a decision on these outstanding items may have had on that timeline. In addition, we would like to take the opportunity to provide the Board with a brief update on the Council’s plan for this year’s Strategic Planning Session and see if there is any input the Board would like to provide to help inform the Council’s discussions. If there are any concerns about this approach and/or you have any additional suggestions for topics or questions for the ICANN Board, please share these by 10 October so we can get this back to the Board in a timely manner. Best regards, Philippe From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Pam Little via council Sent: Tuesday, September 21, 2021 11:55 PM To: Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders Hi all, In case you are not aware, there is a prior correspondence from GNSO Council to ICANN org on this topic: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun… Kind regards, Pam ------------------------------------------------------------------ Sender:council@gnso.icann.org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Sent At:2021 Sep. 22 (Wed.) 04:01 Recipient:Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Cc:council@gnso.icann.org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders Thanks Kurt. Given that the sentence goes on to say "we (..) could work more closely", thats certainly not a silly question to ask... I understand this eventually as a collective effort (possibly staff initiated with community consultation) so its the whole big ICANN. Best, Philippe -------- Message d'origine -------- De : Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Date : 21/09/2021 18:13 (GMT+01:00) À : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc : council(a)gnso.icann.org<mailto:council@gnso.icann.org> Objet : Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders Hi Philippe: Thanks for this. One clarifying question: In the Board topic, who is “we”? The Board? The Board + ICANN org? The whole big ICANN? For reference, the topic is: Please provide input/comments on how you think we could efficiently identify and work more closely with Governments globally, as well as educate, train and interact when it comes to geopolitical issues relating to ICANN’s mission. I don’t know if this is a silly question or not — and if you think it is, there is no need to pursue it — but I was thinking that the advice might change depending on who “we” is. Thanks and regards, Kurt On Sep 21, 2021, at 6:35 AM, philippe.fouquart--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, Please note the topic that will be discussed during the AGM, and provide inputs as you see fit before October 15th. Regards, Philippe From: Gnso-chairs [mailto:gnso-chairs-bounces@icann.org] On Behalf Of Nathalie Peregrine via Gnso-chairs Sent: Tuesday, September 21, 2021 2:55 PM To: gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [gnso-chairs] ICANN72 Joint Session ICANN Board - Stakeholders Sent on behalf of Maarten Botterman, Chair, ICANN Board of Directors Dear Constituency and Stakeholder Groups Chairs, *Please reply no later than Friday 15 October 2021* After a few weeks of break, the Board is back into action and looking forward to meeting with you soon, albeit still virtually considering the ongoing pandemic situation. We certainly do hope that, in spite of these worldwide challenging circumstances, you managed to rest and spend quality time with your love ones. Ahead of our 23rd and second fully virtual AGM, ICANN72 (25-28 October), the Board and I would like to propose the following topic for discussion during our time together: Please provide input/comments on how you think we could efficiently identify and work more closely with Governments globally, as well as educate, train and interact when it comes to geopolitical issues relating to ICANN’s mission. As we are doing for a few years already, we would like 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 single topic of interest and/or questions (please consider the limited time if you chose to submit multiple questions) to our Board Operations team (board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>) no later than Friday 15 October 2021. 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. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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

Joint Meeting with ccNSO and GNSO Councils
by ICANN Policy Calendar Oct. 13, 2021

Oct. 13, 2021

Meeting: Joint Meeting with ccNSO and GNSO Councils Date/time: Wednesday, 20 October 2021 at 19:00 UTC for 1 hour Join Zoom Meeting: https://icann.zoom.us/j/94218282808?pwd=MThDeEpMT0NWVmdDclh4SUxqYmk4Zz09 Meeting ID: 942 1828 2808 Passcode: 9nK?Xa*NHh Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki agenda page: https://community.icann.org/x/MgNyCg Check your time zone: https://tinyurl.com/z8dkywa GNSO Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> One tap mobile +13017158592,,94218282808#,,,,*4929575289# US (Washington DC) +13126266799,,94218282808#,,,,*4929575289# US (Chicago) Webinar ID: 942 1828 2808 Meeting ID: 942 1828 2808 Passcode: 4929575289 Find your local number: https://icann.zoom.us/u/acVVG93Udj Thank you. Kind Regards, Terri

1 0

Reminder: Document and Motion deadline Sunday, 17 October 2021 at 23:59 UTC for GNSO Council Meeting 27 October 2021 at 19:30 UTC
by Nathalie Peregrine Oct. 13, 2021

Oct. 13, 2021

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 17 October 2021 at 23:59 UTC) of the GNSO Council Meeting on Wednesday, 27 October 2021 at 19:30 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/_gBmCg Thank you. Nathalie

1 2

Request ICANN Board to Appoint Liaison to IDNs EPDP
by Farell FOLLY Oct. 12, 2021

Oct. 12, 2021

Dear Councilors, The IDNs EPDP Team would like to request the ICANN Board to appoint a liaison to the EPDP Team. This message is to seek no-objection from the GNSO Council for the EPDP Team to send ICANN Board such a request. As you are aware, the GNSO received directives stemming from the ICANN Board resolution to develop policy to define all gTLDs and manage the variant labels. The ICANN Board requests that the GNSO conducts this work by taking into account the IDN variant TLD recommendations and the RZ-LGR Technical Utilization recommendations, which were approved by the Board. As the other PDPs, the final recommendations developed by this EPDP Team will come before the Board for review and approval. In addition, the EPDP Team’s former Chair Edmon Chung will transition to the ICANN Board at ICANN72. Due to the Board’s close involvement in the IDN subject and its importance in the new gTLD program, the IDNs EPDP Team believes it would be beneficial to establish a Board liaison position. Same as the Board liaisons who served in the Temporary Specification EPDP and the New gTLD Subsequent Procedures PDP, such Board liaison is expected to share on a regular basis any input the Board may have that will inform the EPDP Team deliberations and ongoing work, as well as keep the Board informed concerning the status of the Team deliberations. The Board Governance Committee recently published Guidelines <https://www.icann.org/en/system/files/files/board-liaison-guidelines-31may2…> to provide more details of the Board liaison’s roles and responsibilities. While the Guidelines requires that “a liaison(s) is only appointed if the charter of a certain project is deemed to warrant it and foresee such an appointment”, the Guidelines were published after the GNSO Council approval of the IDNs EPDP Charter. As the EPDP Team is still in the early stages of its work, it would be timely for the Board to appoint a liaison, if it agrees to do so. If there is no objection from the GNSO Council by Friday 15 October, the IDNs EPDP Team leadership will send the liaison appointment request to the ICANN Board. Thank you for your review and consideration. Best Regards, @__f_f__ Best regards ____________________________________ Lt-Colonel Farell FOLLY, Ir GNSO Councillor linkedin.com/in/farellf

1 0

FYI | FW: [Ext] Monday, 11 October 2021 | ICANN72 Prep Week Begins Tomorrow!
by Terri Agnew Oct. 11, 2021

Oct. 11, 2021

**FYI [https://r20.rs6.net/on.jsp?ca=3ffefd91-0a3b-4fdf-8d0f-bfd266cbdaa1&a=112202…] Monday, 11 October 2021 ICANN Community 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. 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=001g0RHfpR_sppSs3cn…> Table of Contents ICANN72 Resources · ICANN72 Policy Outlook Report · ICANN72 GNSO Policy Briefing · Virtual Backgrounds · Registration · ICANN72 Prep Week Schedule · ICANN72 Schedule Information Sharing · REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open Public Comment · Proposal for Japanese Script Root Zone Label Generation Rules · Proposal for Latin Script Root Zone Label Generation Rule · Draft PTI and IANA FY23 Operating Plan and Budgets · Initial Report from the EPDP on Specific Curative Rights Protection for IGOs · Proposed Amendment 5 to the .name Registry Agreement · REMINDER: ICANN Launches Improved Public Comment Feature ICANN72 Resources ICANN72 Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> ICANN72 GNSO Policy Briefing [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> ICANN72 Prep Week Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> ICANN72 Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Information Sharing REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open Applications for the NextGen@ICANN program at ICANN73 are now being accepted. The deadline for applications is Monday, 25 October 2021. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Public Comment Proposal for Japanese Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Open for Submissions Date: Thursday, 30 September 2021 Closed for Submissions Date: Tuesday, 16 November 2021 Proposal for Latin Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Open for Submissions Date: Thursday, 23 September 2021 Closed for Submissions Date: Tuesday, 23 November 2021 Draft PTI and IANA FY23 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Open for Submissions Date: Wednesday, 15 September 2021 Closed for Submissions Date: Monday, 25 October 2021 Initial Report from the EPDP on Specific Curative Rights Protections for IGOs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Open for Submissions Date: Tuesday, 14 September 2021 Closed for Submissions Date: Sunday, 24 October 2021 Proposed Amendment 5 to the .name Registry Agreement [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Open for Submissions Date: Friday, 10 September 2021 Closed for Submissions Date: Wednesday, 20 October 2021 REMINDER: ICANN Launches Improved Public Comment Feature The Information Transparency Initiative (ITI) has reached another important milestone with the release of an improved Public Comment feature. This enhanced feature is part of the ICANN organization's ongoing commitment to increase the findability and transparency of our information. Read more about the improvements! [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…>. Infographic: What is Public Comment? [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Step-by-Step Public Comment Submission Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Zoom Replay: Public Comment Submission Training [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Zoom Replay: Public Comment User Experience Demonstration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> Volume 3, Issue 75 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…> | Next Issue: Thursday, 14 October 2021 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001g0RHfpR_sppSs3cn…>

1 0

Reminder! IMPORTANT PLEASE READ! ICANN72: GNSO Council sessions to attend
by Nathalie Peregrine Oct. 11, 2021

Oct. 11, 2021

Dear all, As you may have seen, the ICANN72 schedule [72.schedule.icann.org]<https://urldefense.com/v3/__https:/72.schedule.icann.org/__;!!PtGJab4!ppa-g…> has been published. You need to register to the event and create your own ICANN72 schedule to download the events to your email calendars. Please refer to the email<https://mm.icann.org/pipermail/council/2021-September/025034.html> from Julie Bisland if this is the first time registering to the event. Please find below the list of sessions GNSO councilors are expected to attend in the upcoming weeks. 1. ICANN72 Prep week (calendar invitations to download from the ICANN meeting schedule) * GNSO Policy Update Webinar. Tuesday 12 October 2021 13:00 PDT (UTC-7) * Policy Update. Thursday 14 October 2021 09:00 PDT (UTC-7) 1. Week in between Prep Week and ICANN72 (calendar invitations have been sent via email) * Joint meeting: ccNSO & GNSO Councils. Wednesday 20 October 2021 19:00 UTC * Strategic Planning Session Virtual Meet and Greet (for 2021-2022 councilors only) Thursday 21 October 2021 20:00 UTC 1. ICANN72 (calendar invitations to download from the ICANN meeting schedule) Please note dates and times noted here are in the Seattle time zone, as the ICANN72 schedule shows sessions in your individual locations, these may differ. * GNSO Council Priorities and Prep Session. Monday 25 October 2021 12:30 PDT (UTC-7) * Joint meeting: GAC and the GNSO. Monday 25 October 2021 16:30 PDT (UTC-7) * Joint meeting: ICANN Board and GNSO Council. Tuesday 26 October 2021 09:00 PDT (UTC-7) * GNSO Council Public meeting part 1. Wednesday 27 October 2021 12:30 PDT (UTC-7) Last meeting of GNSO Council 2020 – 2021 * GNSO Council Admin meeting part 2. Wednesday 27 October 2021 15:00 PDT (UTC-7) First meeting of GNSO Council 2021-2022 * GNSO Council Wrap -Up. Thursday 28 October 2021 12:30 PDT (UTC-7) In addition to these, you may find the ICANN72 GNSO sessions (including Stakeholder Group and Constituency sessions) listed on the wiki space here<https://community.icann.org/display/gnsocouncilmeetings/ICANN72+GNSO+Remote…>. Please ensure you have all the above sessions downloaded to your calendars, and let gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> know if you run into any issues, or have any questions. Thank you! Nathalie

1 0

Candidate Statement GNSO Chair
by philippe.fouquart＠orange.com Oct. 9, 2021

Oct. 9, 2021

Dear Councilors, Please find attached my GNSO Chair Candidate Statement for this year's election. It will be posted on the GNSO website<https://gnso.icann.org/en/council/elections> shortly. Regards, 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

Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders
by philippe.fouquart＠orange.com Oct. 8, 2021

Oct. 8, 2021

Hi everyone, A reminder (arguably a bit close to the initial email but) to make sure you provide any comments you may have on the proposed approach for us to get back to the board by the due date – October 15th. Thank you. Best, Philippe From: FOUQUART Philippe INNOV/NET Sent: Wednesday, October 6, 2021 6:40 PM To: 'Pam Little' <pam.little(a)alibaba-inc.com>; Kurt Pritz <kurt(a)kjpritz.com>; 'council(a)gnso.icann.org' <council(a)gnso.icann.org> Subject: RE: [council] ICANN72 Joint Session ICANN Board - Stakeholders Hi everyone, Thanks, Pam and Kurt for weighing in. Not having seen any further feedback, and having discussed further with Council leadership, I would like to suggest the following: 1. In relation to the Board’s question, it seems that some clarification in advance of the meeting may be helpful to ensure a productive discussion. As a result, we would like to suggest reaching out to the Board with the following follow-up questions / assumptions/ input: * The Council’s assumption is that the “we” in this question refers to the ICANN community as a whole, not just including the ICANN Board, ICANN org and the ICANN community. If that is an incorrect assumption, the Board should advise the Council accordingly. * When referring to “geopolitical” issues and mindful of the CEO’s recent blog post<https://www.icann.org/en/blogs/details/icann-president-and-ceo-goals-for-fi…>, does the Board have any specific examples (initiatives, proposals etc.) short-term and long-term in mind that they would like to address in priority? For those, on which specific issues and in what form would “we”, the ICANN community, work more closely with Governments globally, as well as educate, train and interact? * The Council would like to remind the Board of prior correspondence on this topic (see https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…) and would like to reiterate that it “would welcome further insight into ICANN org’s plans for consolidating, analysing and sharing inputs received from the community”. 2. In relation to the Board’s question to “submit your single topic of interest and/or questions”, we thought it might be helpful to ask the Board for a status update on GNSO Council approved policy recommendations/clarifications issues that are with the ICANN Board for a decision. These include: * Status of EPDP Phase 1 Recommendation #12 – see https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-… * Status of EPDP Phase 1 Recommendation #7 – see https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-… It might be possible to receive updates on the status of these items in advance of our meeting so that no time during the meeting needs to be spent on these. Furthermore, I presume that the Council might welcome an update on the expected timeline for implementation of the EPDP phase 1 recommendations and the potential impact a decision on these outstanding items may have had on that timeline. In addition, we would like to take the opportunity to provide the Board with a brief update on the Council’s plan for this year’s Strategic Planning Session and see if there is any input the Board would like to provide to help inform the Council’s discussions. If there are any concerns about this approach and/or you have any additional suggestions for topics or questions for the ICANN Board, please share these by 10 October so we can get this back to the Board in a timely manner. Best regards, Philippe From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Pam Little via council Sent: Tuesday, September 21, 2021 11:55 PM To: Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> Cc: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders Hi all, In case you are not aware, there is a prior correspondence from GNSO Council to ICANN org on this topic: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun… Kind regards, Pam ------------------------------------------------------------------ Sender:council@gnso.icann.org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Sent At:2021 Sep. 22 (Wed.) 04:01 Recipient:Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Cc:council@gnso.icann.org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject:Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders Thanks Kurt. Given that the sentence goes on to say "we (..) could work more closely", thats certainly not a silly question to ask... I understand this eventually as a collective effort (possibly staff initiated with community consultation) so its the whole big ICANN. Best, Philippe -------- Message d'origine -------- De : Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Date : 21/09/2021 18:13 (GMT+01:00) À : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc : council(a)gnso.icann.org<mailto:council@gnso.icann.org> Objet : Re: [council] ICANN72 Joint Session ICANN Board - Stakeholders Hi Philippe: Thanks for this. One clarifying question: In the Board topic, who is “we”? The Board? The Board + ICANN org? The whole big ICANN? For reference, the topic is: Please provide input/comments on how you think we could efficiently identify and work more closely with Governments globally, as well as educate, train and interact when it comes to geopolitical issues relating to ICANN’s mission. I don’t know if this is a silly question or not — and if you think it is, there is no need to pursue it — but I was thinking that the advice might change depending on who “we” is. Thanks and regards, Kurt On Sep 21, 2021, at 6:35 AM, philippe.fouquart--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, Please note the topic that will be discussed during the AGM, and provide inputs as you see fit before October 15th. Regards, Philippe From: Gnso-chairs [mailto:gnso-chairs-bounces@icann.org] On Behalf Of Nathalie Peregrine via Gnso-chairs Sent: Tuesday, September 21, 2021 2:55 PM To: gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [gnso-chairs] ICANN72 Joint Session ICANN Board - Stakeholders Sent on behalf of Maarten Botterman, Chair, ICANN Board of Directors Dear Constituency and Stakeholder Groups Chairs, *Please reply no later than Friday 15 October 2021* After a few weeks of break, the Board is back into action and looking forward to meeting with you soon, albeit still virtually considering the ongoing pandemic situation. We certainly do hope that, in spite of these worldwide challenging circumstances, you managed to rest and spend quality time with your love ones. Ahead of our 23rd and second fully virtual AGM, ICANN72 (25-28 October), the Board and I would like to propose the following topic for discussion during our time together: Please provide input/comments on how you think we could efficiently identify and work more closely with Governments globally, as well as educate, train and interact when it comes to geopolitical issues relating to ICANN’s mission. As we are doing for a few years already, we would like 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 single topic of interest and/or questions (please consider the limited time if you chose to submit multiple questions) to our Board Operations team (board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>) no later than Friday 15 October 2021. 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. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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

FYI | FW: [Ext] Thursday, 07 October 2021 | ICANN72 Policy Outlook Report Now Available!
by Terri Agnew Oct. 7, 2021

Oct. 7, 2021

FYI [https://r20.rs6.net/on.jsp?ca=62f2434f-257c-449a-95be-793b3bf6f790&a=112202…] Thursday, 07 October 2021 ICANN Community 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. 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=0016iK67-a3ckw5y7V8…> Table of Contents ICANN72 Resources · NEW: ICANN72 Policy Outlook Report · NEW: ICANN72 GNSO Policy Briefing · Virtual Backgrounds · Registration · ICANN72 Prep Week Schedule · ICANN72 Schedule Information Sharing · NEW: Supporting a Respectful Virtual Environment During ICANN Public Meetings · NEW: ICANN's Contractual Compliance Monthly Reports Are Now Available to the Public · NEW: ICANN President and CEO Goals for Fiscal Year 2022 · NEW: ICANN Celebrates the Five-Year Anniversary of the IANA Stewardship Transition · 🚨TOMORROW 🚨: ICANN Continues the Pandemic Internet Access Reimbursement Program · REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open Public Comment · Proposal for Japanese Script Root Zone Label Generation Rules · Proposal for Latin Script Root Zone Label Generation Rule · Draft PTI and IANA FY23 Operating Plan and Budgets · Initial Report from the EPDP on Specific Curative Rights Protection for IGOs · Proposed Amendment 5 to the .name Registry Agreement · REMINDER: ICANN Launches Improved Public Comment Feature ICANN72 Resources ICANN72 Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> ICANN72 GNSO Policy Briefing [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> ICANN72 Prep Week Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> ICANN72 Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Information Sharing NEW: Supporting a Respectful Virtual Environment During ICANN Public Meetings The upcoming ICANN72 will be our second virtual Annual General Meeting, and the sixth ICANN Public Meeting held completely online. While virtual participation has long been a necessary and useful way for our global stakeholders to take part in the ICANN multistakeholder processes, the transition to a solely virtual environment has been an adjustment for many. Some of the virtual participation tools [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> we use are a good proxy for in-person interaction, yet some interactions do not translate as easily online. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> NEW: ICANN's Contractual Compliance Monthly Reports Are Now Available to the Public ICANN announced that the Contractual Compliance team is now publishing its monthly reports online, as part of its mission is to preserve the security, stability, and resiliency of the Domain Name System (DNS) and to promote consumer trust. These reports summarize the function's activities during the month. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> NEW: ICANN President and CEO Goals for Fiscal Year 2022 We live in a time of change, and the speed of change is accelerating. From my perspective, some aspects of this change have a greater impact on ICANN organization (org) than on others. To fulfill our mission, we must continue to evolve and develop innovative approaches to handle the challenges that come our way. Each year, I work with the Board and the org's Executive team to develop goals for the coming fiscal year. I develop the first seven goals, and the Board develops additional goals. They reflect the challenges we face and what we have learned about what the ICANN ecosystem needs to continue to fulfill our mission. I am sharing them with you as part of our collective commitment to accountability and transparency. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> NEW: ICANN Celebrates the Five-Year Anniversary of the IANA Stewardship Transition Five years ago the Internet reached an historic stage in its evolution. On 1 Octobe [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…>r 2016 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…>, the U.S. Department of Commerce, National Telecommunications and Information Administration (NTIA) transitioned the coordination and management of the Internet's unique identifiers to the global Internet community. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> 🚨TOMORROW 🚨: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply in advance of ICANN72, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 08 October 2021 at 23:59 UTC. The application process opens today, and program details are available here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…>. 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. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open Applications for the NextGen@ICANN program at ICANN73 are now being accepted. The deadline for applications is Monday, 25 October 2021. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Public Comment Proposal for Japanese Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Open for Submissions Date: Thursday, 30 September 2021 Closed for Submissions Date: Tuesday, 16 November 2021 Proposal for Latin Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Open for Submissions Date: Thursday, 23 September 2021 Closed for Submissions Date: Tuesday, 23 November 2021 Draft PTI and IANA FY23 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Open for Submissions Date: Wednesday, 15 September 2021 Closed for Submissions Date: Monday, 25 October 2021 Initial Report from the EPDP on Specific Curative Rights Protections for IGOs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Open for Submissions Date: Tuesday, 14 September 2021 Closed for Submissions Date: Sunday, 24 October 2021 Proposed Amendment 5 to the .name Registry Agreement [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Open for Submissions Date: Friday, 10 September 2021 Closed for Submissions Date: Wednesday, 20 October 2021 REMINDER: ICANN Launches Improved Public Comment Feature The Information Transparency Initiative (ITI) has reached another important milestone with the release of an improved Public Comment feature. This enhanced feature is part of the ICANN organization's ongoing commitment to increase the findability and transparency of our information. Read more about the improvements! [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…>. Infographic: What is Public Comment? [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Step-by-Step Public Comment Submission Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Zoom Replay: Public Comment Submission Training [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Zoom Replay: Public Comment User Experience Demonstration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> Volume 3, Issue 74 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…> | Next Issue: Monday, 11 October 2021 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0016iK67-a3ckw5y7V8…>

1 0

ICANN72 GNSO Policy Briefing Available for Download
by Emily Barabas Oct. 6, 2021

Oct. 6, 2021

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN72 is now available for download at https://go.icann.org/gnsobriefing If you have any comments and/or suggestions on how we can further facilitate your preparation for ICANN72, please let us know. Kind regards, Emily

1 0