February 2023 - council - lists.icann.org

Action Items - GNSO Council meeting | 16 February 2023
by Nathalie Peregrine Feb. 22, 2023

Feb. 22, 2023

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday 16 February 2023. 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 3: Consent Agenda * Nomination of a Mentor for the ICANN Fellowship Selection Committee - Taiwo Peter Akinremi Action Items: The GNSO Secretariat: 1. Communicates to staff supporting the ICANN Fellowship Program that the GNSO has nominated Taiwo Peter Akinremi to serve as a Fellowship Selection Committee member for six consecutive ICANN meetings, beginning with ICANN78. 2. Informs Taiwo Peter Akinremi that he has been nominated by the GNSO to serve as a Fellowship Selection Committee member for six consecutive ICANN meetings, beginning with ICANN78. 3. Sends a response to the applicants who were not nominated, thanking them for their interest and encouraging them to apply for future opportunities as they arise * Motion for the Adoption of the Revised Charter for the Budget and Operations Townhall Action Items: The GNSO Council thanks the Council members and subject matter experts that have contributed to the SCBO throughout its lifespan. Item 4: COUNCIL VOTE - Adoption of the Amended Charter for the Transfer Policy Review PDP and Approval of the Project Change Request Action Items: Policy support staff updates the TPR project plan, charter, and other materials and posts on the working group wiki to reflect the Project Change Request approved by the GNSO Council. Item 6: COUNCIL DISCUSSION - Update on the Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI)’s Working Group Self-Assessment Recommendations Report and Update from the Statement of Interest (SOI) Task Force Action Items: Council members to review WGSA Recommendations Report and be prepared to consider the report for adoption during the next Council meeting. Item 7: COUNCIL DISCUSSION - ICANN76 Meeting Planning Action Items: In coordination with GNSO Council leadership, staff to circulate to the GNSO Council for consideration a list of suggested topics for the bilateral meetings at ICANN76. Item 8: COUNCIL DISCUSSION - PDP Improvements item #8 (Review of the Policy & Implementation recommendations) Action Items: GNSO Council members to review the background information on PDP Improvements item #8 (Review of the Policy & Implementation recommendations) and indicate if they have any objections to proceeding with the Policy Status Report (PSR) by the March Council meeting. If there are no objections, staff will move forward with the PSR. Item 9: COUNCIL DISCUSSION - Uniform Domain Name Dispute Resolution Policy (UDRP) Review Next Steps Action Items: The GNSO Council agrees to defer for 18 months and to provide a rationale for its decision.

1 0

