November 2025 - council - lists.icann.org

FW: [Ext] NEW: A Look Back at ICANN84
by Julie Bisland Nov. 17, 2025

Nov. 17, 2025

FYI: From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, November 17, 2025 at 10:00 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: A Look Back at ICANN84 [https://danh45uab.cc.rs6.net/on.jsp?ca=98092fa1-7fee-429b-8cc6-2b76532a5f33…] Monday, 17 November 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=001G5NPKlS…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> 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: A Look Back at ICANN84 Webinars · TOMORROW: Advancing the ICANN Reviews Conversation: Join the Cross Community Group Webinars · NEW: ICANN Webinar Series - Europe: Key Insights from the Registration Data Request Service (RDRS) Two-Year Pilot and Next Steps Next Round · ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics · Next Round Champions Toolkit Available in the Six ICANN Languages · Call for ASP Mentors 🚨 Action Items 🚨 · THIS FRIDAY: Call for Expressions of Interest for the ICANN Director Nominated by At-Large · THIS FRIDAY: Call for Nominations: 2026 ICANN Leadership Program · ONE WEEK FROM TODAY: Updated: ICANN Issues Call for UA Day 2026 Proposals · ICANN Community Excellence Award: Now Accepting Nominations · ICANN Request for Proposal: Evaluator Panels for String Similarity and Variant Strings for the new gTLD Program: 2026 Round · ICANN Request for Proposal: New gTLD Program: 2026 Round Background Screening Services · ICANNWiki Seeking Volunteers Public Comment · CLOSES TODAY: Proposed Next Round Base gTLD Registry Agreement - Public Comment 2 of 2 · ONE WEEK FROM TODAY: Draft LAC Regional Strategic Plan for Fiscal Years 2026–2030 · ICANN Public Meeting Proposed Dates for 2029–2033 · String Similarity Evaluation Data for New gTLD Program: Next Round · Registration Data Request Service (RDRS) Policy Alignment Analysis · Timeline for Urgent Requests for Lawful Disclosure of Nonpublic Registration Data · Name Collision IPv6 Research Study Events · These events occur in November 2025. Information Sharing NEW: A Look Back at ICANN84 In total, 1,594 people attended ICANN84 in person, including 104 first-time attendees, and 526 people participated virtually Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Webinars TOMORROW: Advancing the ICANN Reviews Conversation: Join the Cross Community Group Webinars All community members – including those new to ICANN Reviews – are encouraged to attend by registering for one, or both, of the sessions: Tuesday, 18 November, at 06:00 UTC Tuesday, 18 November, at 18:00 UTC Read more and register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> NEW: ICANN Webinar Series - Europe: Key Insights from the Registration Data Request Service (RDRS) Two-Year Pilot and Next Steps Wednesday 26 November 2025 (14:00 - 14:30 UTC) Read more and register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Next Round ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics ICANN org is developing supplemental, complementary materials to aid prospective generic top-level domain (gTLD) applicants in understanding the Next Round application requirements, and how to navigate the application and evaluation processes. Blog [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> 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=001G5NPKlS…>. 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>. 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=001G5NPKlS…>. 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=001G5NPKlS…> 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>. Action Items THIS FRIDAY: Call for Expressions of Interest for the ICANN Director Nominated by At-Large On behalf of the At-Large Advisory Committee (ALAC) Board Candidate Evaluation Committee (BCEC), the At-Large Community is seeking Expressions of Interest (EoIs) from individuals who wish to serve as an ICANN Board Director. The nominated candidate will serve a three-year term starting at the end of ICANN87, which is currently scheduled for 17–22 October 2026. DEADLINE: Friday, 21 November 2025 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> THIS FRIDAY: Call for Nominations: 2026 ICANN Leadership Program From 30 September – 21 November 2024, ICANN will issue a call for nominations for the 2026 Leadership Program, scheduled for 5 – 6 March in Mumbai, India, just before the ICANN85 Public Meeting. Current and incoming community leaders interested in participating in the program need to be endorsed by their Supporting Organization, Advisory Committee, or stakeholder group chairs. The ICANN organization will reach out to the respective chairs for nominations and a registration link will be sent directly to individuals who are nominated. The Leadership Program does not provide financial support for travel to Mumbai, but does cover accommodations and offer a stipend for the days a participant is involved in the program. Questions may be sent to Fernanda Iunes at fernanda.iunes(a)icann.org. Announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> ONE WEEK FROM TODAY: Updated: ICANN Issues Call for UA Day 2026 Proposals The deadline to submit a proposal has been extended from 9 November 2025 to 24 November 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> ICANN Community Excellence Award: Now Accepting Nominations The Community Excellence Award recognizes ICANN community members who have deeply invested in consensus-based solutions and contributed substantively to the ICANN multistakeholder model. DEADLINE: 8 January 2026 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> ICANN Request for Proposal: New gTLD Program: 2026 Round Background Screening Services Its purpose is to safeguard registrants and the public interest by ensuring that corporations, organizations, and institutions are in good standing and eligible to operate a gTLD. DEADLINE: 23:59 UTC on 16 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> ICANN Request for Proposal: Evaluator Panels for String Similarity and Variant Strings for the new gTLD Program: 2026 Round The selected provider(s) will also be required to collaborate with ICANN on the development of evaluation guides for the work conducted by the panels, ensuring that the evaluation processes are transparent, consistent, and repeatable across all gTLD applications. DEADLINE: 23:59 UTC on 16 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> 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=001G5NPKlS…>. 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=001G5NPKlS…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…>source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> on where to find reliable data. Happy editing! Public Comment CLOSES TODAY: Proposed Next Round Base gTLD Registry Agreement - Public Comment 2 of 2 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Submissions Opening Date: Tuesday, 30 September 2025 Submissions Closing Date: Monday, 17 November 2025 ONE WEEK FROM TODAY: Draft LAC Regional Strategic Plan for Fiscal Years 2026–2030 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Submissions Opening Date: Thursday, 9 October 2025 Submissions Closing Date: Monday, 24 November 2025 ICANN Public Meeting Proposed Dates for 2029–2033 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Submissions Opening Date: Monday, 13 October 2025 Submissions Closing Date: Monday, 1 December 2025 String Similarity Evaluation Data for New gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Submissions Opening Date: Thursday, 16 October 2025 Submissions Closing Date: Thursday, 4 December 2025 Registration Data Request Service (RDRS) Policy Alignment Analysis [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Submissions Opening Date: Thursday, 30 October 2025 Submissions Closing Date: Tuesday, 9 December 2025 Timeline for Urgent Requests for Lawful Disclosure of Nonpublic Registration Data [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Submissions Opening Date: Wednesday, 22 October 2025 Submissions Closing Date: Monday, 15 December 2025 Name Collision IPv6 Research Study [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> Submissions Opening Date: Monday, 20 October 2025 Submissions Closing Date: Monday, 22 December 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…>. Events These events occur in November 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=001G5NPKlS…>. · Training for Fresh Graduates and Women in ICT-Oman 2025 · Local APIGA 2025 - Pakistan · CIO100 Symposium and Awards 2025 · Bitkom Intellectual Property Working Group Meeting · Engagement Evening for German Internet Community Members · Middle East Network Operators Group 2025 (MENOG'25) · ICANN Webinar Series - Europe: Key Insights from the Registration Data Request Service (RDRS) Two-Year Pilot and Next Steps Volume 7, Issue 83 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…> | Next Issue: Thursday, 20 November 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001G5NPKlS…>

1 0

Draft Minutes of the 13 November 2025 GNSO Council Meeting
by John Emery Nov. 17, 2025

Nov. 17, 2025

Dear Councilors, Attached, please find the draft minutes of the GNSO Council Meeting held on 13 November 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 27 November. 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

Reminder: Input welcome on GNSO Council agenda for 2025 meetings
by Terri Agnew Nov. 17, 2025

Nov. 17, 2025

Dear councilors, A reminder to all that a Google doc<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> is open for all to add their suggestions and comments to the upcoming GNSO Council meeting agendas. This does not have to be in the form of a full agenda item proposal, simple comments and questions are equally welcome! You are welcome to add to the document<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> via the comments feature. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

10 48

Document and Motion deadline | Monday, 01 December 2025 at 23:59 UTC for GNSO Council Meeting 11 December 2025 at 21:00 UTC
by Terri Agnew Nov. 17, 2025

Nov. 17, 2025

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 01 December 2025 at 23:59 UTC) for the GNSO Council Meeting on Thursday, 11 December 2025 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Motions Wiki at: https://icann-community.atlassian.net/wiki/x/ZKifBg Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

