April 2025 - council - lists.icann.org

Action Items | GNSO Council meeting | 10 April 2025
by Terri Agnew April 14, 2025

April 14, 2025

Dear Councilors, Please find the action items, as stated during the meetings, below arising from the GNSO Council meetings held on 10 April 2025. Please refer to the Action Item page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> for updates on item completion progress. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. Item 3: Consent Agenda (5 minutes) GNSO Review of the GAC Communiqué Action Items: 1. On behalf of the GNSO Council Chair, the GNSO Secretariat communicates the GNSO Council Review of ICANN82 GAC Communiqué Issues of Importance to the ICANN Board. 2. On behalf of the GNSO Council, the GNSO Secretariat requests that the GNSO Liaison to the GAC also informs the GAC of the communication between the GNSO Council and the ICANN Board. Recommendations Report for the Transfer Policy Review PDP Action Items: On behalf of the GNSO Council, the GNSO Secretariat to transmit the report to the ICANN Board and communicate the outcomes from the GNSO Council's decision as appropriate. Item 4: COUNCIL VOTE - Confirmation of EPDP on Temporary Specification Team’s Intent to Modify RAA Requirements Related to Billing Contact (20 minutes) Action Items: The GNSO Council requests GNSO Support Staff to inform the ICANN org Global Domain Services Team of this motion. Item 5: COUNCIL DISCUSSION - Aspirational Statement Review (15 minutes) Action Items: GNSO Council leadership to add to the Council May meeting agenda for a vote. [added on Council Meeting Agenda planning google doc<https://docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0o…>] Item 6: COUNCIL DISCUSSION - Han Script Single Character gTLDs (Recommendation 3.17) (20 minutes) Action Items: GNSO Council leadership and staff to refine the options and create a comparison chart for the Council to consider. Item 7: COUNCIL UPDATE: Registration Data Request Service (10 minutes) Action Items: Leadership, with assistance from GNSO Support Staff, to follow up with the Council regarding the question of if the RDRS Findings Report should have a public comment period. Item 8: COUNCIL DISCUSSION: Next Steps for Whois Implementation Advisory Group (15 minutes) Action Items: Support Staff to send a follow-up message to Council, outlining potential next steps for Councilors to socialize with their groups. Item 9: Any Other Business (25 minutes) 9.1 - Update on ICANN83 Planning and GNSO Draft Schedule Action Items: GNSO Council leadership and staff to work with the GAC to develop ICANN83 topics early, including this item for discussion on the agenda for the 20 May webinar, and scheduling a meeting for a further review, with Council before ICANN83. 9.2 - WSIS+20 and internet governance discussions Action Items: Farzaneh Badii to volunteer for the WSIS+20 group on the GNSO Council list and staff to inform the group’s administrative support. 9.3 - Latin Diacritics PDP Working Group - Review of Project Plan Action Items: Support staff to inform the LD PDP WG that the Project Plan has been approved by the GNSO Council by non-objection. 9.4 - Standing Committee on Continuous Improvements - Review of Project Plan Action Items: Support staff to inform SCCI that the Project Plan and the accompanying assignment forms have been approved by the GNSO Council by non-objection. 9.5 - Council review of Assignment Forms for DNS Abuse and Accuracy Small Teams Action Items: Recirculate the assignment forms to the Council as Google docs, to better facilitate the collection of Councilor input. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Draft Minutes of 10 April 2025 GNSO Council Meeting
by John Emery April 14, 2025

April 14, 2025

Dear Councilors, Attached, please find the draft minutes of the GNSO Council Meeting held on 10 April 2025. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure section 3.5: "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 24 April. Thank you. Sincerely, John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

FW: [Ext] NEW: Preview the ICANN and IANA FY26 Operating and Financial Plans
by Julie Bisland April 14, 2025

April 14, 2025