Re: [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions
by Steve Chan Feb. 22, 2023

Feb. 22, 2023

Dear Councilors, Please find a Google doc created for this exercise. Permissions are currently set to allow for comments, but once we know who will be taking part in the effort besides Paul, we will provide Editor rights: https://docs.google.com/document/d/1igtbNSUBMc3cIFlR7-zTyg5epNwfm7ImkxaP_K-… Note that in the Google document, we have also included the potential questions to the ICANN Board as by shared by Sebastien. We are assuming that similar planning will be needed once the topics are agreed to by the Council. It sounds like the Councilors will organize themselves, but if you need any assistance from support staff, just let us know. Best, Steve From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> on behalf of Sebastien--- via Gnso-chairs <gnso-chairs(a)icann.org> Reply-To: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy> Date: Friday, February 17, 2023 at 1:48 AM To: Paul McGrady <paul(a)elstermcgrady.com>, "COUNCIL(a)GNSO.ICANN.ORG" <council(a)gnso.icann.org>, GNSO-Chairs <gnso-chairs(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Hi Paul, Thank you for raising your hand for this, it is much appreciated. I think that in the past we would have taken this to the mailing list, but I must admit it is not my favorite medium: I tend to get quickly lost in the sub-threads (I am probably showing my age). The current thinking should lead us to a small team setup, but given the short timelines I wouldn’t want to waste any of it haggling over how to form it. Could I suggest that: 1. We initiate immediately a bespoke small team headed by Paul McGrady + eventually a single co-lead from the other house should anyone volunteer. 2. Membership to open to all Councillors. Should any Councillor need external input, he/she can seek it but remains the small team sole member. 3. Staff to create a bespoke Google Doc with the Board’s questions. 4. The small team takes it from there with the aim of gathering our thoughts by March 3rd. Council colleagues: Thoughts? Comments? Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1287335570] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Paul McGrady <paul(a)elstermcgrady.com> Date: Thursday, 16 February 2023 at 4:32 pm To: Sebastien Ducos <Sebastien(a)registry.godaddy>, COUNCIL(a)GNSO.ICANN.ORG <council(a)gnso.icann.org>, GNSO-Chairs <gnso-chairs(a)icann.org>, gnso-secs(a)icann.org <gnso-secs(a)icann.org> Subject: RE: PLEASE READ - ICANN76 Stakeholders/Board sessions You don't often get email from paul(a)elstermcgrady.com. Learn why this is important [aka.ms]<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;…> Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Thanks Seb! I think our questions to the Board proposed below look great and touch on important concerns. As for Tripti’s question, what will be our mechanism to respond? Should we (1) start a shared document that folks can contribute to, (2) do we want to run a short-lived small team to develop a draft for the broader Council to review (I’m happy to lead that effort if you like), (3) do we send ideas to the mailing list and have staff compile them and then we all edit the compilation, (4) something else? Also, we need to have milestone deadlines so that we aren’t scrambling and doing this on airplanes to Cancun. Thanks! Best, Paul From: council <council-bounces(a)gnso.icann.org> On Behalf Of Sebastien--- via council Sent: Thursday, February 16, 2023 9:01 AM To: COUNCIL(a)GNSO.ICANN.ORG; GNSO-Chairs <gnso-chairs(a)icann.org>; gnso-secs(a)icann.org Subject: Re: [council] PLEASE READ - ICANN76 Stakeholders/Board sessions Dear Council Colleagues, A short note to correct my previous email: While the Board would like us to prepare our response to their question ahead of our meeting, the March 1st deadline if for us to submit our questions to them. Here are some questions already floated: * Ensuring Board and ICANN org input to PDP processes How do we minimize the need for an ODP and minimize its impact when it is needed? What further information or details should the GNSO integrate into a PDP Final Report to ensure it delivers Board-ready recommendations? * Getting to the next round of new gTLDs What in the Boards view would be required of the GNSO Council and Community to secure a Next Round Launch Date by the 2023 AGM? * WHOIS Disclosure System The Council’s recommendations were delivered 3 months ago which corresponds to ICANN Org’s ramp up requirement; has the development been initiated? What assistance can the Council and its small team offer to ensure initial timelines are met? Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3093328915] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Sebastien--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Date: Thursday, 16 February 2023 at 2:00 pm To: COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, GNSO-Chairs <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>> Subject: [council] FW: PLEASE READ - ICANN76 Stakeholders/Board sessions Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear Council Colleagues, Please find below a letter from Tripti Sinha on behalf of the Board regarding our session in Cancun. In particular the Board would like for us to respond to the following by March 1st: The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT). IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented. What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process? Please be as concrete as possible. Please note that as per our discussion with Becky today, I also expect we will receive a list of clarifying questions on the SubPro Recommendations themselves. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1469584128] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Gnso-chairs <gnso-chairs-bounces(a)icann.org<mailto:gnso-chairs-bounces@icann.org>> on behalf of Vinciane Koenigsfeld via Gnso-chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Date: Tuesday, 14 February 2023 at 7:23 pm To: gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org> <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Cc: becky.burr(a)board.icann.org<mailto:becky.burr@board.icann.org> <becky.burr(a)board.icann.org<mailto:becky.burr@board.icann.org>>, matthew.shears(a)board.icann.org<mailto:matthew.shears@board.icann.org> <matthew.shears(a)board.icann.org<mailto:matthew.shears@board.icann.org>> Subject: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors Dear Generic Names Supporting Organization Council Leaders, *Please reply no later than Wednesday 1 March 2023* The Board and I very much look forward to welcoming and meeting with you during ICANN76 in Cancún, between 11-16 March. It is with great pleasure and excitement that we are finally going to Mexicó, after having had to cancel the in-person component of both ICANN67 and ICANN70. We are grateful to our friends and stakeholders in Latin America for their patience and understanding in the process, and delighted to say ¡ Cancún aquí vamos! (Cancún, here we are!). The last three years have certainly proven eventful for all of us, but in unison with ICANN organization, we are more determined than ever to work closely with you to make 2023 and the many years after that, productive and successful. This time in particular, the Board proposes a slight change in the approach to our bilateral sessions. We understood that there was an appetite for questions more tailored to each stakeholder group’s needs. Therefore, we will not be sending the same question from the Board to all of you. Having said this, to maintain our commitment to transparency, all of the questions the Board to sends to each group will be published in the Community Digest. The second improvement that we are putting in place starting at ICANN76, is to provide you with a summary of what we heard from you during these bilateral sessions. This summary will be in two forms: 1. A blog highlighting key take aways from ICANN76 (and every ICANN meeting after that) 2. Summaries of bilateral sessions will be included in the Policy Outcomes Report we publish after each ICANN meeting These are only initial steps, and we will continue to discuss with you ways improve the way we interact moving forward. In the meantime, please find herewith the questions we would like to ask your Group ahead of our joint session in Cancún: The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT). IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented. What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process? Please be as concrete as possible. We look forward to hearing your thoughts on this soon. We would be grateful if you could send to Board Operations (board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>) the questions you would like the Board to address during our face-to-face meetings. Given the finite time available for these meetings, please list your questions in order of priority. We would also appreciate getting your questions no later than Wednesday 1 March, 2023. We thank you in advance for your time on this matter. Best regards, Tripti Sinha Chair, ICANN Board of Directors

9 11

Small Team on SubPro ODA
by Sebastien＠registry.godaddy Feb. 22, 2023

Feb. 22, 2023

Hello Anne, Justine, Susan, Jeff and Thomas, As our conversation with the Board on SubPro is moving on to its next stage, leadership agreed to bring the SubPro ODA small team to an end. We thank you for your valuable input and capacity to deliver on such short timelines. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3476297097] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0