[council@icann.org]: Please confirm to continue.
by ICANN . Nov. 14, 2025

Nov. 14, 2025

1 0

Re: [Ext] PPSAI IRT Answers to Threshold Questions from Council
by Jason Kean Nov. 13, 2025

Nov. 13, 2025

Dear Susan, Thank you for the Council’s responses to the IRT’s requested guidance. And many thanks to Paul for shepherding this work forward as Council Liaison to the PPSAI IRT. We look forward to working with Ashley Heineman as the new Council Liaison to the PPSAI IRT moving forward. The ICANN org team is excited to start the next phase of implementation work with the IRT. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: Susan Payne <susan.payne(a)comlaude.com> Date: Thursday, November 13, 2025 at 11:19 AM To: Jason Kean <jason.kean(a)icann.org> Cc: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org>, John Emery <john.emery(a)icann.org>, Caitlin Tubergen <caitlin.tubergen(a)icann.org>, Anne ICANN via council <council(a)icann.org> Subject: [Ext] PPSAI IRT Answers to Threshold Questions from Council Dear Jason, In response to your request, as PPSAI Project Manager, to Council on 1 August 2025 concerning the Privacy and Proxy Services Accreditation Issues (PPSAI) Threshold Questions (TQ), please find the attached responses from Council. The PPSAI Small Team, chaired by Paul McGrady worked diligently to provide helpful and consensus-driven responses, which were presented at the ICANN84 GNSO Council meeting and amended to updated language for TQ B. Having received no objections from Councilors by the deadline, I am pleased to send these responses on the PPSAI TQs from the GNSO Council to ICANN org and the PPSAI IRT. We look forward to the updates from our new Council Liaison to the PPSAI IRT, Ashley Heineman. Thank you, Susan Payne GNSO Council Chair ________________________________ 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 [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com__;!!PtGJab4!5Tbwbtvllb03ifi…>

1 0

GNSO Council resolutions 13 November 2025
by Terri Agnew Nov. 13, 2025

Nov. 13, 2025

Dear all, Please find below the resolutions from the GNSO Council meeting on 13 November 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 Policy Team Supporting the GNSO Option 1 has been withdrawn by both Anne Aikman-Scalese & Lawrence Olawale-Roberts Council Confirmation of Policy Intent regarding Specific IGO/INGO PDP Recommendations Submitted By: Anne Aikman-Scalese Seconded By: Lawrence Olawale-Roberts Whereas: 1. In November 2013, the Working Group for the Protection of International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) in All gTLDs completed a Policy Development Process (PDP) and submitted its Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/issues/igo-ingo-final-…> to the GNSO Council; 2. On 20 November 2013, the GNSO Council approved [gnso.icann.org]<https://urldefense.com/v3/__http:/gnso.icann.org/en/council/resolutions*201…> all the consensus recommendations in the PDP Final Report; 3. On 30 April 2014, the ICANN Board approved<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> those of the GNSO’s consensus recommendations that were not inconsistent with advice received from the Governmental Advisory Committee (GAC) on the topic of IGO and INGO protections, which recommended top-level protections for specific identifiers associated with the Red Cross Red Crescent Movement and the International Olympic Committee and the full names of specific International Governmental Organizations and International Non-TGovernmental Organizations; 4. In the context of implementing the PDP Recommendations in the Next Round Applicant Guidebook, the implementation staff and the Implementation Review Team (IRT) discussed potential alternatives for the implementation of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP (“the Applicable Recommendations”), the so-called “Options 1 and 2” as set out in the staff briefing [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> but could not reach agreement on which option properly reflects the intent and scope of the protections afforded by the Applicable Recommendations. 5. On 15 September 2025 staff referred this matter to the GNSO Council for guidance on the interpretation of the Applicable Recommendations, as a late addition to the agenda of the GNSO Council meeting on 18 September 2025. 6. On 16 September 2025, the ICANN Board sent correspondence<https://www.icann.org/en/system/files/correspondence/sinha-to-samme-nlar-am…> to the GNSO Council, providing the Board’s interpretation of the relevant recommendations, while acknowledging that the decision resides with the Council; 7. The Council had a preliminary discussion on the request for guidance during its meeting on 18 September; 8. The Council scheduled an Extraordinary Meeting on 9 October 2025, to progress the issue; and, 9. The Council has now carefully considered the natural meaning and original intent of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP. Resolved: 1. The GNSO Council confirms that the intent of the relevant recommendations is only to ensure that no organization other than the relevant organization can apply for the exact match of the specific, protected identifier associated with that organization, and that as such, Reserved Name strings are now placed in the category formerly-termed “ineligible for delegation” under paragraph 2.2.1.2.3 of the 2012 Round AGB. Accordingly, the relevant identifiers shall not be included in the String Similarity Evaluation in the New gTLD Program and such a relevant identifier shall not operate as a bar to an application for a confusingly similar string by another applicant, during evaluation. Objection proceedings and GAC Advice could still be brought against such a third-party application, where applicable, in the usual manner. Pursuant to existing policy, any application submitted by a protected organization for its protected string would remain subject to existing policy barring delegation if such string is found to be visually-confusingly similar to a string previously delegated. Option 1 would align with this interpretation. 2. The GNSO Council requests that its liaisons to the SubPro IRT provide this information to the implementation staff and IRT. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> Option 2 has been withdrawn by both Anne Aikman-Scalese & Lawrence Olawale-Roberts Council Confirmation of Policy Intent regarding Specific IGO/INGO PDP Recommendations Submitted By: Anne Aikman-Scalese Seconded By: Lawrence Olawale-Roberts Whereas: 1. In November 2013, the Working Group for the Protection of International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) in All gTLDs completed a Policy Development Process (PDP) and submitted its Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/issues/igo-ingo-final-…> to the GNSO Council; 2. On 20 November 2013, the GNSO Council approved [gnso.icann.org]<https://urldefense.com/v3/__http:/gnso.icann.org/en/council/resolutions*201…> all the consensus recommendations in the PDP Final Report; 3. On 30 April 2014, the ICANN Board approved<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> those of the GNSO’s consensus recommendations that were not inconsistent with advice received from the Governmental Advisory Committee (GAC) on the topic of IGO and INGO protections, which recommended top-level protections for specific identifiers associated with the Red Cross Red Crescent Movement and the International Olympic Committee and the full names of specific International Governmental Organizations and International Non-TGovernmental Organizations; 4. In the context of implementing the PDP Recommendations in the Next Round Applicant Guidebook, the implementation staff and the Implementation Review Team (IRT) discussed potential alternatives for the implementation of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP (“the Applicable Recommendations”), the so-called “Options 1 and 2” as set out in the staff briefing [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> but could not reach agreement on which option properly reflects the intent and scope of the protections afforded by the Applicable Recommendations. 5. On 15 September 2025 staff referred this matter to the GNSO Council for guidance on the interpretation of the Applicable Recommendations, as a late addition to the agenda of the GNSO Council meeting on 18 September 2025. 6. On 16 September 2025, the ICANN Board sent correspondence<https://www.icann.org/en/system/files/correspondence/sinha-to-samme-nlar-am…> to the GNSO Council, providing the Board’s interpretation of the relevant recommendations, while acknowledging that the decision resides with the Council; 7. The Council had a preliminary discussion on the request for guidance during its meeting on 18 September; 8. The Council scheduled an Extraordinary Meeting on 9 October 2025, to progress the issue; and, 9. The Council has now carefully considered the natural meaning and original intent of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP. Resolved: 1. The GNSO Council confirms that the intent of the relevant recommendations is to ensure not only that no organization other than the relevant organization can apply for the exact match of the specific, protected identifier associated with that organization, but also that any visually-confusingly similar string applied for by an applicant other than the protected organization would not be delegated. String Similarity Review should be conducted against the relevant identifiers. An applicant whose string is determined to be confusingly similar to a protected identifier in the String Similarity evaluation could challenge that determination, where applicable, in the usual manner. Objection proceedings and GAC Advice are still possible. Option 2 would align with this interpretation. 2. The GNSO Council requests that its liaisons to the SubPro IRT provide this information to the implementation staff and IRT. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> Option 3 has been withdrawn by both Anne Aikman-Scalese & Lawrence Olawale-Roberts Council Confirmation of Policy Intent regarding Specific IGO/INGO PDP Recommendations Submitted By: Anne Aikman-Scalese Seconded By: Lawrence Olawale-Roberts Whereas: 1. In November 2013, the Working Group for the Protection of International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) in All gTLDs completed a Policy Development Process (PDP) and submitted its Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/issues/igo-ingo-final-…> to the GNSO Council; 2. On 20 November 2013, the GNSO Council approved [gnso.icann.org]<https://urldefense.com/v3/__http:/gnso.icann.org/en/council/resolutions*201…> all the consensus recommendations in the PDP Final Report; 3. On 30 April 2014, the ICANN Board approved<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> those of the GNSO’s consensus recommendations that were not inconsistent with advice received from the Governmental Advisory Committee (GAC) on the topic of IGO and INGO protections, which recommended top-level protections for specific identifiers associated with the Red Cross Red Crescent Movement and the International Olympic Committee and the full names of specific International Governmental Organizations and International Non-TGovernmental Organizations; 4. In the context of implementing the PDP Recommendations in the Next Round Applicant Guidebook, the implementation staff and the Implementation Review Team (IRT) discussed potential alternatives for the implementation of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP (“the Applicable Recommendations”), the so-called “Options 1 and 2” as set out in the staff briefing [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> but could not reach agreement on which option properly reflects the intent and scope of the protections afforded by the Applicable Recommendations. 5. On 15 September 2025 staff referred this matter to the GNSO Council for guidance on the interpretation of the Applicable Recommendations, as a late addition to the agenda of the GNSO Council meeting on 18 September 2025. 6. On 16 September 2025, the ICANN Board sent correspondence<https://www.icann.org/en/system/files/correspondence/sinha-to-samme-nlar-am…> to the GNSO Council, providing the Board’s interpretation of the relevant recommendations, while acknowledging that the decision resides with the Council; 7. The Council had a preliminary discussion on the request for guidance during its meeting on 18 September; 8. The Council scheduled an Extraordinary Meeting on 9 October 2025, to progress the issue; and, 9. The Council has now carefully considered the natural meaning and original intent of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP. Resolved: 1. The GNSO Council confirms that both Options 1 and 2 offered by ICANN Staff are consistent with policy. While the Council reserves its right to instruct an IRT on the proper implementation of Council and Board-adopted PDP Recommendations, the Council has determined, based on correspondence from the Board and in light of pressing time deadlines, that the IRT should refer adoption of Option 1 or Option 2 to a determination to be made by the ICANN Board. By this action, the Council does not waive its procedures relating to resolution of issues in implementation at the Council level when raised by the IRT, the Council liaison(s), or ICANN Implementation Staff. 2. The GNSO Council requests that its liaisons to the SubPro IRT provide this information to the implementation staff and IRT. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> Option 4: **Updated with friendly amendment proposed by Susan Payne and accepted by Susan Payne and Nacho Amadoz on 13 November 2025 Council Confirmation of Policy Intent regarding Specific IGO/INGO PDP Recommendations Submitted By: Susan Payne Seconded By: Nacho Amadoz Whereas: 1. In November 2013, the Working Group for the Protection of International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) in All gTLDs completed a Policy Development Process (PDP) and submitted its Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/issues/igo-ingo-final-…> to the GNSO Council; 2. On 20 November 2013, the GNSO Council approved [gnso.icann.org]<https://urldefense.com/v3/__http:/gnso.icann.org/en/council/resolutions*201…> all the consensus recommendations in the PDP Final Report; 3. On 30 April 2014, the ICANN Board approved<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> those of the GNSO’s consensus recommendations that were not inconsistent with advice received from the Governmental Advisory Committee (GAC) on the topic of IGO and INGO protections, which recommended top-level protections for specific identifiers associated with the Red Cross Red Crescent Movement and the International Olympic Committee and the full names of specific International Governmental Organizations and International Non-Governmental Organizations “the protected organizations”); 4. In the context of implementing the PDP Recommendations in the Next Round Applicant Guidebook, the implementation staff and the Implementation Review Team (IRT) discussed potential alternatives for the implementation of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP (“the Applicable Recommendations”), the so-called “Options 1 and 2” as set out in the staff briefing [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> but could not reach agreement on which option properly reflects the intent and scope of the protections afforded by the Applicable Recommendations. 5. On 15 September 2025 staff referred this matter to the GNSO Council for guidance on the interpretation of the Applicable Recommendations, as a late addition to the agenda of the GNSO Council meeting on 18 September 2025. 6. On 16 September 2025, the ICANN Board sent correspondence<https://www.icann.org/en/system/files/correspondence/sinha-to-samme-nlar-am…> to the GNSO Council, providing the Board’s interpretation of the relevant recommendations, while acknowledging that the decision resides with the Council; 7. The Council discussed the request for guidance during its meeting on 18 September, Extraordinary Meeting on 9 October 2025, and meeting on 29October 2025; and, 8. The Council has now carefully considered the natural meaning and original intent of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP. Resolved: 1. The GNSO Council confirms that the intent of the Applicable Recommendations is only to ensure that no organization other than the protected organization can apply for the exact match of the specific, protected identifier associated with that organization, and that as such, Reserved Name strings are now placed in the category formerly-termed “ineligible for delegation” under paragraph 2.2.1.2.3 of the 2012 Round AGB. Accordingly, the relevant identifiers shall not be included in the String Similarity Evaluation in the New gTLD Program and such a relevant identifier shall not operate as a bar to an application by another applicant for a string that could be considered potentially confusingly similar during that evaluation. Objection proceedings and GAC Advice could still be brought against such a third-party application, where applicable, in the usual manner. Pursuant to existing policy, any application submitted by a protected organization for its protected string would remain subject to existing policy barring delegation if such string is found to be visually-confusingly similar to a string previously delegated. Option 1 would align with this interpretation. 2. The GNSO Council acknowledges that this was a difficult issue. Although the majority support this interpretation as best reflecting the intent of the policy recommendations, which were made more than a decade ago, this view was not unanimous. It is clear that reasonable people can differ as to this intent. 3. The GNSO appreciates the Board’s consideration of steps which could be taken to ensure that the protected organizations and GAC are made aware, if any application for a confusingly similar string were to be submitted, as set out in the penultimate paragraph of the Board’s letter <https://www.icann.org/en/system/files/correspondence/sinha-to-samme-nlar-am…> of 26 September 2025. The GNSO Council would support and encourage the following steps: a) The application process must prominently display and clearly communicate the Reserved Names list so that TLD applicants are fully aware of its existence and implications prior to filing its choice of the TLD string. b) That Org should contact the relevant protected organizations after String Confirmation Day to ensure they are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, and are aware of their options for bringing formal Objection or seeking support of the GAC. c) That Org should also contact the GAC after String Confirmation Day to ensure that the GAC are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, in order that GAC members may consider whether any Early Warning(s) or GAC Consensus Advice would be appropriate. d) We also would encourage the GAC to contact the relevant protected organizations to ensure that they are aware of any applied-for strings and can decide whether to utilize any challenge methods outlined in the AGB. e) That Org should also notify the applicant of the confusingly similar string, and give them the option to withdraw for an appropriate refund. f) The GNSO Council notes that procedures exist under the AGB and ICANN Bylaws that govern how a TLD application is treated, where an objection is filed or GAC advice is submitted against the string, pending resolution of the same. g) ) The GNSO Council further recommends that the IRT and Org consider including a provision in the reserved names section of the AGB advising potential applicants that ICANN will notify the GAC and the relevant protected organizations to ensure they are aware of any relevant applied-for strings. 1. If the Board considers it timely for the existing policy to be reviewed, the GNSO Council would invite the Board to request an issues report for further potential policy work which might apply to subsequent future rounds. The GNSO Council assumes that Org would again be instructed to take any steps considered appropriate to safeguard the strings on the Reserved Names List from any confusingly similar applications, which might be submitted in any application round pending the future conclusion of such policy work. 2. The GNSO Council requests that its liaisons to the SubPro IRT provide this information to the implementation staff and IRT. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> RrSG Statement<https://gnso.icann.org/sites/default/files/policy/2025/presentation/rrsg-st…> Motion to commemorate Rubens Kuhl Proposed: Jennifer Chung Seconded: All members of the GNSO Council The Council was informed earlier this month of Rubens Kuhl’s passing. We wish to recognize Rubens' significant contribution to the GNSO and the ICANN multi-stakeholder model during his tenure, as well as his professionalism, his friendship and mentorship to many. He will be greatly missed. Whereas: 1. Rubens Kuhl joined the GNSO Council on 21 October 2015 as an elected representative of the Registries Stakeholder Group from the LAC Region. He served 2 full terms between 2015 and 2019. 2. As GNSO Councilor, Rubens brought his professionalism, his deep knowledge of the GNSO Council’s best practices and history, his experienced thoughts on topics, to serve the Registries he represented as well as Council as a whole. 3. Rubens made significant contributions to ICANN and was a strong and respected community participant. During his tenure Rubens participated in: * Activities as Councilor that initiated the EPDP on the Temporary Specification * GNSO Guidance Process (GGP) Initiation Request - Select SubPro Topics (Applicant Support) team. * IDNs Small team * Modifications to GNSO Operating Procedures Relating to Elections and Motions * GNSO Council liaison - Translation & Transliteration of gTLD Registration Data IRT * Discussion Group (DG) - New gTLD Subsequent Procedures * Next-Generation gTLD Registration Directory Services to Replace Whois * New gTLD Subsequent procedures - Work Track 1, Work Track 4 as Co-Leader, Sub Group B, Sub Group C * IDN Scoping Team Rubens was also an active and valuable member of many ICANN initiatives, outside of his service to the GNSO Council, including but not limited to: * Activities as Community participant * EPDP Phase I and its IRT * Registration Data Policy Implementation IRT + IPT * GeoTLDs - .rio * ccTLDs - .br, and many Brazilian city campaigns at the second level * Latin American and Caribbean Islands Regional At-Large Organization (LACRALO) * Name Collision analysis Project (NCAP) * New gTLD Applicant Group (NTAG) Executive Committee - Vice Chair * Chairing Skills Program (CSP) * ccNSO IDN Policies Preliminary Review Team (IDN PRT) * RSP Sub-Track * Subsequent Procedures Implementation Review and ASP Sub-Track * EPDP on the Temporary Specification for gTLD Registration Data Drafting Team * gTLD Marketplace Health Index Advisory Panel * Enhancing ICANN Accountability - Work Stream 2 * New gTLD Subsequent procedures 1. Rubens was a well-respected and much appreciated member of not only the GNSO, the CPH and the Registries, but of the broader ICANN Community. He was a friend and quiet mentor to many who are able to trace back when they first encountered him. 2. Rubens was also an active member of the community of ICANN participants within the LAC region and a representative of NIC.br [nic.br]<https://urldefense.com/v3/__http:/nic.br__;!!PtGJab4!-VVghCopcwqNJT8J37bXlV…>, able to both share the dynamics of the ICANN Community to his region and a Latin American perspective to the ICANN discussion. 3. Rubens’ passing is a great loss to the many people across the ICANN community who had the pleasure to work and interact with him, and for his many friends at ICANN the loss is significant. 4. In addition to this devotion and set of accomplishments, Rubens endeared himself to those in the community by his willingness to help others and give unselfishly of his time to teach and mentor others. His work is missed but he is missed more. Resolved: 1. The GNSO Council wishes to recognize the significant contribution Rubens Kuhl made to the GNSO Council and the ICANN Community during his tenure and his achievements during this time. 2. Rubens’ presence, professionalism and commitment to the ICANN Community will be dearly missed. 3. On behalf of the current and previous GNSO Councils represented today, we offer our deepest and heartfelt sympathies to his family and friends at this most difficult time. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…>

