February 2023 - council - lists.icann.org

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

FW: PLEASE READ - ICANN76 Stakeholders/Board sessions
by Sebastien＠registry.godaddy Feb. 17, 2023

Feb. 17, 2023

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> on behalf of Vinciane Koenigsfeld via Gnso-chairs <gnso-chairs(a)icann.org> Date: Tuesday, 14 February 2023 at 7:23 pm To: gnso-chairs(a)icann.org <gnso-chairs(a)icann.org> Cc: becky.burr(a)board.icann.org <becky.burr(a)board.icann.org>, matthew.shears(a)board.icann.org <matthew.shears(a)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

4 6

ICANN76 First Ever GNSO Town Hall meeting | Sunday 12 March from 16:30 - 17:30 local time
by Nathalie Peregrine Feb. 16, 2023

Feb. 16, 2023

Dear councilors, Please find below the message circulated to your Stakeholder Group and Constituency Chairs. Thank you, Nathalie _____________________________________________________________________________________________________________________ Dear Stakeholder Group and Constituency Chairs, To encourage GNSO community engagement with the GNSO Council, we would like to invite you to attend the first ever GNSO Town Hall meeting which is planned for Sunday 12 March from 16.30 – 17.30 local time. The Council has been considering how to facilitate engagement and collaboration with the GNSO community which has resulted in this first ever GNSO Town Hall meeting. The objective is to have an open and frank discussion with the GNSO Community during which any topics or questions can be raised. One particular topic that the Council would like to draw your attention to is the recent Council Strategic Planning session and the strategic priorities that came out of that meeting (see meeting report<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/gnso-…>): * Develop and implement improvements that ensure that policy recommendations are “Board ready” when these are considered for adoption by the GNSO Council. · Ensure timely input into the Board’s consideration of the SubPro ODP and related policy recommendations, as well as keeping a close eye on dependencies that are within the Council’s remit to address with the aim of getting the Board into a position to be able to agree and announce a next round date before the end of this Council session / year. · Engage in further conversations with the ICANN Board as well as the GNSO community concerning how ODP type input and assessment can be developed prior to GNSO Council consideration of policy recommendations. · Consider how to create further transparency in small team deliberations. · Consider how to ensure enhanced uptake and use of the techniques of the Consensus Playbook with a specific focus on scoping and chartering, learning from approaches applied in efforts such as the facilitated dialogue on Closed Generics. · Exploring incentives for compromising and promoting opportunities for mutual gain. The Council would welcome your ideas/suggestions for how to ensure that the Council is able to meet these strategic priorities. The Council also welcomes your feedback after this session on whether this is a welcome approach to encourage such engagement or whether alternative paths should be explored. If you would like to submit any topics or questions in advance of the meeting, please submit these to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> with “GNSO Town Hall” as the subject. We look forward to welcoming you on Sunday 12 March! Kind regards, Nathalie

1 0

FW: [Ext] ICANN Publishes FY23 Q2 Unaudited Financial Results
by Julie Bisland Feb. 16, 2023