ODP Liaison - Thank you
by Sebastien＠registry.godaddy Feb. 22, 2023

Feb. 22, 2023

Dear Jeff, Following your question during our January Council Meeting, I wanted to reach out and confirm that the ODP Liaison role has come to an end, thereby relieving you from any day to day duties related to it. We will of course reach out for your comments on the process when evaluation time comes. I would like to thank you on behalf of the GNSO Council for the time and energy you put into the role for the better part of the last 18 months, since your appointment. This is much appreciated. Please don’t hesitate to reach out should you have any questions. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_789535678] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0

GNSO Council Related Sessions at ICANN76
by Steve Chan Feb. 21, 2023

Feb. 21, 2023

Dear Councilors, At action item was identified during the February Council meeting to circulate proposed topics from Council leadership and staff for the joint meetings (i.e., ICANN Board, ccNSO, GAC) and the GNSO working sessions. You can see the proposed topics here: https://docs.google.com/document/d/1aPpNkqf4c_lyJCPmA9CCrpp4sScQeI3x0gEsusV… (and attached as a Word doc). Please feel free of course to provide comments on the mailing list or in the Google doc. 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

Meeting Invitation | Joint Meeting: ICANN Board and GNSO on SubPro discussion | Tuesday, 28 February 2023 at 18:00 UTC
by Terri Agnew Feb. 21, 2023

Feb. 21, 2023

Dear all, The Joint ICANN Board and GNSO Council on SubPro discussion will take place on Tuesday, 28 February 2023 at 18:00 UTC for 60 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/95350985362?pwd=NGpIcDhOZThNVDl4d1FsVmowaCtlQT09 Passcode: 28GNSO-BD# If you are joining via audio only: One tap mobile : US: +19294362866,,95350985362#,,,,*7240367063# or +13017158592,,95350985362#,,,,*7240367063# Or Telephone: Dial(for higher quality, dial a number based on your current location): Webinar ID: 953 5098 5362 Phone Only Passcode: 7240367063 International numbers available: https://icann.zoom.us/u/ad5DVFGeyu Thank you. Kind regards, Terri

1 0

ICANN76 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland Feb. 21, 2023

Feb. 21, 2023

Dear all, With ICANN76<https://meetings.icann.org/en/icann76> just around the corner, please take a moment to read the information below for a seamless and successful meeting. REGISTER NOW! DEADLINE TO REGISTER IS 08 MARCH 2023! * Sign into Your ICANN Account or create an account here<https://account.icann.org/login>. * Register by selecting the Meeting Registration tile. * Click on the Registration link. Before creating your schedule, please read this page carefully: https://meetings.icann.org/en/remote-participation. If participating on-site, please read the Health and Safety page<https://meetings.icann.org/en/76healthandsafety>. CREATE YOUR MEETING SCHEDULE * Access the schedule here<https://icann76.sched.com/>. The schedule shows up with blank radial buttons to the left of each session. Hover over the radial button and click “ADD TO MY SCHEDULE” or just click to add the checkmark. * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. * Click the Phone icon * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to you, to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior. * Visit the Participation Tools page<https://meetings.icann.org/en/remote-participation> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN76 Meeting Schedule<https://icann76.sched.com/> GNSO ICANN76 Wiki Page<https://community.icann.org/x/RAKBDQ> GNSO Session agendas<https://community.icann.org/x/QgKBDQ> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- 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