1 0

PPSAI IRT Answers to Threshold Questions from Council
by Susan Payne Nov. 13, 2025

Nov. 13, 2025

Dear Jason, In response to your request, as PPSAI Project Manager, to Council on 1 August 2025 concerning the Privacy and Proxy Services Accreditation Issues (PPSAI) Threshold Questions (TQ), please find the attached responses from Council. The PPSAI Small Team, chaired by Paul McGrady worked diligently to provide helpful and consensus-driven responses, which were presented at the ICANN84 GNSO Council meeting and amended to updated language for TQ B. Having received no objections from Councilors by the deadline, I am pleased to send these responses on the PPSAI TQs from the GNSO Council to ICANN org and the PPSAI IRT. We look forward to the updates from our new Council Liaison to the PPSAI IRT, Ashley Heineman. Thank you, Susan Payne GNSO Council Chair ________________________________ 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>

1 0

Recordings | GNSO Council Meeting | Thursday, 13 November 2025
by Terri Agnew Nov. 13, 2025

Nov. 13, 2025

Dear all, Please find below the audio and zoom recordings of the GNSO Council Meeting that took place on Thursday, 13 November 2025. Audio only: https://icann.zoom.us/rec/play/jvbmdfqZLuapu_zGK7g8AlN6BR2FkYv87oNJz1WcS5ep… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/VPXI_ZiuNQT1eZ726s4EY9Ip8Es7IcJUSJf3bmrdWOm… 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