FYI: From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, April 14, 2025 at 10:03 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: Preview the ICANN and IANA FY26 Operating and Financial Plans [https://danh45uab.cc.rs6.net/on.jsp?ca=73bea211-ff45-4b51-acd6-8ccc46249e54…] Monday, 14 April 2025 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] Click here to learn more about the New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents Information Sharing · NEW: Preview the ICANN and IANA FY26 Operating and Financial Plans · ONE WEEK FROM TODAY: ICANN83 Community Childcare Grants Program: Apply Now · ICANN Opens Application Period for New gTLD Applicant Support Program · ICANN Opens New gTLD Registry Service Provider Evaluation Program · Next Round Champions Toolkit Available in the Six ICANN Languages · ICANNWiki Seeking Volunteers Webinars · NEW: ICANN Webinar Series for Europe: ICANN’s Enforcement of DNS Abuse Mitigation Requirements – A Look at the First Year · NEW: Webinar: Preview the ICANN and IANA FY26 Operating and Financial Plans 🚨 Action Items 🚨 · Request for Applicant Guidebook related sessions at ICANN83 · Call for Applications: NextGen@ICANN84 · Call for ASP Mentors Public Comment · NEW: ICANN Public Comment Summary Report: Proposed Updates to the Operating Standards for Specific Reviews · NEW: Governance Document for the Recognition, Maintenance, and Derecognition of RIRs · Second IANA Naming Function Review Team (IFR2) Initial Report · Proposal for Thaana script Root Zone Label Generation Rules · FY26-FY30 Middle East Regional Plan · How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy Events · These events occur in April 2025. Information Sharing NEW: Preview the ICANN and IANA FY26 Operating and Financial Plans The Board is expected to adopt the ICANN FY26–30 Operating and Financial Plan and ICANN FY26 Operating Plan and Budget in May 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> ONE WEEK FROM TODAY: ICANN83 Community Childcare Grants Program: Apply Now Grants of up to $750 per family are available for ICANN Public Meeting participants who meet the criteria, are bringing children, and will incur expenses associated with babysitting or local childcare services. There will be no on-site meeting or conference-sponsored childcare services during ICANN83. Deadline: Monday, 21 April 2025, at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> ICANN Opens New gTLD Registry Service Provider Evaluation Program ICANN has opened the Registry Service Provider (RSP) Evaluation Program for the New Generic TopLevel Domains (gTLD) Program: Next Round. The RSP Evaluation Program was created to streamline the evaluation of gTLD applications by separating the evaluation of the technical aspects of operating the gTLD from the application for the name. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Next Round Champions Toolkit Available in the Six ICANN Languages ICANN is working with the community to identify potential Applicant Support Program (ASP) applicants – especially in regions that are currently under-represented in ICANN. If you are interested in helping to raise awareness among your own contacts or communities, please use the materials in the Next Round Champions Toolkit [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…>. To stay up to date on the New gTLD Program: Next Round and ASP, join the mailing list: nextroundinfo(a)icann.org. ASP leads, targets, and ideas can be sent to engagement.newgTLDprogram(a)icann.org<mailto:engagement.newgTLDprogram@icann.org>. ICANNWiki Seeking Volunteers ICANNWiki is seeking volunteers to assist with creating and editing articles and content for the site. Do you want to help? Getting started is as simple as requesting an account [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…>. Then, make sure to read the short content guide [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> on where to find reliable data. Happy editing! Webinars NEW: ICANN Webinar Series for Europe: ICANN’s Enforcement of DNS Abuse Mitigation Requirements – A Look at the First Year Date: Wednesday 23 April 2025 (12:00 - 13:00 UTC) Read more and Register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> NEW: Webinar: Preview the ICANN and IANA FY26 Operating and Financial Plans Date: Monday 28 April 2025 (05:30 - 07:00 UTC) Read more and Register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Action Items Request for Applicant Guidebook related sessions at ICANN83 ICANN’s New gTLD Program team will be available to provide updates on Applicant Guidebook topics to the interested parties during ICANN83. If you would like the team to join any of your sessions, please send an email to nextround_policyimplementation(a)icann.org<mailto:nextround_policyimplementation@icann.org> indicating which topics you would like to be briefed on and during which session no later than 30 April 2025. Call for Applications: NextGen@ICANN84 ICANN wants to hear from university students living and studying in the Asia Pacific region who are interested in the future of the Internet and participating in the Public Meeting. Deadline: 09 May 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Call for ASP Mentors ICANN is seeking volunteer mentors who would like to offer their expertise to supported applicants as part of the ASP in the new gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…>. ICANN is looking for mentors who can share insights and experience across ICANN Languages (Arabic, Chinese, English, French, Russian, or Spanish) to support diverse gTLD applicants. Mentors may play a role in: advising applicants on navigating the gTLD application process and DNS industry; identifying resources; providing guidance; sharing experiences as appropriate; and helping supported applicants navigate the ICANN community and Public Meetings. If you or someone in your network might be interested, please refer to the mentor registration announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> for more information. Questions about the ASP or becoming a supported applicant Mentor can be sent to globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Public Comment NEW: ICANN Public Comment Summary Report: Proposed Updates to the Operating Standards for Specific Reviews [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> NEW: Governance Document for the Recognition, Maintenance, and Derecognition of RIRs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Open for Submissions: 14 April 2025 Closed for Submissions: 27 May 2025 Second IANA Naming Function Review Team (IFR2) Initial Report [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Submissions Opening Date: Thursday, 20 March 2025 Submissions Closing Date: Monday, 28 April 2025 Proposal for Thaana script Root Zone Label Generation Rules [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Submissions Opening Date: Thursday, 27 March 2025 Submissions Closing Date: Wednesday, 7 May 2025 FY26-FY30 Middle East Regional Plan [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Submissions Opening Date: Monday, 31 March 2025 Submissions Closing Date: Monday, 12 May 2025 How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> Submissions Opening Date: Wednesday, 9 April 2025 Submissions Closing Date: Monday, 19 May 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…>. Events These events occur in April 2025. To learn more, please visit our community engagement calendar [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…>. · MA Domain Day 2025 · IGF Moldova 2025 · Taiwan Network Operators' Group 6 (TWNOG6) · Local APIGA 2025- Taipei · TWNIC Engagement Forum 2025 · ICANN Webinar Series for Europe: ICANN’s Enforcement of DNS Abuse Mitigation Requirements – A Look at the First Year · ARIN 55 · Webinar: Preview the ICANN and IANA FY26 Operating and Financial Plans Volume 7, Issue 28 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…> | Next Issue: Thursday, 17 April 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001QGidEtI…>

1 0

Adjusted date & time | Meeting Invitation | GNSO Council - Reviews- Seeking Alignment (PHR, ATRT4) with Appointed Board Members | Thursday, 17 April 2025
by Terri Agnew April 12, 2025

April 12, 2025

**The date and time have been changed from 28 April 12:00 UTC to 17 April at 14:00 UTC, please make sure to adjust your calendars. Dear all, The GNSO Council - Reviews- Seeking Alignment (PHR, ATRT4) with Appointed Board Members is scheduled on Thursday, 17 April 2025 at 14:00 UTC for 60 minutes. This meeting will be recorded for those who are unable to make it. 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> Visit the Wiki Agenda page: https://icann-community.atlassian.net/wiki/x/GIBoD Check your time zone: https://tinyurl.com/5ydb4kzz Join Zoom Meeting https://icann.zoom.us/j/96611661142?pwd=K2VpaHlzNkNuY1J6YzRYcW1sd0VjUT09 Meeting ID: 966 1166 1142 Passcode: Z4B3SUR!U& --- One tap mobile +13126266799,,96611661142#,,,,*0505103780# US (Chicago) +13462487799,,96611661142#,,,,*0505103780# US (Houston) Meeting ID: 966 1166 1142 Passcode: 0505103780 Find your local number: https://icann.zoom.us/u/actl7q9Q9B Thank you. Kind regards, Terri Policy Team Supporting the GNSO

2 1

Additional information to share | Re: Re: Our Deepest Condolences | Nigel Hickson
by Terri Agnew April 11, 2025

April 11, 2025

Hello all, Additional information to share. **** A couple of updates about Nigel: The family have created a fundraising page where people can make donations in lieu of flowers, now or on the funeral day itself. The donations will support Cancer Research UK and the Potters Bar Scout Grouphttps://www.memorygiving.com/nigeljohnhickson [memorygiving.com]<https://urldefense.com/v3/__https:/www.memorygiving.com/nigeljohnhickson__;…> All are welcome to join Nigel's funeral on Thursday, May 1st at 11am BST at St Mary’s Church, The Walk, Potters Bar, UK. There will also be a livestream available from the church. It will be on the Facebook page of the church: https://m.facebook.com/stmaryspb/ [m.facebook.com]<https://urldefense.com/v3/__https:/m.facebook.com/stmaryspb/__;!!PtGJab4!9w…> Anyone who would like to join remotely is welcome to join at 11am BST (UTC +1) on May 1, 2025. And I am still taking messages for the family if anyone would like these shared please send to me <adam.peake(a)icann.org<mailto:adam.peake@icann.org>> Warm regards, Ada From: Terri Agnew <terri.agnew(a)icann.org> Date: Thursday, April 3, 2025 at 11:23 AM To: Anne ICANN <anneicanngnso(a)gmail.com>, "Thomas Rickert | rickert.law" <thomas(a)rickert.law> Cc: Susan Payne <susan.payne(a)comlaude.com>, "council(a)icann.org" <council(a)icann.org>, GNSO-Secs <gnso-secs(a)icann.org> Subject: Re: [council] Re: Our Deepest Condolences Hello all, Update to share. Please do not use the google form listed below. ICANN is gathering messages of appreciation and memories from both ICANN staff and the community to share with Nigel's family. These will be compiled alongside messages received by UK Government and collated into a book to be sent to his family. Please email Adam Peake adam.peake(a)icann.org<mailto:adam.peake@icann.org> , with your message. it would be very helpful if the subject line of any message included "Nigel Hickson". With this in the works, maybe no need for the GNSO Council to have their own book? I am sure Nigel's family will enjoy reading your memories and appreciation – he is much loved. All the best, Kind regards, Terri Policy Team Supporting the GNSO From: Terri Agnew <terri.agnew(a)icann.org> Date: Thursday, April 3, 2025 at 10:52 AM To: Anne ICANN <anneicanngnso(a)gmail.com>, "Thomas Rickert | rickert.law" <thomas(a)rickert.law> Cc: Susan Payne <susan.payne(a)comlaude.com>, "council(a)icann.org" <council(a)icann.org>, GNSO-Secs <gnso-secs(a)icann.org> Subject: Re: [council] Re: Our Deepest Condolences Hi all, We wanted to pass along the following information. ICANN is gathering messages of appreciation and memories in this Google Form https://forms.gle/486sGR32ZR8xu6JY6 from both ICANN staff and the community to share with Nigel's family. These will be compiled alongside messages received by UK Government and collated into a book to be sent to his family. With this in the works, maybe no need for the GNSO Council to have their own book? Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: Anne ICANN <anneicanngnso(a)gmail.com> Date: Wednesday, April 2, 2025 at 6:18 PM To: "Thomas Rickert | rickert.law" <thomas(a)rickert.law> Cc: Susan Payne <susan.payne(a)comlaude.com>, "council(a)icann.org" <council(a)icann.org>, GNSO-Secs <gnso-secs(a)icann.org> Subject: Re: [council] Re: Our Deepest Condolences Thomas - I wonder if GNSO Council should have its own book. The reason is there are so many GAC reps and theirs will be FULL! Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Apr 2, 2025 at 7:10 AM Thomas Rickert | rickert.law <thomas(a)rickert.law> wrote: Great idea, Anne. I think it is likely the GAC will offer a book. Inam happy to ask Nico if that is the case. We could then write into that book, too. Ok? Best, Thomas Sent from my mobile device. Please excuse typos and brevity. ________________________________ Von: Anne ICANN via council <council(a)icann.org<mailto:council@icann.org>> Gesendet: Wednesday, April 2, 2025 3:22:23 PM An: Susan Payne <susan.payne(a)comlaude.com<mailto:susan.payne@comlaude.com>> Cc: council(a)icann.org<mailto:council@icann.org> <council(a)icann.org<mailto:council@icann.org>>; GNSO-Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Betreff: [council] Re: Our Deepest Condolences I must admit to being in shock as I just spoke with Nigel in Seattle regarding the WSIS+20 SO/AC Discussion Group. Certainly his work in building a bridge between the GAC and the GNSO has been instrumental and his time commitment very impressive indeed. I recall that when Pam Little passed, we put together a Memories book to give to her family. Councilors wrote personal messages honoring her. Maybe we can do the same for Nigel's family in the meeting in Prague? Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com<mailto:anneicanngnso@gmail.com> On Tue, Apr 1, 2025 at 2:26 PM Susan Payne via council <council(a)icann.org<mailto:council@icann.org>> wrote: Thank you for sharing these lovely words Greg, Nacho and Tomslin. Nigel is such a loss to the UK and wider ICANN and Internet Governance communities. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DBAACA.E4EAA420] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> Error! Filename not specified. ________________________________ From: Devan Reed via council <council(a)icann.org<mailto:council@icann.org>> Sent: Tuesday, April 1, 2025 4:46:16 PM To: council(a)icann.org<mailto:council@icann.org> <council(a)icann.org<mailto:council@icann.org>> Cc: GNSO-Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: [council] FW: Our Deepest Condolences Dear Councilors, For your information, we sent the attached letter to the GAC Chair. Kind regards, Devan From: Devan Reed <devan.reed(a)icann.org<mailto:devan.reed@icann.org>> Date: Tuesday, April 1, 2025 at 10:36 AM Cc: GNSO-Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, "gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>" <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Subject: Our Deepest Condolences Dear Nico, Please find attached a letter regarding our deepest condolences and sympathies regarding the passing of an extremely valuable community member, Nigel Hickson. This will be posted to the GNSO Correspondence<https://gnso.icann.org/en/council/correspondence/2025> page shortly. Kind regards, Devan Devan Reed Secretariat Operations Coordinator Policy Development Team Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&…> ________________________________ 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 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 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 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<https://comlaude.com/> _______________________________________________ council mailing list -- council(a)icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave(a)icann.org<mailto:council-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

GNSO Council resolutions 10 April 2025
by Terri Agnew April 11, 2025

April 11, 2025

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 10 April 2025 which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. Thank you. Kind regards, Terri 20250410-1 Consent Agenda GNSO Council Motion to Adopt the GNSO Council Review of ICANN82 GAC Communiqué Issues of Importance Submitted by: Nacho Amadoz Whereas, 1. The Governmental Advisory Committee (GAC) advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The Generic Names Supporting Organization (GNSO) is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO Council has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present, or future gTLD policy activities that may directly or indirectly relate to Advice provided by the GAC. 4. The GNSO Council's review of GAC Communiqué Advice and Issues of Importance<https://gnso.icann.org/sites/default/files/policy/2025/correspondence/dibia…> is intended to further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board, and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the ICANN82 Seattle Communiqué Issues of Importance<https://gnso.icann.org/sites/default/files/policy/2025/draft/draft-gnso-cou…> (there was no GAC Advice provided for ICANN82) and requests that the GNSO Council Chair communicate the GNSO Council Review of ICANN82 GAC Communiqué Issues of Importance to the ICANN Board. 2. The GNSO Council requests that the GNSO Liaison to the GAC also informs the GAC of the communication between the GNSO Council and the ICANN Board. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> 20250410-2 Consent Agenda GNSO Council Motion to Approve the GNSO Council Recommendations Report to the ICANN Board regarding the Transfer Policy Review Policy Development Process Working Group Submitted by: Nacho Amadoz Whereas: 1. On 12 March 2025, the GNSO Council unanimously approved<https://gnso.icann.org/en/council/resolutions/2020-current#202503> the forty-seven (47) Full Consensus policy recommendations from the Transfer Policy Review Policy Development Process Working Group by a GNSO Supermajority; 2. On 31 March 2025, as required under the ICANN Bylaws, a GNSO Council Recommendations Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-r…> to the ICANN Board on the approved PDP recommendations was submitted to the GNSO Council for its consideration. Resolved: 1. The GNSO Council approves the Recommendations Report to the ICANN Board regarding the Final Recommendations from the Transfer Policy Review Policy Development Process Working Group and instructs the GNSO Secretariat to transmit the report to the ICANN Board and communicate the outcomes from the GNSO Council's decision as appropriate. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> 20250410-3 **Updated as friendly amendment Motion to confirm EPDP on Temporary Specification Team’s Intent to Modify RAA Requirements Related to Billing Contact Submitted by: Greg Dibiase Seconded by: Farzaneh Badii WHEREAS 1. On 17 May 2018<https://www.icann.org/resources/board-material/resolutions-2018-05-17-en>, the ICANN Board adopted the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…> (Temporary Specification) pursuant to the procedures in the Registry Agreement and Registrar Accreditation Agreement concerning the establishment of temporary policies. 2. Following the adoption of the Temporary Specification, and per the procedure for Temporary Policies as outlined in the Registry Agreement and Registrar Accreditation Agreement, a Consensus Policy development process as set forth in ICANN's Bylaws needed to be initiated immediately and completed within a one-year time period from the implementation effective date (25 May 2018) of the Temporary Specification. 3. On 19 July 2018, the GNSO Council approved the EPDP Initiation Request<https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…> and the EPDP Team Charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…>. 4. The EPDP followed the prescribed EPDP procedures as stated in the Bylaws, resulting in a Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> delivered on 20 February 2019. 5. The GNSO Council reviewed and discussed the recommendations of the EPDP Team (Recommendations) and approved<https://gnso.icann.org/en/council/resolutions/1999-2019#20190304-1> all Recommendations on 4 March 2019 by a GNSO Supermajority vote. 6. The GNSO Council vote exceeded the required voting threshold set forth in the ICANN Bylaws to impose new Consensus Policies on ICANN contracted parties. 7. The ICANN Board adopted the Recommendations for a new Consensus Policy on gTLD Registration Data as set forth in section 5 of the Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> in accordance with Sections A and B of the attached scorecard titled "Scorecard: EPDP Phase 1 Recommendations<https://www.icann.org/en/system/files/files/epdp-scorecard-15may19-en.pdf>". 8. The ICANN Board directed the President and CEO, or his designee(s), to develop and execute an implementation plan for the adopted Recommendations that is consistent with the guidance provided by the GNSO Council. 9. Throughout the implementation phase, ICANN org, in cooperation with the GNSO Council Liaison to the Implementation Review Team (IRT), identified questions concerning the Recommendations, including areas for additional clarification and potential drafting errors. 10. During these discussions, former EPDP Team members, the GNSO Council Liaison to the IRT, and the GNSO Council acknowledged the unique circumstances involved in the Board’s adoption of the Temporary Specification and the narrow timeframe within which the EPDP Team had to produce theRecommendations. 11. In light of this truncated timeline, the GNSO Council acknowledges, in particular, that some of the Recommendations could have benefitted from further discussions and, accordingly, acknowledged that the Recommendations had some unintentional omissions and errors. 12. On 21 February 2024, ICANN org published the Registration Data Policy<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> with an effective date of 21 August 2025. 13. On 8 August 2024, ICANN org informed the IRT that billing contact data must still be collected and retained pursuant to the current requirements in the Registrar Accreditation Agreement. 14. In response, some members of the IRT expressed the view that the absence in the Recommendations of a specific consensus policy recommendation to supersede and eliminate Registrar Accreditation Agreement requirements related to processing billing contact data was a drafting error, and that the EPDP Team intended for registrars’ collection of billing contact data to become optional and not mandatory. No IRT members expressed disagreement with this view. For the avoidance of doubt, the relevant sections of the Registrar Accreditation Agreement the IRT referenced include section 3.6 (as it relates to 3.4.1.3), 3.4.1.3, and 1.1.2 - 1.1.5 of the Data Retention Specification. 15. The GNSO Council acknowledges that the role of the GNSO Council during policy implementation is to “serve as a resource for staff who have questions about the background or intent of the policy recommendations during its implementation. The GNSO Council may continue to provide input on the implementation of a policy, for example, if the GNSO Council believes that the implementation is inconsistent with the policy.” 16. The GNSO Council also acknowledges that unless in conflict with or otherwise modified by a policy recommendation, current contractual requirements and consensus policy requirements remain in place following the implementation of a new ICANN Consensus Policy. 17. ICANN org asked the GNSO Council to provide guidance on whether the Recommendations were intended to supersede and eliminate the current Registrar Accreditation Agreement requirements for the collection, retention, and escrow of registrant billing contact data, and the GNSO Council discussed this topic during its meetings on 19 December 2024<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, 13 February 2025<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, and 12 March 2025<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>. 18. In its discussion, the GNSO Council agreed that the EPDP Team did intend to eliminate the requirement for registrars to collect and retain billing contact data under an ICANN purpose for processing; however, the GNSO Council acknowledged that there is no corresponding policy recommendation that states this. 19. The GNSO Council further acknowledges that it is not the role of the GNSO Council nor the IRT to create policy, as policy is created per the GNSO Policy Development Process in the ICANN Bylaws, Annex A<https://www.icann.org/en/governance/bylaws#annexA>. 20. The GNSO Council acknowledges that the EPDP Phase 1 Team was working under an exceptional timeline due to the Board’s adoption of a Temporary Specification (the first of its kind), and for that reason, the Recommendations fail to comprehensively capture the Working Group’s intent related to the collection and escrow of billing contact data. 21. With this exceptional circumstance in mind, the GNSO Council confirms that the EPDP Team intended to eliminate the current requirements in the Registrar Accreditation Agreement related to Billing Contact. This intention was demonstrated in the Final Report, which did not include a recommendation for registrars to collect and retain billing contact data and which was delivered pursuant to the EPDP Team Charter which directed the EPDP Team to consider the collection and retention of billing contact data. RESOLVED 1. The GNSO Council confirms its guidance to ICANN org that the EPDP Team did intend to modify the current Registrar Accreditation Agreement requirements related to billing contact, and the current RAA requirements for the collection, retention, and escrow of billing contact have been eliminated by the Registration Data Policy. For the avoidance of doubt, the modified sections include section 3.6 (as it relates to 3.4.1.3), 3.4.1.3, and 1.1.2 - 1.1.5 of the Data Retention Specification. 2. The GNSO Council confirms and commits that, going forward, it will be specified in Working Group Charters that if the Working Groups intend to modify a requirement within the Registry Agreement, Registrar Accreditation Agreement, or Consensus Policy via Consensus Policy recommendations, the policy recommendations must explicitly and specifically identify which requirements are intended to be modified and how such requirements are recommended to be modified per their Consensus Policy recommendations. 3. The GNSO Council requests GNSO Support Staff to inform the ICANN org Global Domain Services Team of this motion. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> IPC Statement<https://gnso.icann.org/sites/default/files/policy/2025/presentation/ipc-sta…>

1 0

Recordings | GNSO Council Meeting | Thursday, 10 April 2025
by Terri Agnew April 11, 2025

April 11, 2025

Dear all, Please find below the audio and zoom recordings of the GNSO Council Meeting that took place on Thursday, 10 April 2025. Audio only: https://icann.zoom.us/rec/play/H66oq2jwJqE3dH30c4OggQikOKZs7CjLMZx4ZKWk_bTm… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/1BdJrVMYICLOfeH4W7CEh-q9Udop0TZrUmaQ47ekzkZ… The recordings and transcriptions of the calls are posted on the GNSO Calendar page. <https://gnso.icann.org/en/group-activities/calendar/2025> Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

GNSO WSIS+20 mapping document -
by desiree-me April 10, 2025

April 10, 2025

Dear Councilors Thank you for agreeing to review our informal group team exercise by April 18. Here's a link to the document https://docs.google.com/document/d/1fM5b8tZX1APSUhEovc0qHWXc_wg3HzJ8__mJuvZ… We would appreciate the Council's review of this draft so we can share it more broadly with the informal GAC IG Topic leads and cccNSO Internet Governance Liaison Committee first, and ultimately with the SO/AC informal discussion group. Thank you Desiree -- GNSO Councilor, NCA CPH

1 0

Re: [Ext] IPC Statement on No Vote
by Terri Agnew April 10, 2025

April 10, 2025

Hi Damon, Thank you very much, confirm receipt. Kindest regards, Terri From: "Ashcraft, Damon" <dashcraft(a)swlaw.com> Date: Thursday, April 10, 2025 at 4:18 PM To: Terri Agnew <terri.agnew(a)icann.org> Cc: "DiBiase, Gregory" <dibiase(a)amazon.com>, Susan Payne <susan.payne(a)comlaude.com>, GNSO Council List <council(a)gnso.icann.org> Subject: [Ext] IPC Statement on No Vote Hi Terri, Here is our statement: The IPC appreciates opposing viewpoints and research that was done on this topic. While the topic of billing data collection may have been discussed during the PDP, no decision was reached or recorded and we’re simply not comfortable with characterizing this omission being a drafting error and thus effectively having Council amend a section of the RAA. Thank you again for the discussion and vote. Thanks, Damon J. Damon Ashcraft , P.C. O: 602.382.6389<tel:602.382.6389> | M: 602.510.1640<tel:602.510.1640> dashcraft(a)swlaw.com<mailto:dashcraft@swlaw.com> SNELL & WILMER swlaw.com [swlaw.com]<https://urldefense.com/v3/__https:/www.swlaw.com/__;!!PtGJab4!_u8LRIHBR8L2u…> | LinkedIn [linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/snell-&-wilmer_…> One East Washington Street | Suite 2700 | Phoenix, AZ 85004‑2556 Albuquerque | Boise | Dallas | Denver | Las Vegas | Los Angeles | Los Cabos | Orange County | Palo Alto | Phoenix | Portland | Reno | Salt Lake City | San Diego | Seattle | Tucson | Washington, D.C. This email and any attachments may be confidential and protected by legal privilege. If you have received this message in error, please do not disclose the contents to anyone. Please notify the sender by return email and delete this email as well as any attachments from your system.

1 0

IPC Statement on No Vote
by Ashcraft, Damon April 10, 2025

April 10, 2025

Hi Terri, Here is our statement: The IPC appreciates opposing viewpoints and research that was done on this topic. While the topic of billing data collection may have been discussed during the PDP, no decision was reached or recorded and we’re simply not comfortable with characterizing this omission being a drafting error and thus effectively having Council amend a section of the RAA. Thank you again for the discussion and vote. Thanks, Damon J. Damon Ashcraft , P.C. O: 602.382.6389<tel:602.382.6389> | M: 602.510.1640<tel:602.510.1640> dashcraft(a)swlaw.com<mailto:dashcraft@swlaw.com> SNELL & WILMER swlaw.com<https://www.swlaw.com/> | LinkedIn<https://www.linkedin.com/company/snell-&-wilmer> One East Washington Street | Suite 2700 | Phoenix, AZ 85004‑2556 Albuquerque | Boise | Dallas | Denver | Las Vegas | Los Angeles | Los Cabos | Orange County | Palo Alto | Phoenix | Portland | Reno | Salt Lake City | San Diego | Seattle | Tucson | Washington, D.C. This email and any attachments may be confidential and protected by legal privilege. If you have received this message in error, please do not disclose the contents to anyone. Please notify the sender by return email and delete this email as well as any attachments from your system.

1 0