NEW: Supporting a Multilingual Internet: ICANN Publishes 2022 IDN Annual Report
by Nathalie Peregrine Feb. 20, 2023

Feb. 20, 2023

From: David Olive <david.olive(a)icann.org> Reply to: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, 20 February 2023 at 17:00 To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Subject: [Ext] NEW: Supporting a Multilingual Internet: ICANN Publishes 2022 IDN Annual Report Monday, 20 February 2023 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=001eXezxGeHoQKTq_m6…> Table of Contents ICANN76 Resources · CLOSES FRIDAY: ICANN Continues the Pandemic Internet Access Reimbursement Program Information Sharing · ON WEDNESDAY: Join the Webinar and Apply for the NextGen@ICANN Program at ICANN77 · NEW: ICANN Announces Recipients of the ICANN77 Fellowship · NEW: Supporting a Multilingual Internet: ICANN Publishes 2022 IDN Annual Report · REMINDER: ICANN77 Community Childcare Grants Pilot Program Application · REMINDER: Apply Now for ICANN and PTI Leadership Positions · REMINDER: ICANN Community Excellence Award Nomination Period Now Open Public Comment · Proposed Procedure for Selecting a Top-Level Domain String for Private Use · Additional Script-Based Reference Label Generation Rules and Related Updates ICANN76 Resources Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Prep Week Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Zoom Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Health & Safety [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> CLOSES FRIDAY: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply in advance of ICANN76, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 24 February 2023 at 23:59 UTC. Since ICANN76 will be conducted as a hybrid meeting, only applicants that attend virtually are eligible for this program. The program details are available here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Information Sharing ON WEDNESDAY: Join the Webinar and Apply for the NextGen@ICANN Program at ICANN77 The Internet Corporation for Assigned Names and Numbers (ICANN) is calling for applications [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> for the ICANN77 Policy Forum. The NextGen@ICANN Program application window will remain open until 31 March 2023. To inform potential applicants about the NextGen@ICANN Program and the application process for ICANN77, ICANN is hosting a webinar . When: 22 February 2023 19:00 Universal Time UTC Register in advance for this webinar: https://icann.zoom.us/webinar/register/WN_XAq6MOyHTfeqxj4GgxEWpg [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> NEW: ICANN Announces Recipients of the ICANN77 Fellowship ICANN announced the successful candidates selected to participate in the ICANN Fellowship Program at the ICANN77 Policy Forum. A total of 40 applicants from 26 countries will take part in the 12–15 June 2023 meeting in Washington, D.C., USA. The successful candidates represent all sectors of society including civil, government, country code top-level domain operations, academia, business, technical, security, and end-user groups. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> NEW: Supporting a Multilingual Internet: ICANN Publishes 2022 IDN Annual Report Internet Corporation for Assigned Names and Numbers (ICANN) published the 2022 Internationalized Domain Name (IDN) Annual Report. The report provides an overview of the status of IDNs at the top and second levels of the Domain Name System (DNS), as well as the IDN-related work being done by the ICANN organization (ICANN org) and community. The full report is available here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> REMINDER: ICANN77 Community Childcare Grants Pilot Program Application ICANN is opening the application round for its Community Childcare Grants Pilot Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> for ICANN77 in Washington, DC. The program facilitates in-person participation of community members with children who are 12 years old or younger at ICANN Public Meetings and eligible ICANN events. Deadline: Friday, 10 March 2023 at 23:59 UTC Apply here. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> REMINDER: Apply Now for ICANN and PTI Leadership Positions The Nominating Committee (NomCom) of ICANN is accepting applications for key leadership positions within ICANN's Supporting Organizations and Advisory Committees, the ICANN Board of Directors, and the Public Technical Identifiers (PTI) Board of Directors. The deadline to submit applications [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> is 23 March 2023 at 23:59 Coordinated Universal Time (UTC). Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> 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 Tuesday, 28 March 2023 and the winner(s) will be announced at ICANN77. Learn more about the nomination process [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…>. Submit your nominations. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Public Comment Proposed Procedure for Selecting a Top-Level Domain String for Private Use [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Open for submissions date: 13 January 2023 Closed for submissions date: 28 February 2023 Additional Script-Based Reference Label Generation Rules and Related Updates [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Open for submissions date: 19 January 2023 Closed for submissions date: 03 March 2023 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…>. Volume 5, Issue 14 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> | Next Issue: Thursday, 23 February 2023 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe nathalie.peregrine(a)icann.org [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=un&m=00…> Update Profile [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=oo&m=00…> | Constant Contact Data Notice [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> powered by [Image removed by sender. Trusted Email from Constant Contact - Try it FREE today.][r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…> Try email marketing for free today! [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001eXezxGeHoQKTq_m6…>

1 0

Re: [council] [gnso-secs] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions
by Nathalie Peregrine Feb. 20, 2023

Feb. 20, 2023

Hello all! I’ve given Paul, Susan, Tomslin, Mark and Jeff editing rights to the document. Please let me know if others want to join. Thank you, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Reply to: Susan Payne <susan.payne(a)comlaude.com> Date: Monday, 20 February 2023 at 08:51 To: Paul McGrady <paul(a)elstermcgrady.com>, "Mark W. Datysgeld" <mark(a)governanceprimer.com>, Steve Chan <steve.chan(a)icann.org>, "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy>, "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [gnso-secs] [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Hi all, I’d like to join this team too, thanks. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01D94523.6AFBD080][comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!7131yaNn7gb0FU…> From: council <council-bounces(a)gnso.icann.org> On Behalf Of Paul McGrady via council Sent: Saturday, February 18, 2023 12:14 PM To: Mark W. Datysgeld <mark(a)governanceprimer.com>; Steve Chan <steve.chan(a)icann.org>; Sebastien(a)registry.godaddy; COUNCIL(a)GNSO.ICANN.ORG; GNSO-Chairs <gnso-chairs(a)icann.org>; gnso-secs(a)icann.org Subject: Re: [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Disclaimers: Subject to a final greenlight from Council Leadership to proceed. Written early in the morning on a Saturday – forgive typos. Thanks Mark! All, it would be great to have 1 or 2 more so that we are sure to get a full range of eyes on this, especially helpful if they were Non-commercial and Contracted Parties voices to round us out. Special request that Jeff join the team as this is a question from the GAC. Also, if you don’t have time to participate on the bespoke small team but have thoughts on Tripti’s question, please do put your comments into the document (diamonds in the rough welcome – the team can polish later). Best, Paul From: Mark W. Datysgeld <mark(a)governanceprimer.com<mailto:mark@governanceprimer.com>> Sent: Friday, February 17, 2023 11:22 PM To: Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>>; Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>; Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>; COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Since I have been been banging the drum about Council-Board interaction, I think I should step up for this team. Lead us to greatness, Paul. --- Mark W. Datysgeld Director at Governance Primer ICANN GNSO Councilor ________________________________ From: Paul McGrady via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Sent: Friday, February 17, 2023 18:37 To: Steve Chan; Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>; COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; GNSO-Chairs; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Thanks Steve! The document looks great. I’ll await the final greenlight from Seb that the bespoke small team is the final plan and then the resulting flood of volunteers. Once we are at that point, I hope Staff will send around a Doodle to help us get our kickoff meeting scheduled. Best, Paul From: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Sent: Friday, February 17, 2023 1:14 PM To: Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>; Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>>; COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Dear Councilors, Please find a Google doc created for this exercise. Permissions are currently set to allow for comments, but once we know who will be taking part in the effort besides Paul, we will provide Editor rights: https://docs.google.com/document/d/1igtbNSUBMc3cIFlR7-zTyg5epNwfm7ImkxaP_K-… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1igtbNSUBMc3c…> Note that in the Google document, we have also included the potential questions to the ICANN Board as by shared by Sebastien. We are assuming that similar planning will be needed once the topics are agreed to by the Council. It sounds like the Councilors will organize themselves, but if you need any assistance from support staff, just let us know. Best, Steve From: Gnso-chairs <gnso-chairs-bounces(a)icann.org<mailto:gnso-chairs-bounces@icann.org>> on behalf of Sebastien--- via Gnso-chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Reply-To: "Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>" <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>> Date: Friday, February 17, 2023 at 1:48 AM To: Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>>, "COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, GNSO-Chairs <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>> Subject: Re: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Hi Paul, Thank you for raising your hand for this, it is much appreciated. I think that in the past we would have taken this to the mailing list, but I must admit it is not my favorite medium: I tend to get quickly lost in the sub-threads (I am probably showing my age). The current thinking should lead us to a small team setup, but given the short timelines I wouldn’t want to waste any of it haggling over how to form it. Could I suggest that: 1. We initiate immediately a bespoke small team headed by Paul McGrady + eventually a single co-lead from the other house should anyone volunteer. 2. Membership to open to all Councillors. Should any Councillor need external input, he/she can seek it but remains the small team sole member. 3. Staff to create a bespoke Google Doc with the Board’s questions. 4. The small team takes it from there with the aim of gathering our thoughts by March 3rd. Council colleagues: Thoughts? Comments? Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1287335570] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>> Date: Thursday, 16 February 2023 at 4:32 pm To: Sebastien Ducos <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>>, COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, GNSO-Chairs <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>> Subject: RE: PLEASE READ - ICANN76 Stakeholders/Board sessions You don't often get email from paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>. Learn why this is important [aka.ms]<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;…> Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Thanks Seb! I think our questions to the Board proposed below look great and touch on important concerns. As for Tripti’s question, what will be our mechanism to respond? Should we (1) start a shared document that folks can contribute to, (2) do we want to run a short-lived small team to develop a draft for the broader Council to review (I’m happy to lead that effort if you like), (3) do we send ideas to the mailing list and have staff compile them and then we all edit the compilation, (4) something else? Also, we need to have milestone deadlines so that we aren’t scrambling and doing this on airplanes to Cancun. Thanks! Best, Paul From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Sebastien--- via council Sent: Thursday, February 16, 2023 9:01 AM To: COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] PLEASE READ - ICANN76 Stakeholders/Board sessions Dear Council Colleagues, A short note to correct my previous email: While the Board would like us to prepare our response to their question ahead of our meeting, the March 1st deadline if for us to submit our questions to them. Here are some questions already floated: * Ensuring Board and ICANN org input to PDP processes How do we minimize the need for an ODP and minimize its impact when it is needed? What further information or details should the GNSO integrate into a PDP Final Report to ensure it delivers Board-ready recommendations? * Getting to the next round of new gTLDs What in the Boards view would be required of the GNSO Council and Community to secure a Next Round Launch Date by the 2023 AGM? * WHOIS Disclosure System The Council’s recommendations were delivered 3 months ago which corresponds to ICANN Org’s ramp up requirement; has the development been initiated? What assistance can the Council and its small team offer to ensure initial timelines are met? Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3093328915] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Sebastien--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Date: Thursday, 16 February 2023 at 2:00 pm To: COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, GNSO-Chairs <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>> Subject: [council] FW: PLEASE READ - ICANN76 Stakeholders/Board sessions Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear Council Colleagues, Please find below a letter from Tripti Sinha on behalf of the Board regarding our session in Cancun. In particular the Board would like for us to respond to the following by March 1st: The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT). IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented. What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process? Please be as concrete as possible. Please note that as per our discussion with Becky today, I also expect we will receive a list of clarifying questions on the SubPro Recommendations themselves. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1469584128] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Gnso-chairs <gnso-chairs-bounces(a)icann.org<mailto:gnso-chairs-bounces@icann.org>> on behalf of Vinciane Koenigsfeld via Gnso-chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Date: Tuesday, 14 February 2023 at 7:23 pm To: gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org> <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Cc: becky.burr(a)board.icann.org<mailto:becky.burr@board.icann.org> <becky.burr(a)board.icann.org<mailto:becky.burr@board.icann.org>>, matthew.shears(a)board.icann.org<mailto:matthew.shears@board.icann.org> <matthew.shears(a)board.icann.org<mailto:matthew.shears@board.icann.org>> Subject: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors Dear Generic Names Supporting Organization Council Leaders, *Please reply no later than Wednesday 1 March 2023* The Board and I very much look forward to welcoming and meeting with you during ICANN76 in Cancún, between 11-16 March. It is with great pleasure and excitement that we are finally going to Mexicó, after having had to cancel the in-person component of both ICANN67 and ICANN70. We are grateful to our friends and stakeholders in Latin America for their patience and understanding in the process, and delighted to say ¡ Cancún aquí vamos! (Cancún, here we are!). The last three years have certainly proven eventful for all of us, but in unison with ICANN organization, we are more determined than ever to work closely with you to make 2023 and the many years after that, productive and successful. This time in particular, the Board proposes a slight change in the approach to our bilateral sessions. We understood that there was an appetite for questions more tailored to each stakeholder group’s needs. Therefore, we will not be sending the same question from the Board to all of you. Having said this, to maintain our commitment to transparency, all of the questions the Board to sends to each group will be published in the Community Digest. The second improvement that we are putting in place starting at ICANN76, is to provide you with a summary of what we heard from you during these bilateral sessions. This summary will be in two forms: 1. A blog highlighting key take aways from ICANN76 (and every ICANN meeting after that) 2. Summaries of bilateral sessions will be included in the Policy Outcomes Report we publish after each ICANN meeting These are only initial steps, and we will continue to discuss with you ways improve the way we interact moving forward. In the meantime, please find herewith the questions we would like to ask your Group ahead of our joint session in Cancún: The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT). IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented. What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process? Please be as concrete as possible. We look forward to hearing your thoughts on this soon. We would be grateful if you could send to Board Operations (board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>) the questions you would like the Board to address during our face-to-face meetings. Given the finite time available for these meetings, please list your questions in order of priority. We would also appreciate getting your questions no later than Wednesday 1 March, 2023. We thank you in advance for your time on this matter. Best regards, Tripti Sinha Chair, ICANN Board of Directors ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com__;!!PtGJab4!7131yaNn7gb0FUh…>

2 2

Re: [council] [gnso-secs] PLEASE READ - ICANN76 Stakeholders/Board sessions
by Nathalie Peregrine Feb. 17, 2023

Feb. 17, 2023

Hi Susan, Excellent catch! His email address was updated in the mailing list, but the settings adjusted incorrectly. Thank you so much for spotting this! All fixed now, and our apologies for the mishap! Kind regards, Natshalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Reply to: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy> Date: Friday, 17 February 2023 at 11:37 To: Susan Payne <susan.payne(a)comlaude.com>, Paul McGrady <paul(a)elstermcgrady.com>, "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [gnso-secs] PLEASE READ - ICANN76 Stakeholders/Board sessions Thank you Susan. Good catch. I have asked Nathalie to look into it. Paul is probably still in our mailing list under his Taft Law address. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2497806818] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Susan Payne <susan.payne(a)comlaude.com> Date: Friday, 17 February 2023 at 11:30 am To: Sebastien Ducos <Sebastien(a)registry.godaddy>, Paul McGrady <paul(a)elstermcgrady.com>, COUNCIL(a)GNSO.ICANN.ORG <council(a)gnso.icann.org>, GNSO-Chairs <gnso-chairs(a)icann.org>, gnso-secs(a)icann.org <gnso-secs(a)icann.org> Subject: RE: PLEASE READ - ICANN76 Stakeholders/Board sessions Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Hi all, I just wanted to flag that I didn’t receive the email from Paul that Seb is responding to, and it’s not in Junk. Is his new email address perhaps not yet permitted to post to the Council list? Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image002.png@01D942C4.F11AF800][nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> From: council <council-bounces(a)gnso.icann.org> On Behalf Of Sebastien--- via council Sent: Friday, February 17, 2023 9:48 AM To: Paul McGrady <paul(a)elstermcgrady.com>; COUNCIL(a)GNSO.ICANN.ORG; GNSO-Chairs <gnso-chairs(a)icann.org>; gnso-secs(a)icann.org Subject: Re: [council] PLEASE READ - ICANN76 Stakeholders/Board sessions Hi Paul, Thank you for raising your hand for this, it is much appreciated. I think that in the past we would have taken this to the mailing list, but I must admit it is not my favorite medium: I tend to get quickly lost in the sub-threads (I am probably showing my age). The current thinking should lead us to a small team setup, but given the short timelines I wouldn’t want to waste any of it haggling over how to form it. Could I suggest that: 1. We initiate immediately a bespoke small team headed by Paul McGrady + eventually a single co-lead from the other house should anyone volunteer. 2. Membership to open to all Councillors. Should any Councillor need external input, he/she can seek it but remains the small team sole member. 3. Staff to create a bespoke Google Doc with the Board’s questions. 4. The small team takes it from there with the aim of gathering our thoughts by March 3rd. Council colleagues: Thoughts? Comments? Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1287335570] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Paul McGrady <paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>> Date: Thursday, 16 February 2023 at 4:32 pm To: Sebastien Ducos <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>>, COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, GNSO-Chairs <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>> Subject: RE: PLEASE READ - ICANN76 Stakeholders/Board sessions You don't often get email from paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com>. Learn why this is important [aka.ms]<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;…> Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Thanks Seb! I think our questions to the Board proposed below look great and touch on important concerns. As for Tripti’s question, what will be our mechanism to respond? Should we (1) start a shared document that folks can contribute to, (2) do we want to run a short-lived small team to develop a draft for the broader Council to review (I’m happy to lead that effort if you like), (3) do we send ideas to the mailing list and have staff compile them and then we all edit the compilation, (4) something else? Also, we need to have milestone deadlines so that we aren’t scrambling and doing this on airplanes to Cancun. Thanks! Best, Paul From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Sebastien--- via council Sent: Thursday, February 16, 2023 9:01 AM To: COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] PLEASE READ - ICANN76 Stakeholders/Board sessions Dear Council Colleagues, A short note to correct my previous email: While the Board would like us to prepare our response to their question ahead of our meeting, the March 1st deadline if for us to submit our questions to them. Here are some questions already floated: * Ensuring Board and ICANN org input to PDP processes How do we minimize the need for an ODP and minimize its impact when it is needed? What further information or details should the GNSO integrate into a PDP Final Report to ensure it delivers Board-ready recommendations? * Getting to the next round of new gTLDs What in the Boards view would be required of the GNSO Council and Community to secure a Next Round Launch Date by the 2023 AGM? * WHOIS Disclosure System The Council’s recommendations were delivered 3 months ago which corresponds to ICANN Org’s ramp up requirement; has the development been initiated? What assistance can the Council and its small team offer to ensure initial timelines are met? Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3093328915] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Sebastien--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Date: Thursday, 16 February 2023 at 2:00 pm To: COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, GNSO-Chairs <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>> Subject: [council] FW: PLEASE READ - ICANN76 Stakeholders/Board sessions Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear Council Colleagues, Please find below a letter from Tripti Sinha on behalf of the Board regarding our session in Cancun. In particular the Board would like for us to respond to the following by March 1st: The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT). IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented. What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process? Please be as concrete as possible. Please note that as per our discussion with Becky today, I also expect we will receive a list of clarifying questions on the SubPro Recommendations themselves. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1469584128] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Gnso-chairs <gnso-chairs-bounces(a)icann.org<mailto:gnso-chairs-bounces@icann.org>> on behalf of Vinciane Koenigsfeld via Gnso-chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Date: Tuesday, 14 February 2023 at 7:23 pm To: gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org> <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Cc: becky.burr(a)board.icann.org<mailto:becky.burr@board.icann.org> <becky.burr(a)board.icann.org<mailto:becky.burr@board.icann.org>>, matthew.shears(a)board.icann.org<mailto:matthew.shears@board.icann.org> <matthew.shears(a)board.icann.org<mailto:matthew.shears@board.icann.org>> Subject: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors Dear Generic Names Supporting Organization Council Leaders, *Please reply no later than Wednesday 1 March 2023* The Board and I very much look forward to welcoming and meeting with you during ICANN76 in Cancún, between 11-16 March. It is with great pleasure and excitement that we are finally going to Mexicó, after having had to cancel the in-person component of both ICANN67 and ICANN70. We are grateful to our friends and stakeholders in Latin America for their patience and understanding in the process, and delighted to say ¡ Cancún aquí vamos! (Cancún, here we are!). The last three years have certainly proven eventful for all of us, but in unison with ICANN organization, we are more determined than ever to work closely with you to make 2023 and the many years after that, productive and successful. This time in particular, the Board proposes a slight change in the approach to our bilateral sessions. We understood that there was an appetite for questions more tailored to each stakeholder group’s needs. Therefore, we will not be sending the same question from the Board to all of you. Having said this, to maintain our commitment to transparency, all of the questions the Board to sends to each group will be published in the Community Digest. The second improvement that we are putting in place starting at ICANN76, is to provide you with a summary of what we heard from you during these bilateral sessions. This summary will be in two forms: 1. A blog highlighting key take aways from ICANN76 (and every ICANN meeting after that) 2. Summaries of bilateral sessions will be included in the Policy Outcomes Report we publish after each ICANN meeting These are only initial steps, and we will continue to discuss with you ways improve the way we interact moving forward. In the meantime, please find herewith the questions we would like to ask your Group ahead of our joint session in Cancún: The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT). IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented. What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process? Please be as concrete as possible. We look forward to hearing your thoughts on this soon. We would be grateful if you could send to Board Operations (board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>) the questions you would like the Board to address during our face-to-face meetings. Given the finite time available for these meetings, please list your questions in order of priority. We would also appreciate getting your questions no later than Wednesday 1 March, 2023. We thank you in advance for your time on this matter. Best regards, Tripti Sinha Chair, ICANN Board of Directors ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…>

1 0