FW: [Ext] NEXT WEEK: Advancing the ICANN Reviews Conversation: Join the Cross Community Group Webinars
by Julie Bisland Nov. 13, 2025

Nov. 13, 2025

FYI: From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, November 13, 2025 at 11:04 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEXT WEEK: Advancing the ICANN Reviews Conversation: Join the Cross Community Group Webinars [https://danh45uab.cc.rs6.net/on.jsp?ca=c14e0464-495b-4431-9c75-53414e178223…] Thursday, 13 November 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=0018CWllR2…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> 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: ICANN86 Fellowship Application Round Now Open Webinars · NEXT WEEK: Advancing the ICANN Reviews Conversation: Join the Cross Community Group Webinars Next Round · ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics · Next Round Champions Toolkit Available in the Six ICANN Languages · Call for ASP Mentors 🚨 Action Items 🚨 · NEXT WEEK: Call for Expressions of Interest for the ICANN Director Nominated by At-Large · NEXT WEEK: Call for Nominations: 2026 ICANN Leadership Program · Updated: ICANN Issues Call for UA Day 2026 Proposals · ICANN Community Excellence Award: Now Accepting Nominations · ICANN Request for Proposal: Evaluator Panels for String Similarity and Variant Strings for the new gTLD Program: 2026 Round · ICANN Request for Proposal: New gTLD Program: 2026 Round Background Screening Services · ICANNWiki Seeking Volunteers Public Comment · CLOSES MONDAY: Proposed Next Round Base gTLD Registry Agreement - Public Comment 2 of 2 · Draft LAC Regional Strategic Plan for Fiscal Years 2026–2030 · ICANN Public Meeting Proposed Dates for 2029–2033 · String Similarity Evaluation Data for New gTLD Program: Next Round · Registration Data Request Service (RDRS) Policy Alignment Analysis · Timeline for Urgent Requests for Lawful Disclosure of Nonpublic Registration Data · Name Collision IPv6 Research Study Events · These events occur in November 2025. Information Sharing NEW: ICANN86 Fellowship Application Round Now Open Only those who have successfully completed an ICANN Fellowship Program (Fellowship Program Alumni) are eligible to apply for a Policy Forum fellowship. DEADLINE: 10 December 2025 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Webinars NEXT WEEK: Advancing the ICANN Reviews Conversation: Join the Cross Community Group Webinars All community members – including those new to ICANN Reviews – are encouraged to attend by registering for one, or both, of the sessions: Tuesday, 18 November, at 06:00 UTC Tuesday, 18 November, at 18:00 UTC Read more and register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Next Round ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics ICANN org is developing supplemental, complementary materials to aid prospective generic top-level domain (gTLD) applicants in understanding the Next Round application requirements, and how to navigate the application and evaluation processes. Blog [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> 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=0018CWllR2…>. 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>. 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=0018CWllR2…>. 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=0018CWllR2…> 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>. Action Items NEXT WEEK: Call for Expressions of Interest for the ICANN Director Nominated by At-Large On behalf of the At-Large Advisory Committee (ALAC) Board Candidate Evaluation Committee (BCEC), the At-Large Community is seeking Expressions of Interest (EoIs) from individuals who wish to serve as an ICANN Board Director. The nominated candidate will serve a three-year term starting at the end of ICANN87, which is currently scheduled for 17–22 October 2026. DEADLINE: Friday, 21 November 2025 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> NEXT WEEK: Call for Nominations: 2026 ICANN Leadership Program From 30 September – 21 November 2024, ICANN will issue a call for nominations for the 2026 Leadership Program, scheduled for 5 – 6 March in Mumbai, India, just before the ICANN85 Public Meeting. Current and incoming community leaders interested in participating in the program need to be endorsed by their Supporting Organization, Advisory Committee, or stakeholder group chairs. The ICANN organization will reach out to the respective chairs for nominations and a registration link will be sent directly to individuals who are nominated. The Leadership Program does not provide financial support for travel to Mumbai, but does cover accommodations and offer a stipend for the days a participant is involved in the program. Questions may be sent to Fernanda Iunes at fernanda.iunes(a)icann.org. Announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Updated: ICANN Issues Call for UA Day 2026 Proposals The deadline to submit a proposal has been extended from 9 November 2025 to 24 November 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> ICANN Community Excellence Award: Now Accepting Nominations The Community Excellence Award recognizes ICANN community members who have deeply invested in consensus-based solutions and contributed substantively to the ICANN multistakeholder model. DEADLINE: 8 January 2026 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> ICANN Request for Proposal: New gTLD Program: 2026 Round Background Screening Services Its purpose is to safeguard registrants and the public interest by ensuring that corporations, organizations, and institutions are in good standing and eligible to operate a gTLD. DEADLINE: 23:59 UTC on 16 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> ICANN Request for Proposal: Evaluator Panels for String Similarity and Variant Strings for the new gTLD Program: 2026 Round The selected provider(s) will also be required to collaborate with ICANN on the development of evaluation guides for the work conducted by the panels, ensuring that the evaluation processes are transparent, consistent, and repeatable across all gTLD applications. DEADLINE: 23:59 UTC on 16 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> 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=0018CWllR2…>. 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=0018CWllR2…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…>source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> on where to find reliable data. Happy editing! Public Comment CLOSES MONDAY: Proposed Next Round Base gTLD Registry Agreement - Public Comment 2 of 2 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Submissions Opening Date: Tuesday, 30 September 2025 Submissions Closing Date: Monday, 17 November 2025 Draft LAC Regional Strategic Plan for Fiscal Years 2026–2030 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Submissions Opening Date: Thursday, 9 October 2025 Submissions Closing Date: Monday, 24 November 2025 ICANN Public Meeting Proposed Dates for 2029–2033 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Submissions Opening Date: Monday, 13 October 2025 Submissions Closing Date: Monday, 1 December 2025 String Similarity Evaluation Data for New gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Submissions Opening Date: Thursday, 16 October 2025 Submissions Closing Date: Thursday, 4 December 2025 Registration Data Request Service (RDRS) Policy Alignment Analysis [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Submissions Opening Date: Thursday, 30 October 2025 Submissions Closing Date: Tuesday, 9 December 2025 Timeline for Urgent Requests for Lawful Disclosure of Nonpublic Registration Data [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Submissions Opening Date: Wednesday, 22 October 2025 Submissions Closing Date: Monday, 15 December 2025 Name Collision IPv6 Research Study [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> Submissions Opening Date: Monday, 20 October 2025 Submissions Closing Date: Monday, 22 December 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…>. Events These events occur in November 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=0018CWllR2…>. · Training for Fresh Graduates and Women in ICT-Oman 2025 · 2025 Canadian Internet Governance Forum · Seminar on the New gTLD Program: Next Round - Pakistan 2025 · 2025 Youth IGF Canada · Local APIGA 2025 - Pakistan · CIO100 Symposium and Awards 2025 · Bitkom Intellectual Property Working Group Meeting · Engagement Evening for German Internet Community Members · Middle East Network Operators Group 2025 (MENOG'25) Volume 7, Issue 82 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…> | Next Issue: Monday, 17 November 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0018CWllR2…>

1 0