Feb. 16, 2023

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, February 16, 2023 at 10:02 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] ICANN Publishes FY23 Q2 Unaudited Financial Results [https://r20.rs6.net/on.jsp?ca=20f802ac-0d17-494c-b63b-9b709b59c404&a=112202…] Thursday, 16 February 2023 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=00194JTsWw9AiMRI-im…> Table of Contents ICANN76 Resources · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Information Sharing · NEW: ICANN Publishes FY23 Q2 Unaudited Financial Results · NEW: ICANN Enacts Relief for Registrants Affected by Republic of Türkiye and Syrian Arab Republic Earthquakes · REMINDER: Join the Webinar and Apply for the NextGen@ICANN Program at ICANN77 · 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=00194JTsWw9AiMRI-im…> Prep Week Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> Zoom Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> Health & Safety [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> REMINDER: 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=00194JTsWw9AiMRI-im…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> Information Sharing NEW: ICANN Publishes FY23 Q2 Unaudited Financial Results ICANN and Public Technical Identifiers (PTI) published their unaudited financial results for the second quarter of fiscal year 2023 (FY23). Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> NEW: ICANN Enacts Relief for Registrants Affected by Republic of Türkiye and Syrian Arab Republic Earthquakes ICANN accredited registrars will be permitted to temporarily forbear from canceling domain registrations that are unable to be renewed by registrants. We encourage registrars and registries to support this action when reviewing domain name renewal delinquencies in the affected areas. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> REMINDER: 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=00194JTsWw9AiMRI-im…> for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…>. Submit your nominations. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…> 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=00194JTsWw9AiMRI-im…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…>. Volume 5, Issue 13 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…> | Next Issue: Monday, 20 February 2023 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=00194JTsWw9AiMRI-im…>

1 0

Recordings | GNSO Council meeting | Thursday, 16 February 2023
by Nathalie Peregrine Feb. 16, 2023

Feb. 16, 2023

Dear all, Please find below the audio recording and zoom recording (audio, visual, rough transcript, and chat) of the GNSO Council meeting held on Thursday, 16 February 2023 at 05:00 UTC. Audio only: https://icann.zoom.us/rec/play/9FqNiOLdWrcqwt2abkDUjUSCKi7odOyjMIDLAmUaV8OR… [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/9FqNiOLdWrcqwt2ab…> Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/play/jFVDUvt7kAtrlUIfUUpQcr6afJWzU-Itc4lxwQx1fzmx… [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/jFVDUvt7kAtrlUIfU…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Thank you. With kind regards, Nathalie

1 0

GNSO Council resolutions 16 February 2023
by Terri Agnew Feb. 16, 2023

Feb. 16, 2023

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 16 February 2023, which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. CONSENT AGENDA Nomination of a Member of the Fellowship Selection Committee Submitted by: Greg DiBiase Seconded by: John McElwaine Whereas, 1. On 11 November 2022, the ICANN Fellowship Program invited<https://community.icann.org/download/attachments/105383387/digest_2022_11No…> the GNSO to nominate one individual to serve as member of the Fellowship Selection Committee<https://www.icann.org/resources/pages/fellowship-selection-committee> for six consecutive ICANN meetings beginning with ICANN78. 2. On 9 December 2022, the GNSO launched<https://gnso.icann.org/en/announcements/announcement-09dec22-en.htm> an Expression of Interest (EOI) process to solicit volunteers for the GNSO-nominated position. 3. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing applications and recommending one individual for the GNSO to nominate. 4. The SSC reviewed the applications received, taking into account the criteria outlined in the EOI announcement. 5. The SSC submitted its full consensus recommendation to the GNSO Council on 06 February 2023, by way of submission of the relevant motion. 6. The GNSO Council considered the recommendations of the SSC. Resolved, 1. The GNSO nominates Taiwo Peter Akinremi to serve as a Fellowship Selection Committee member for six consecutive ICANN meetings, beginning with ICANN78. 2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to staff supporting the ICANN Fellowship Program. 3. The GNSO Council instructs the GNSO Secretariat to inform the nominated candidate that he has been selected. 4. The GNSO Council requests the GNSO Secretariat to send 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. Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-cou…> CONSENT AGENDA Adoption of the Revised Charter for the Budget and Operations Townhall Submitted by: Greg DiBiase Seconded by: John McElwaine Whereas, 1. In 2017 the GNSO Council expressed its desire to establish the GNSO Standing Committee on Budget and Operations (SCBO) to assist with the development of GNSO Council comments that relate to ICANN's Budgetary and Finance matters; 2. On 21 December 2017, the GNSO Council adopted the formation of the SCBO and its interim charter; 3. In FY18, the SCBO developed four public comments (IANA-PTI FY19 Budget, ICANN's Reserve Fund Target Level, ICANN's Draft FY19 Budget and Operating Plan, and ICANN Reserve Fund: Proposed Replenishment Strategy) on behalf of the GNSO Council that were later accepted and posted to ICANN's public forum; 4. On 24 October 2018, the GNSO Council voted to adopt the charter for the GNSO Standing Committee on Budget and Operations (SCBO) on a permanent basis; 5. On an annual basis, the SCBO developed and provided drafts public comment to the GNSO Council on the IANA-PTI Budget and ICANN’s Draft Budget and Operating Plan, which upon non-objection from the Council, were submitted to the relevant public comment proceeding; 6. Interest and engagement in the SCBO has waned and the substance of public comments has diminished; 7. The GNSO Council identified an opportunity to evolve the SCBO to better align with the needs of the Council as well as establish a consistent platform for the Stakeholder Groups and Constituencies to engage with the Finance and Planning team in a more streamlined and collaborative manner; and, 8. The GNSO Council leadership team coordinated with the GNSO Council and Stakeholder Group and Constituency leadership teams to ensure that they are supportive of the change to the SCBO. Resolved, 1. The GNSO Council adopts the revised Charter<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-scbo-cha…> for the Budget and Operations Townhall (formerly known as the SCBO). 2. The GNSO Council thanks the Council members and subject matter experts that have contributed to the SCBO throughout its lifespan. Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-cou…> 20230216-2 Motion - Approval of a Project Change Request (PCR) to Update the Project Plan of the Transfer Policy Review (TPR) Policy Development Process (PDP) Submitted by: Osvaldo Novoa Seconded by: Greg Dibiase Whereas, 1. On 18 February 2021, the GNSO Council voted<https://gnso.icann.org/en/council/resolutions/2020-current#202102> to initiate a PDP to review the Transfer Policy. 2. On 24 March 2021, the GNSO Council approved<https://gnso.icann.org/en/council/resolutions/2020-current#20210324-3> the PDP working group’s charter, which anticipated a two-phase approach to completing the PDP’s work. 3. The working group began meeting in May 2021 and has made substantial progress, including publication of an Initial Report on Phase 1(a) topics, review of public comments on the Phase 1(a) Initial Report, and preliminary deliberations on Phase 1(b) topics. 4. In the course of considering the Phase 1 charter questions, the working group identified dependencies between charter topics that require the working group to make progress on certain Phase 2 topics (Transfer Emergency Action Contact (TEAC), reversal of a transfer, and Transfer Dispute Resolution Policy (TDRP)) before Phase 1 deliberations on inter-registrar and inter-registrant transfers can be completed. 5. The working group has determined that the best path forward is to consolidate its work into a single phase, which will allow the working group to consider all topics in the charter iteratively. This approach will result in delivery of a second Initial Report covering all topics in the charter and a single Final Report. 6. The working group anticipates that with this new approach, the PDP will conclude a year earlier than originally anticipated, because there will be fewer discrete deliverables and public comment periods. 7. The Working Group leadership team submitted a Project Change Request outlining the full rationale for updating the project plan. Resolved, 1. The GNSO Council approves this Project Change Request. 2. The GNSO Council instructs policy support staff to update the TPR project plan, charter, and other materials accordingly and post on the working group wiki. Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-cou…> Thank you. Kind regards, Terri

1 0

**Starting in 15 minute | Meeting Invitation | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC
by Terri Agnew Feb. 16, 2023

Feb. 16, 2023

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday 16 February 2023 at 05:00 UTC for 2 hours. 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/nAjVD Check your time zone: https://tinyurl.com/2mx8bt8t <https://urldefense.com/v3/__https:/tinyurl.com/2mx8bt8t__;!!PtGJab4!5RvZYMI…> 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> Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/97891627902?pwd=RURCTiti…> Passcode: 5d$X0$^0L2 If joining Zoom via Zoom App the following will be required: Webinar ID: 978 9162 7902 Passcode: 9844091488 One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# If you are joining via audio only: Dial(for higher quality, dial a number based on your current location): US: +1 312 626 6799 or +1 301 715 8592 or +1 929 436 2866 or +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or 877 853 5247 (Toll Free) or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) International numbers available: https://icann.zoom.us/u/abaexQvkCI <https://urldefense.com/v3/__https:/icann.zoom.us/u/abaexQvkCI__;!!PtGJab4!4…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/2QGjDQ> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

ICANN76 prep week scheduled is now published / How to Create your Prep Week Schedule
by Julie Bisland Feb. 15, 2023

Feb. 15, 2023

Dear all, The ICANN76 prep week scheduled is now published! Please take a moment to read the information below to help create your prep week schedule and add sessions to your calendar. For the prep week schedule, go here: https://icann76.sched.com/ [icann76.sched.com]<https://urldefense.com/v3/__https:/icann76.sched.com/__;!!PtGJab4!-WtbJjGY_…> * Click Sign up and enter your information (email address and create password) * Once you “Join Event”, 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” (see screen shot below) or just click to add the checkmark. [cid:image001.png@01D94150.CD7498E0] * 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. [cid:image002.png@01D94150.CD7498E0] Or [cid:image003.png@01D94150.CD7498E0] * Click the Phone icon [cid:image004.png@01D94150.CD7498E0] * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. [cid:image005.png@01D94150.CD7498E0] [cid:image006.png@01D94150.CD7498E0] The ICANN76 Schedule<https://76.schedule.icann.org/> will be posted 17 February 2023.Please email questions to us at: gnso-secs(a)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

RV: Motion to approve the Project Change Request to update the project plan of the Transfer Policy Review PDP
by Novoa, Osvaldo Feb. 15, 2023

Feb. 15, 2023

Dear Councilors, Attached please find a Motion to approve the Project Change Request to update the project plan of the Transfer Policy Review PDP, and the associated Project Change Request. Since the PDP was initially chartered in two phases, as a consequence of this PCR, the charter requires minor revisions to remove references to phases. Attached is also included the revised charter. Best Regards, Osvaldo Novoa ________________________________ El presente correo y cualquier posible archivo adjunto est? dirigido ?nicamente al destinatario del mensaje y contiene informaci?n que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Est? prohibida cualquier utilizaci?n, difusi?n o copia de este e-mail por cualquier persona o entidad que no sean las espec?ficas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicaci?n que haya sido emitida incumpliendo nuestra Pol?tica de Seguridad de la Informaci?n This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

5 4

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC
by Devan Reed Feb. 15, 2023

Feb. 15, 2023

Dear all, The GNSO Council meeting is scheduled on Thursday 16 February 2023 at 05:00 UTC for 2 hours. 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/nAjVD Check your time zone: https://tinyurl.com/2mx8bt8t <https://urldefense.com/v3/__https:/tinyurl.com/2mx8bt8t__;!!PtGJab4!5RvZYMI…> 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> Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/97891627902?pwd=RURCTiti…> Passcode: 5d$X0$^0L2 If joining Zoom via Zoom App the following will be required: Webinar ID: 978 9162 7902 Passcode: 9844091488 One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# If you are joining via audio only: Dial(for higher quality, dial a number based on your current location): US: +1 312 626 6799 or +1 301 715 8592 or +1 929 436 2866 or +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or 877 853 5247 (Toll Free) or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) International numbers available: https://icann.zoom.us/u/abaexQvkCI <https://urldefense.com/v3/__https:/icann.zoom.us/u/abaexQvkCI__;!!PtGJab4!4…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/2QGjDQ> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

Please read: Upcoming GNSO Council meeting prep 16 February 2023 at 05:00 UTC
by Nathalie Peregrine Feb. 14, 2023

Feb. 14, 2023

Dear all, A few reminders of prep for the Council meeting 16 February at 05:00 UTC: 1. Please email the GNSO Council mailing list if you would like to second one or several motions. Please see the motion wiki page<https://community.icann.org/display/gnsocouncilmeetings/Motions+2023-02-16>. 1. Please review the GNSO Council meeting Cheat Sheet <https://urldefense.com/v3/__https:/docs.google.com/document/d/1lQ9fqEjD-inZ…> in order to help you prepare for the session and also provide your input in suggestion mode. It is also attached to this email for your convenience. 1. All documents mentioned on the Council agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> will be listed on the Document wiki page<https://community.icann.org/display/gnsocouncilmeetings/Documents+2023-02-16> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/download/attachments/150178775/GNSO_Council_Pro…> and the Project List<https://community.icann.org/download/attachments/150178773/GNSO_Council_Pro…> which have been updated for this month’s Council meeting. 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. Thank you! Kind regards, Nathalie

1 0

FW: [Ext] CLOSES TODAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget
by Julie Bisland Feb. 13, 2023

Feb. 13, 2023

FYI-- From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, February 13, 2023 at 10:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] CLOSES TODAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget [https://r20.rs6.net/on.jsp?ca=f0d16007-abbf-4b39-b7d8-2d1851275adf&a=112202…] Monday, 13 February 2023 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=001M_rt90AWZMMb9SBF…> Table of Contents ICANN76 Resources · REMINDER: ICANN76 SO/AC Zoom Backgrounds · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program · REMINDER: Register for the ICANN76 Community Forum in Cancún, Mexico Information Sharing · NEW Chair’s Blog: Recap of the January Board Workshop · NEW: Changes to ICANN Org’s Meetings Scheduling Platform · REMINDER ICANN Request for Information: gTLD Application Life Cycle System · REMINDER: Watch the Recording of the Draft ICANN FY24 Plans Informational Webinar · REMINDER: Join the Webinar and Apply for the NextGen@ICANN Program at ICANN77 · 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 · CLOSES TODAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget · Proposed Procedure for Selecting a Top-Level Domain String for Private Use · Additional Script-Based Reference Label Generation Rules and Related Updates ICANN76 Resources REMINDER: ICANN76 SO/AC Zoom Backgrounds ICANN76 Community Forum SO/AC Zoom Backgrounds here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…>. REMINDER: 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=001M_rt90AWZMMb9SBF…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> REMINDER: Register for the ICANN76 Community Forum in Cancún, Mexico Registration closes for in-person attendance closes on 8 March 2023. Registration for virtual participation will remain open through 16 March 2023. Registration link. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> The full schedule for ICANN76 will be published on 17 February 2023. Prep Week will be held 27 February 2023 to 01 March 2023. Information Sharing NEW Chair’s Blog: Recap of the January Board Workshop The ICANN Board of Directors recently held its first Board Workshop of the year, and I'm pleased to report that we began 2023 on a productive note. During the four-day meeting, held in Los Angeles, we discussed and made progress on many of the most important issues that ICANN is currently facing, including the effectiveness of ICANN's multistakeholder model of governance and the next round of new generic top-level domains (gTLDs). Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> NEW: Changes to ICANN org’s Meetings Scheduling Platform As the ICANN76 Community Forum approaches, I wanted to share an update with you about the ICANN organization's (org) online scheduling tool. Because the vendor is discontinuing support for Pathable, we will no longer be using this tool. Instead, we will be using Sched. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> REMINDER ICANN Request for Information: gTLD Application Life Cycle System Internet Corporation for Assigned Names and Numbers (ICANN) organization issued a request for information (RFI) seeking to evaluate vendors interested in supporting the implementation of a new enterprise system to aid ICANN staff in the collection and processing of applications for new generic top-level domains (gTLDs). Participants submit any questions via Portal (Q&A Board) by13 February 2023 by 23:59 UTC Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> REMINDER: Watch the Recording of the Draft ICANN FY24 Plans Informational Webinar The Internet Corporation for Assigned Names and Numbers (ICANN) posted the Draft FY24-28 Operating and Financial Plan, and Draft FY24 Operating Plan and Budget for public comment on December 14, 2022. See link [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…>. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> And this proceeding closes on 13 February 2023. ICANN org hosted two informational webinars about the Draft FY24 Plans, both webinars presented identical information, please watch [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…>the recording [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> to learn more about these Plans. REMINDER: 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=001M_rt90AWZMMb9SBF…> for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…>. Submit your nominations. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> Public Comment CLOSES TODAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> Open for submissions date: 14 December 2022 Closed for submissions date: 13 February 2023 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=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…> 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=001M_rt90AWZMMb9SBF…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…>. Volume 5, Issue 12 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…> | Next Issue: Thursday, 16 February 2023 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001M_rt90AWZMMb9SBF…>

1 0

Fwd: Hal Lubsen Memoriam
by Nacho Amadoz Feb. 10, 2023

Feb. 10, 2023

Good morning, Following Ram’s request, I am sharing this sad news with the Council. Nacho > Inici del missatge reenviat: > > De: Ram Mohan <rmohan(a)afilias.info> > Tema: Rv: Hal Lubsen Memoriam > Data: 9 de febrer de 2023, 23:02:40 CET > Per a: RySG membership <members(a)rysg.info> > > Dear Registry Stakeholder group colleagues, > > The family just released the following Memoriam for Hal Lubsen. > > Could you kindly forward this to the GNSO Council and other relevant groups as well. > > Thank you, > Ram > > Web: > https://circleid.com/posts/20230209-hal-lubsen-industry-leader-and-former-c… > Twitter: > https://twitter.com/CircleID/status/1623793121191682052 > <https://twitter.com/CircleID/status/1623793121191682052> > > -- > To unsubscribe from this group and stop receiving emails from it, send an email to members+unsubscribe(a)rysg.info <mailto:members+unsubscribe@rysg.info>.

1 0

FW: [Ext] CLOSES MONDAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget
by Devan Reed Feb. 9, 2023

Feb. 9, 2023

FYI: From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, February 9, 2023 at 10:14 AM To: Devan Reed <devan.reed(a)icann.org> Subject: [Ext] CLOSES MONDAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget [https://r20.rs6.net/on.jsp?ca=f5124f31-4118-4782-abcc-ef17cdc06ab0&a=112202…] Thursday, 09 February 2023 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=001TDHuQ_32BFOMXFSz…> Table of Contents ICANN76 Resources · REMINDER: ICANN76 SO/AC Zoom Backgrounds · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program · REMINDER: Register for the ICANN76 Community Forum in Cancún, Mexico Information Sharing · NEW: Join the Webinar and Apply for the NextGen@ICANN Program at ICANN77 · REMINDER: ICANN Request for Quotation: Storage Network Replacement 2023 · REMINDER: ICANN Request for Proposal: Software Engineering Staff Augmentation · REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members · REMINDER: Watch the Recording of the Draft ICANN FY24 Plans Informational Webinar · 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 · CLOSES MONDAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget · Proposed Procedure for Selecting a Top-Level Domain String for Private Use · Additional Script-Based Reference Label Generation Rules and Related Updates ICANN76 Resources REMINDER: ICANN76 SO/AC Zoom Backgrounds ICANN76 Community Forum SO/AC Zoom Backgrounds here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…>. REMINDER: 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 process opens Monday, 30 January 2023. 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=001TDHuQ_32BFOMXFSz…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> REMINDER: Register for the ICANN76 Community Forum in Cancún, Mexico Registration for in-person attendance closes on 8 March 2023. Registration for virtual participation will remain open through 16 March 2023. The full schedule for ICANN76 will be published on 17 February 2023. Prep Week will be held 27 February 2023 - 01 March 2023 The Prep Week schedule will be published on 13 February 2023. ICANN76 Health and Safety Protocols [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> Registration link. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> Information Sharing NEW: 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=001TDHuQ_32BFOMXFSz…> for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> 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=001TDHuQ_32BFOMXFSz…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> REMINDER: ICANN Request for Quotation: Storage Network Replacement 2023 ICANN organization issued a request for quotation (RFQ) to identify one or more providers to facilitate the sourcing and pre-configuration of predetermined storage area network equipment for our data centers. For a complete overview of this RFQ, including the timeline, please click here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> REMINDER: Watch the Recording of the Draft ICANN FY24 Plans Informational Webinar The Internet Corporation for Assigned Names and Numbers (ICANN) posted the Draft FY24-28 Operating and Financial Plan, and Draft FY24 Operating Plan and Budget for public comment on December 14, 2022. See link [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…>. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> And this proceeding closes on 13 February 2023. ICANN org hosted two informational webinars about the Draft FY24 Plans, both webinars presented identical information, please watch [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…>the recording [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> to learn more about these Plans. 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=001TDHuQ_32BFOMXFSz…> 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=001TDHuQ_32BFOMXFSz…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> 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=001TDHuQ_32BFOMXFSz…> 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=001TDHuQ_32BFOMXFSz…> 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=001TDHuQ_32BFOMXFSz…>. Submit your nominations. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> Public Comment CLOSES MONDAY: Draft FY24–28 Operating & Financial Plan and Draft FY24 Operating Plan & Budget [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> Open for submissions date: 14 December 2022 Closed for submissions date: 13 February 2023 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=001TDHuQ_32BFOMXFSz…> 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=001TDHuQ_32BFOMXFSz…> 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=001TDHuQ_32BFOMXFSz…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…>. Volume 5, Issue 11 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…> | Next Issue: Monday, 13 February 2023 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001TDHuQ_32BFOMXFSz…>

1 0

Re: [council] Consent Agenda for February meeting
by Terri Agnew Feb. 6, 2023

Feb. 6, 2023

Hi Greg, We acknowledge receipt and confirm this has now been added to the motions wiki page.<https://community.icann.org/x/zQOBDQ> Thank you. Kind regards, Terri From: council <council-bounces(a)gnso.icann.org> on behalf of "DiBiase, Gregory via council" <council(a)gnso.icann.org> Reply-To: "DiBiase, Gregory" <dibiase(a)amazon.com> Date: Monday, February 6, 2023 at 4:21 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Consent Agenda for February meeting Hi All, Please see the attached consent agenda for the February GNSO meeting. Please let me know if you have any questions. Thanks, Greg

1 0

Consent Agenda for February meeting
by DiBiase, Gregory Feb. 6, 2023

Feb. 6, 2023

Hi All, Please see the attached consent agenda for the February GNSO meeting. Please let me know if you have any questions. Thanks, Greg

1 0

Meeting Invitation | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC
by Terri Agnew Feb. 6, 2023

Feb. 6, 2023

Dear all, The GNSO Council meeting is scheduled on Thursday 16 February 2023 at 05:00 UTC for 2 hours. 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/nAjVD Check your time zone: https://tinyurl.com/2mx8bt8t 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> Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97891627902?pwd=RURCTiti…> Passcode: 5d$X0$^0L2 If joining Zoom via Zoom App the following will be required: Webinar ID: 978 9162 7902 Passcode: 9844091488 One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# If you are joining via audio only: Dial(for higher quality, dial a number based on your current location): US: +1 312 626 6799 or +1 301 715 8592 or +1 929 436 2866 or +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or 877 853 5247 (Toll Free) or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) International numbers available: https://icann.zoom.us/u/abaexQvkCI [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/abaexQvkCI__;!!PtGJab4!4…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/2QGjDQ> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

Proposed Agenda | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC
by Terri Agnew Feb. 6, 2023

Feb. 6, 2023

Dear all, Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/zwOBDQ. This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 16 February 2023 at 05:00 UTC: https://tinyurl.com/2mx8bt8t. (Wednesday) 21:00 Los Angeles; (Thursday) 00:00 Washington DC; 05:00 London; 06:00 Paris; 08:00 Moscow; 16:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (10 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso…> of the GNSO Council meeting on 15 December 2022 were posted on 03 January 2023. Minutes<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso…> of the GNSO Council meeting on 19 January 2023 were posted on 02 February 2023. Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Nomination of a Mentor for the ICANN Fellowship Selection Committee - Taiwo Peter Akinremi * Motion<https://community.icann.org/x/zQOBDQ> for the Adoption of the Revised Charter<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-scbo-cha…> for the Budget and Operations Townhall Item 4: COUNCIL VOTE - Adoption of the Amended Charter for the Transfer Policy Review PDP and Approval of the Policy Change Request (20 Minutes) The Council initiated the two-phased Transfer Policy Review PDP in February 2021. Since it began meeting in May 2021, the WG has made steady progress on its Phase 1 charter questions, including publishing its Phase 1A Initial Report<https://www.icann.org/en/public-comment/proceeding/initial-report-on-the-tr…> for public comment. The WG conducted preliminary deliberations on Phase 1B topics during the Phase 1A Initial Report public comment period, then reviewed public comments on the Phase 1A Initial Report, and is now completing revisions to preliminary recommendations, taking into account public comment received. In the course of Phase 1 work conducted to date, the WG discovered that certain Phase 2 topics must be addressed before Phase 1 recommendations can be fully developed. As a result, the leadership team prepared a Policy Change Request (PCR<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/carne…>) to update its work plan to consolidate all work into a single phase and change the order in which topics are considered. This will impact the timeline for key deliverables. In order to ensure that Council fully understood the potential changes prior to being asked to accept the Project Change Request (PCR), the changes and potential implications were shared with the Council and reviewed during the January meeting. Because the PDP was initially chartered in two phases, as a consequence of the PCR, the charter requires minor revisions to remove references to phases. Here, the Council will approve the amended Charter <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/novoa…> and approve the PCR for the Transfer Policy Review PDP. 4.1 – Presentation of motion - (Osvaldo Novoa, GNSO Council Liaison, Transfer Policy Review PDP) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A: GNSO Policy Development Process of the ICANN Bylaws. Item 5: 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 (20 minutes) The GNSO Council resolved<https://gnso.icann.org/en/council/resolutions/2020-current#202106> on 16 June 2021 to initiate the Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI) as a pilot, which included the review of the Working Group Self-Assessment as one of the two areas of focus. The CCOICI started the Working Group Self-Assessment assignment in October 2021 and concluded its work on this assignment in February 2022. However, the CCOICI deferred conducting the public comment until it could be combined with recommendations related to the GNSO Statement of Interest (SOI). The consolidated public comment proceeding<https://www.icann.org/en/public-comment/proceeding/updates-to-the-gnso-stat…> on Proposed Updates to the GNSO Operating Procedures was initiated on 09 September 2022 and closed on 14 November 2022. The CCOICI integrated public comments as appropriate and submitted its Recommendations Report to the Council on 5 January 2023. Here, the Council will receive an update on both the CCOICI’s Working Group Self-Assessment Recommendations Report. In addition, an update will be provided on the work of the the GNSO SOI Task Force (TF). 5.1 – Introduction of topic (Manju Chen, Chair of the CCOICI) 5.2 – Council discussion 5.3 - Next steps Item 6: COUNCIL DISCUSSION - ICANN76 Meeting Planning (15 minutes) The ICANN76 Community Forum is scheduled from 11-16 March 2023. With the meeting quickly approaching, the GNSO Council has a number of sessions that require advance planning. The Draft ICANN76 Schedule<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-gnso-ica…> was shared on 20 January 2023 and the various GNSO Council related sessions were briefly discussed. Those sessions include: * PDP/EPDP meetings on Saturday. * The GNSO working sessions (3) are scheduled for Sunday. * The joint meeting with the ccNSO on Monday. * The joint meeting with the ICANN Board on Tuesday. * The public Council meeting on Wednesday. * The GNSO Council wrap-up on Thursday. Here, the Council will discuss and prepare for the various Council-related sessions scheduled during ICANN76. 6.1 – Introduction of topic (Council leadership) 6.2 – Council discussion 6.3 - Next steps Item 7: COUNCIL DISCUSSION - PDP Improvements item #8 (Review of the Policy & Implementation recommendations) (15 minutes) The GNSO Council established a PDP Improvements Tracker<https://community.icann.org/display/GNSOPDPIT> in order to provide an aggregated view of the various proposed improvements that have been identified from a number of different initiatives., which include: * Council Strategic Planning Session (SPS) Action Item – how to improve support for and follow up on policy recommendations post-Council adoption * Operational Design Phase * Modifying Consensus Policies * PDP 3.0 Parking Lot Items * Review of Policy & Implementation Recommendations For item #8 (Review of the Policy & Implementation recommendations) and the agreed next step (“Staff support team to provide further detail on what a policy status report (PSR) would be expected to cover”), staff circulated a background note on a possible PSR on the Policy & Implementation Recommendations<https://mm.icann.org/pipermail/council/2023-January/026461.html> on 20 January 2023. Here, the Council will discuss the background note and consider next steps. 7.1 – Introduction of topic (Council leadership) 7.2 – Council discussion 7.3 - Next steps Item 8: COUNCIL DISCUSSION - Uniform Domain Name Dispute Resolution Policy (UDRP) Review Next Steps (15 minutes) After the approval of the Phase 1 Final Report of the GNSO Policy Development Process (PDP) on the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs in January 2021, the Council discussed the need to review the RPMs charter in advance of launching Phase 2 of the PDP. The Council determined that a Policy Status Report (PSR) should be requested from ICANN org, in order to better understand if new issues or information has emerged that would be relevant to a comprehensive review of the policy. ICANN org’s Global Domains and Strategy (GDS) team completed the draft PSR and published it for public comment on 3 March 2022; the revised PSR<https://gnso.icann.org/sites/default/files/file/field-file-attach/udrp-stat…> was shared with the Council on 18 July 2022 and the Council then received a briefing from GDS during the July meeting. During this meeting and subsequent meetings, there seemed to be support from the Council to delay next steps based on a number of reasons, primarily though because of the amount of competing work. The Council agreed during its November meeting that because of the launch of the Phase 1 RPMs Implementation Review Team (IRT), which would likely have overlapping community support with a Phase 2 PDP, that the delay for next steps should be tied to the completion or key milestones for the IRT Here, the Council will receive an update from the Council’s liaison to the RPMs IRT to better understand precise timing for delaying Phase 2 next steps. 8.1 – Introduction of topic (John McElwaine, GNSO Council liaison to the Rights Protection Mechanisms IRT) 8.2 – Council discussion 8.3 - Next steps Item 9: ANY OTHER BUSINESS (5 minutes) 9.1 - Standing Selection Committee (SSC) process feedback 9.2 - Update on Closed Generics Facilitated Dialogue _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 05:00 UTC Local time between November and March in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 (Wednesday) 21:00 San José, Costa Rica (CST) UTC-6 (Wednesday) 23:00 New York/Washington DC, USA (EST) UTC-5 (Thursday) 00:00 Buenos Aires, Argentina (ART) UTC-3 02:00 Rio de Janeiro, Brazil (BRT) UTC-3 02:00 London, United Kingdom (GMT) UTC+0 05:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:00 Paris, France (CET) UTC+1 06:00 Moscow, Russia (MSK) UTC+3 08:00 Singapore (SGT) UTC+8 13:00 Melbourne, Australia (AEDT) UTC+11 16:00 ---------------------------------------------------------------------------- DST starts on Sunday 26 March 2023, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 12 March 2023 for the U.S. DST ends on Sunday 29 October 2023 for EU countries, and on Sunday 05 November 2023 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/2mx8bt8t.

1 0

GNSO Council Portfolio Management Tool Suite - 16 February 2023 Meeting
by Berry Cobb Feb. 6, 2023

Feb. 6, 2023

Dear all, Please see links below to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 16 February 2023. Agenda: * https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen… Links to the Program Suite: * Program/Project Management Framework (PPMF): https://community.icann.org/x/0YvzC * Portfolio Management Tool (PMT): https://community.icann.org/x/04vzC * **Action/Decision Radar (ADR): https://community.icann.org/x/14vzC * **Project List (PL): https://community.icann.org/x/1YvzC * **Action Items (AIs): https://community.icann.org/x/RgZlAg * Council Small Teams (CSTs): https://community.icann.org/display/gnsocouncilmeetings/2022-2023+GNSO+Coun… * ** denotes the required three work products for review by Councilors in preparation for monthly meetings Key Program Suite Structural Changes for this Period: * None for this period. Key Project Changes or Milestones for this Period: * TPR_P1 – Transfer WG Project Change Request. * GNSO_BOT – Council to consider revised charter. * RPM_P2 – Next steps on Review of UDRP * Update on SOI Task Force. * Project Packages: * EPDP_IDN: https://community.icann.org/x/cYbOCg * TPR_P1: https://community.icann.org/x/MQDQCQ * SubPro_GGP: https://community.icann.org/x/EQOBDQ Key Project Activities for March 2023: * Expiration PSR – Council to consider small team’s output. * SubPro – Council to consider the Operational Design Assessment report delivered to the ICANN Board. Please let staff know if you have any questions. Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) berry.cobb(a)icann.org

1 0

REMINDER | Document and Motion deadline | Monday 06 February 2023 at 23:59 UTC for GNSO Council Meeting 16 February 2023 at 05:00 UTC
by Terri Agnew Feb. 6, 2023

Feb. 6, 2023

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 06 February 2023 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 16 February 2023 at 05:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/zQOBDQ Thank you. Nathalie

1 0

Re: [council] RV: Motion to approve the Project Change Request to update the project plan of the Transfer Policy Review PDP
by Terri Agnew Feb. 6, 2023

Feb. 6, 2023

Hello, We confirm receipt and the motion is now posted on the motions wiki page<https://community.icann.org/x/zQOBDQ>. Thank you. Kind regards, Terri From: council <council-bounces(a)gnso.icann.org> on behalf of "Novoa, Osvaldo via council" <council(a)gnso.icann.org> Reply-To: "Novoa, Osvaldo" <onovoa(a)Antel.com.uy> Date: Monday, February 6, 2023 at 11:46 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] RV: Motion to approve the Project Change Request to update the project plan of the Transfer Policy Review PDP Dear Councilors, Attached please find a Motion to approve the Project Change Request to update the project plan of the Transfer Policy Review PDP, and the associated Project Change Request. Since the PDP was initially chartered in two phases, as a consequence of this PCR, the charter requires minor revisions to remove references to phases. Attached is also included the revised charter. Best Regards, Osvaldo Novoa ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0