October 2025 - council - lists.icann.org

IGO/INGO Integration of Policy into AGB - Possible
by Anne ICANN Oct. 11, 2025

Oct. 11, 2025

Hi Jen, Thomas, and Nacho, At the end of our Council Meeting, yesterday, some of you proposed a reworded Option 3 that might operate as a fourth alternative in the form of a friendly amendment to be included in an upcoming vote. Have any of you given thought to changes that might be agreeable to move this forward? Another possibility might be: Council confirms that a majority of Council and IRT members believe that only Option 1 is consistent with the approved IGO/INGO Policy Recommendations. However, in the course of creating the Exception for delegation of the protected strings, the Council instructs the IRT to consider that such protected string would likewise itself not be subject to string similarity review whenever applied for. Thus, the protected string would not be barred by that review if application is made by the relevant entity concurrently with or subsequent to a visually confusingly similar application by a third party. In other words, the protected strings may co-exist with visually similar strings without requiring auction procedures and without barring either string from delegation. Objections and GAC Advice would still be available, as usual. After due consideration, the Council confirms that the foregoing implementation best reflects the intent of the IGO/INGO policy Recommendations in that no String Similarity Review occurs as to such strings at any time. Any thoughts on this one? It's similar to an option proposed at the IRT level. It was thought to require further policy work but after the discussion yesterday, I'm not sure that's the case. Wouldn't it be an extension of the principle that No String Similarity Review applies to these strings and that a proper exception is being created for delegation as provided by the IGO/INGO Recommendations? This has not gone to the full list. All ideas welcome. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.comI

3 2

Question to GAC
by farzaneh badii Oct. 9, 2025

Oct. 9, 2025

Hello Council I am suggesting that during our GAC meeting we ask this question: "As human rights are a foundational part of our work, no policy development process is complete without an assessment of its potential human rights implications. GAC colleagues, could you share how you are operationalizing this commitment in your work (communiqués and other aspects?) We’d be very interested to learn from your approach as we need to undertake the HRIA that will have to happen on every pdp moving forward" Please let us know soon if you have any objections. Farzaneh

10 14

FW: [Ext] NEW: ICANN Extends Deadline for Applicant Support Program
by Julie Bisland Oct. 9, 2025

Oct. 9, 2025

FYI-- From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, October 9, 2025 at 10:04 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: ICANN Extends Deadline for Applicant Support Program [https://danh45uab.cc.rs6.net/on.jsp?ca=bd6fc5a2-7162-4072-a553-2ca663ec17d8…] Thursday, 09 October 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=001BQQsgvN…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> 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 ICANN84 · ICANN84 Schedule · Prep Week Schedule · FAQ's · ICANN84 Time Change Notice Information Sharing · NEW: ICANN Extends Deadline for Applicant Support Program · NEW: The Latest New gTLD Program Achievements · NEW: As the Internet Evolves, ICANN Remains Focused on its Security and Stability · NEW: ICANN Issues Call for UA Day 2026 Proposals · NEW: SSAC 2025 Annual Workshop in Review 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: ICANN Generic Names Supporting Organization Calls for Volunteers for SPIRT · NEXT WEEK: ICANN Request for Proposal: NomCom Recruiting Services · NextGen@ICANN Mentor Program Nominations · Call for Nominations: 2026 ICANN Leadership Program · ICANNWiki Seeking Volunteers Public Comment · NEW: Public Comment Summary Report: Functional Model for Root Server System Governance · NEXT WEEK: Preliminary Issue Report on a Policy Development Process on DNS Abuse Mitigation · Updated GNSO Stakeholder Group and Constituency Charter Amendment Process · Second Draft of the RIR Governance Document · Proposed Next Round Base gTLD Registry Agreement - Public Comment 2 of 2 Events · These events occur in October 2025. ICANN84 ICANN84 SCHEDULE [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> PREP WEEK SCHEDULE [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> FAQ's [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> ICANN84 Time Change Notice On Sunday, 26 October 2025 the time zone in Dublin, Ireland will change from Irish Standard Time (UTC+1) to Greenwich Mean Time, back one hour (UTC+0). Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> Information Sharing NEW: ICANN Extends Deadline for Applicant Support Program Entities that enter organizational information in the system by 19 November 2025 will now have until 19 December 2025 to submit a complete application. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> NEW: The Latest New gTLD Program Achievements With continued momentum and the collaboration with the community, we are optimistic that we will open the new gTLD application window in April 2026, as planned. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> NEW: As the Internet Evolves, ICANN Remains Focused on its Security and Stability Our remit, to ensure the security, stability, and resilience of those systems, is key to making the Internet work for the billions of people who depend on it. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> NEW: ICANN Issues Call for UA Day 2026 Proposals Event proposals are encouraged from all relevant organizations The deadline to submit a proposal is 9 November 2025. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> NEW: SSAC 2025 Annual Workshop in Review The SSAC workshop enables our members to come together to plan our strategic goals and upcoming work for the year ahead. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> 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=001BQQsgvN…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> 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=001BQQsgvN…>. 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=001BQQsgvN…>. 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=001BQQsgvN…> 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: ICANN Generic Names Supporting Organization Calls for Volunteers for SPIRT In coordination with the GNSO Council, the SPIRT will collaborate with ICANN org to address all non-minor changes during the program using the Predictability Framework. Deadline: Friday, 17 October 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> NEXT WEEK: ICANN Request for Proposal: NomCom Recruiting Services By issuing this RFP, ICANN is soliciting proposals from qualified suppliers for the provision of the services to achieve this. Deadline: 17 October 2025 Announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> RFP Overview [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> NextGen@ICANN Mentor Program Nominations The NextGen@ICANN Program is seeking nominations for three (3) positions in the 2026 Mentor Program. These mentors will guide the NextGen participants through the mentorship process during the ICANN85-87 meetings. ICANN will provide travel funding for the appointed mentors to attend these meetings. Each Supporting Organization (SO) and Advisory Committee (AC) is invited to nominate one individual for a total of three spots. Nominations can include program alumni, and we encourage the selection of active community members who are passionate about mentoring students. SOs and ACs can also choose to renominate previous mentors. Please note that individual self-nominations will not be accepted. All nominations must be submitted by Friday, 7 November 2025 to Fernanda Iunes at fernanda.iunes(a)icann.org. If we receive nominations from more than three SOs/ACs, they will be accepted on a first come, first served basis, but ICANN org will prioritize groups that have not had mentors in the past. 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=001BQQsgvN…> 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=001BQQsgvN…>. 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=001BQQsgvN…> 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=001BQQsgvN…>source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> on where to find reliable data. Happy editing! Public Comment NEW: Public Comment Summary Report: Functional Model for Root Server System Governance [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> NEXT WEEK: Preliminary Issue Report on a Policy Development Process on DNS Abuse Mitigation [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> Submissions Opening Date: Monday, 08 September 2025 Submissions Closing Date: Saturday, 18 October 2025 Updated GNSO Stakeholder Group and Constituency Charter Amendment Process [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> Submissions Opening Date: Wednesday, 10 September 2025 Submissions Closing Date: Wednesday, 05 November 2025 Second Draft of the RIR Governance Document [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> Submissions Opening Date: Thursday, 28 August 2025 Submissions Closing Date: Friday, 07 November 2025 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=001BQQsgvN…> Submissions Opening Date: Tuesday, 30 September 2025 Submissions Closing Date: Monday, 17 November 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…>. Events These events occur in October 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=001BQQsgvN…>. · Training for Fresh Graduates and Women in ICT-Oman 2025 · DNSSEC Workshop Morocco 2025 · Baltic Domain Days · Finnish Internet Forum · Netnod Tech Meeting 2025 · Public Interest Technology Career Summit · Internet Measurement Day - Tunisia 2025 · LA Tech Week - A Piece of the Internet to Realize Your Vision · Technical Training Tunisia 2025 · Tech Policy Week - CITRIS · Domain Days Dubai 2025 Volume 7, Issue 75 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…> | Next Issue: Monday, 13 October 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001BQQsgvN…>

1 0

Recordings | Extraordinary GNSO Council Meeting | Thursday, 09 October 2025
by Terri Agnew Oct. 9, 2025

Oct. 9, 2025

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

The ALAC's position on the protection of IGO/INGO Identifiers
by Justine Chew Oct. 9, 2025

Oct. 9, 2025

Dear Councilors, As mentioned on the call just ended, I have instructions from the ALAC to forward to Council, its position on the issue of protection of IGO/INGO Identifiers. The full version is attached by way of letter, and the shorter version is as follows. The At-Large Advisory Committee (ALAC) wishes to convey its position on this issue of protection of IGO/INGO Identifiers. After having considered the available information, the ALAC stands with the position expressed by the ICANN Board, the IGO/INGO Group spokesperson Brian Beckham and several SubPro IRT members in favouring Option 2 of including the IGO/INGO Identifiers in String Similarity Review. In supporting Option 2, the ALAC places predominance on the following: 1. Firstly, the ALAC recognizes and supports the role of the String Similarity Review (SSR) in helping to mitigate unacceptable risk of end-user confusion and loss of confidence in the DNS due to visually confusingly similar strings being delegated into the Root Zone. This goal should neither be taken lightly nor undermined. Given the status and functions of those IGOs/INGOs in globally advocating for issues and people outside of government, allowing a third party applicant to potentially secure a string that is confusingly similar to a protected IGO/INGO Identifier would not serve the public interest, as it is conceivable that this could lead to bad actors exploiting end-user confusion vulnerabilities to perpetrate harm “in the name of an IGO/INGO”. 2. The ALAC views the inclusion of IGO/INGO Identifiers in SSR, per Option 2, not as an ‘expansion of rights beyond those exact matches of those IGO/INGO Identifiers’ but as the appropriate mechanism to preserve the ability for an IGO/INGO to apply for its relevant identifier if and when it chooses to, as was intended by the relevant policy recommendations from the IGO-INGO PDP. It is inconceivable to the ALAC that policy which exists to protect those IGO/INGO Identifiers for application by their respective IGO/INGO could then be displaced by an unreasonably strict interpretation of policy recommendation text or absence of specific policy recommendation text said to be required to allow implementation by way of Option 2. No policy recommendation exists to suggest that the ability for an IGO/INGO to apply for its protected IGO/INGO Identifier would be encumbered or blocked by a confusingly similar string; or that an IGO/INGO must promptly apply for its IGO/INGO Identifier in order to avoid being blocked by a confusingly similar string/TLD in the next round or future application opportunities. Therefore, *the ALAC urges the GNSO Council to place public interest considerations towards the mitigation of risk of end-user confusion and loss of confidence in the DNS above the call for the strict interpretation of policy recommendation text expressed in Option 1.* *The ALAC would also be supportive of the Third Resolved Clause Option wherein the GNSO Council agrees to instruct the SubPro IRT to refer the issue to the ICANN Board for a decision.* ***** And I would like to reiterate that we should also consider the input from Brian Beckham on behalf of the IGO/INGO group, and whose Identifiers are the very subject of this issue. Kind regards, *Justine Chew* At-Large Advisory Committee (ALAC) Liaison to the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) At-Large website: https://atlarge.icann.org/ ------

1 0

**Starting in 15 minutes | Meeting Invitation | Extraordinary GNSO Council meeting | Thursday, 09 October 2025
by Terri Agnew Oct. 9, 2025

Oct. 9, 2025

**Starting in 15 minutes Dear all, The Extraordinary GNSO Council meeting is scheduled on Thursday, 09 October 2025 at 13:00 UTC for 60 minutes. 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/i4CTHQ Check your time zone: https://tinyurl.com/vjvhe8w4 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Passcode: mkt7*ULa9b If joining Zoom via Zoom App the following will be required: Webinar ID: 910 4823 5847 Passcode: 9213420189 Or One tap mobile : +13462487799,,91048235847#,,,,*9213420189# US (Houston) +16699006833,,91048235847#,,,,*9213420189# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/a6JrPP2u5 Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://icann-community.atlassian.net/wiki/x/aACSHQ> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

NCSG’s position on IGO/INGO issue
by farzaneh badii Oct. 9, 2025

Oct. 9, 2025

Hello, Please find our position in advance of the call. NCSG has maintained a consistent position on IGO/INGO and Red Cross protections from 2012 to the present. In 2012, the NCSG Policy Committee opposed the introduction of special reserved-name protections for the IOC and Red Cross. We argued that there was no transparent legal basis for such protections, that creating them would set a precedent for endless additions to a finite list, and that any further consideration should occur through a proper Policy Development Process (PDP) in future rounds, not through ad-hoc amendments to the Applicant Guidebook. See *NCSG Policy Committee Statement on Proposal to Protect Names of the International Federation of the Red Cross and the International Olympic Committee* (23 March 2012): https://gnso.icann.org/sites/default/files/file/field-file-attach/reconvene… In 2018, when the convened IGO/INGO Working Group and Red Cross group expanded these protections to hundreds of national society names (at the second level), the NCSG reiterated its concern. Our statement recorded *“grave concern regarding the move toward reserving names and their alteration by broad interpretation of national laws and conventions in domain-name space.”* We cautioned that this practice, even if well-intentioned, undermines due process, invites unverified legal justifications, and risks turning the domain-name system into an instrument for exceptional privileges. The transcript of the GNSO Council meeting of 27 September 2018 further reflects the NCSG’s position and rationale for opposing the expansion of reserved names: https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip… It is worth mentioning however that the NewgTLDs subsequent procedure did not mention any way to reserve IGOs and INGOs names. So we again ended up in a situation when PDP didn't address the issue. The current 2025 GNSO Council discussion again raises the same issue in the form “implementation options.” NCSG finds the framing of these options by the Implementation Review Team (IRT) itself problematic. The IRT’s mandate is to implement existing GNSO policy faithfully, not to present new policy directions for the Council to select from. By introducing “Option 2,” the IRT (staff) has effectively reopened a settled policy question and blurred the line between implementation and policymaking. Option 2 represents a significant expansion of protections by inserting these identifiers into the String Similarity evaluation, creating new barriers for applicants and turning reserved names into a broad blocking mechanism—something never approved through the GNSO policy process. NCSG supports Option 1 as the only correct implementation path. Option 1 is fully consistent with existing GNSO policy. It correctly ensures that the relevant identifiers are reserved solely for the corresponding entities while allowing confusingly similar strings to be handled under the standard String Similarity Review and objection procedures. This preserves the original limited intent and respects the boundaries of prior Council decisions. We also recommend that the IRT and staff revise its approach in future work. The practice of presenting “options” that include policy changes should cease, as it creates confusion, politicizes the implementation process, and risks undermining the GNSO’s policy making authority. If the IRT identifies ambiguity or disagreement about policy scope, the proper course of action is to refer the matter back to the GNSO Council for clarification, not to create new “options” that effectively rewrite or expand the underlying policy. For these reasons, NCSG supports Option 1, rejects Option 2 as a policy overreach, and urges the IRT and Staff to adhere strictly to the implementation role and avoid framing policy questions as implementation choices. Farzaneh

1 0

Fwd: [gnso-chairs] Invitation - RSVP - ICANN Leadership Program (LP) 2026
by Tomslin Samme-Nlar Oct. 9, 2025

Oct. 9, 2025

Dear Council Colleagues, We received the below invitation to the ICANN Leadership Program (LP) 2026. This is the program we sent Manju Chen, Mark Datysgeld and Jennifer Chung in the past. If you are interested please reach out to them for all the insider details. We are allowed one candidate for the GNSO Council. We will also be alerting incoming Councilors. Given that this single seat open for Council is for a 2-day event, the organizers are also asking us to nominate an alternate, all by 21 November. Remain blessed, Tomslin ---------- Forwarded message --------- From: Fernanda Iunes via Gnso-chairs <gnso-chairs(a)icann.org> Date: Wed, 1 Oct 2025 at 01:36 Subject: [gnso-chairs] Invitation - RSVP - ICANN Leadership Program (LP) 2026 To: gnso-chairs(a)icann.org <gnso-chairs(a)icann.org> Cc: Sandra Hoferichter <info(a)hoferichter.eu>, Ergys Ramaj < ergys.ramaj(a)icann.org> Dear Nacho and Tomslin, After a one-year hiatus, the ICANN Academy Leadership Program (LP) is back and we are preparing for its 9th edition, scheduled to take place from 5–6 March 2026, two days before the official start of ICANN85 in Mumbai, India. For this program, one seat is reserved for a representative from the GNSO Council. The program is designed for current *and *incoming leaders, helping to increase understanding of the complexity of ICANN and to develop facilitation skills, as well as building a network with other leaders. We are aware that understanding ICANN as an organization, the topics discussed within ICANN, and interaction within other stakeholder groups can be challenging for incoming leaders, but sometimes also for experienced leaders. ICANN and the community are making considerable efforts to help incoming leaders have a good start to their terms and to provide current leaders the opportunity to strengthen their leadership and facilitation skills. Opportunities for Leadership Program participants include the following: - Connect with leaders from the other SOs/ACs and get an insight of the functionality and issues in other groups - Discuss current ICANN topics in-depth - Deepen the understanding of ICANN processes - Develop facilitation and leadership skills, focused personal effectiveness to run meetings and foster processes A preliminary agenda is attached to this email. Kindly note that this is subject to change. Accommodation for participants will be covered between Wednesday and Thursday, 4-5 March 2026, and participants will receive a stipend. Please note that flights will *NOT* be covered under this program, as incoming and current leaders are normally already covered. Please ensure that the leaders that are nominated for your group are being covered by ICANN Travel Support (or by other means) for their flights to Mumbai for ICANN85. We would like to ask you to identify one incoming or current leader from your stakeholder group who is interested and available to participate in this program. We recommend that you also identify an alternate candidate. All candidates should be able to participate in the full program. *Kindly forward us the names and email addresses of the endorsed individuals no later than Friday, 21 November 2025, and ask them to register **here* <https://forms.gle/X2MoCPAT8u4YB2RUA>* by Monday, 24 November 2025.* We hope this program will meet the needs of your community. All participants will be encouraged to openly exchange their views under Chatham House Rules, as this will help facilitate cross-constituency collaboration during their leadership terms. We are happy to answer any questions you may have and look forward to having your group’s participants confirmed. Sandra Hoferichter is also available to visit your group at the upcoming ICANN84 meeting at a time that is convenient for you. She can give a short presentation on the LP and answer any questions. This should take no more than 15 minutes. Please coordinate with Sandra if this is something that would interest you and your group. Kind regards, Sandra Hoferichter, Chair of the ICANN Academy Working Group and Fernanda Iunes, ICANN Capacity Development Manager _______________________________________________ Gnso-chairs mailing list -- gnso-chairs(a)icann.org To unsubscribe send an email to gnso-chairs-leave(a)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

Board reversal of a previously adopted policy Recommendation
by Anne ICANN Oct. 8, 2025

Oct. 8, 2025

Dear Councilors, If we reach the subject topic in the October 9 meeting, I would like to highlight a change I requested in the Google doc in relation to the Board reversal of a previously adopted policy recommendation. The current draft says: In limited circumstances, where the ICANN Board has adopted a GNSO policy recommendation and where that recommendation has not yet concluded its implementation, the Board may need to reverse its adoption of the GNSO policy recommendation. In this circumstance, the Board may adhere to the process below. Prior to taking such action, the Board should make all reasonable efforts to engage in dialogue with the GNSO Council to, at a minimum, (i) communicate its intentions to reverse its adoption, (ii) detail the issue(s), (iii) provide rationale for the intended action, and (iv) explain why reversal is the only or best option. The deletion I recommend is in red above. I don't think the Bylaws provision that deals with Board failure to adopt a GNSO approved Recommendation contains this conditional language and I thought we had a consensus that the amendment to our GNSO procedures should track that Bylaws process even if the Bylaws are not amended to make this a Bylaws requirement. The Bylaws requirement is stated in Section 9 of Annex A. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

1 0

UPDATED agenda | Proposed Agenda | Extraordinary GNSO Council | Thursday, 09 October 2025
by Terri Agnew Oct. 8, 2025

Oct. 8, 2025

Dear all, The agenda has been updated to change item 2 (New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations) from a vote to discussion and additional information added to this item. The wiki agenda page has been updated: https://icann-community.atlassian.net/wiki/x/i4CTHQ Thank you Extraordinary GNSO Council Agenda 09 October 2025 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://icann-community.atlassian.net/wiki/x/aACSHQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 15 March 2023. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 09 October 2025 at 13:00 UTC: https://tinyurl.com/vjvhe8w4 06:00 Los Angeles; 09:00 Washington DC; 14:00 London; 15:00 Paris; 16:00 Moscow; 23:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 14 August 2025 were posted on 2 September 2025. Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 18 September 2025 were posted on 02 October Item 2: COUNCIL DISCUSSION - New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations (35 minutes) During its September meeting<https://icann.zoom.us/rec/play/XYy4NN_IZZv08C-bg6V2CiZv-C_HxrwTqlFeWgVvkHfm…>, the Council discussed an issue that recently arose in the proposed implementation of the Subsequent Procedures PDP recommendations. Specifically, ICANN org staff prepared a discussion paper<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/460783617/2025…> to explain the issue and to provide a path forward. The IRT was not aligned with ICANN org’s proposal. The Council was requested to provide guidance on the intent of relevant recommendations; without this guidance, the timeline for the Board’s adoption of the Applicant Guidebook and launch of the Next Round are likely to be negatively impacted. GNSO support staff sought to identify the underlying question for the Council to consider: What does it mean for the full name identifiers to be “protected,” but available for the relevant organization via an exception procedure? Based upon discussions within the SubPro IRT, there are two interpretations: 1. Protected only means that no organization other than the relevant organization can apply for the exact match of the full name identifier. This implies that an unrelated third party could apply for a confusingly similar string, thereby preventing the relevant organization from securing their protected string in the future. 2. Or, protected means that no organization other than the relevant organization can apply for the exact match of the full name identifier AND the ability for the relevant organization to secure their protected string should persist. This implies that unrelated third parties would need to be prevented from securing confusingly similar strings (i.e., include the protected strings in string similarity). The Council has been asked to help determine whether the intent of the relevant IGO/INGO PDP recommendations are aligned with interpretation 1 or 2 above. Councilors have been asked to consult with their respective groups to help reach alignment on the original intent of the recommendations. Here, the Council will discuss the original intent of the relevant recommendations with the aim of voting on the interpretation of the original intent either via an email vote or at its upcoming meeting at ICANN84. 2.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Co-Chair) 2.2 - Council Discussion (Anne Aikman-Scalese & Susan Payne, GNSO co-liaisons to the PDP) 2.3 - Next Steps Item 3: COUNCIL DISCUSSION - Board Reversal of its Adoption of a GNSO PDP Recommendation (15 minutes) During the Council’s last Strategic Planning Session (SPS), the Council came to general agreement on an approach for the ICANN Board to reverse its adoption of a GNSO recommendation. The resulting action item was to identify the proper place to document that generally agreed upon process. On 19 August 2025<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/LOD5WHIQ6I…>, GNSO support staff sent a message to the Council, noting that support staff coordinated with ICANN legal colleagues to determine the most appropriate location to capture the process, and, following that discussion, recommended updating the EPDP, PDP, and GGP manuals. Having received no objections to this approach, GNSO Support Staff provided draft redlines for the EPDP, PDP, and GGP manuals for the Council’s consideration on 19 September 2025<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/RMMJYAX6NC…> with an accompanying request to provide comments and concerns prior to this Special Meeting. Here, the Council will discuss the proposed updates to the GNSO processes in preparation for discussing the proposal with the Board at the upcoming ICANN84 ICANN Board and GNSO Council bilateral. 3.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Co-Chair) 3.2 - Council Discussion 3.3 - Next Steps Item 4: Any Other Business (5 minutes) * None _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 13:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 06:00 San José, Costa Rica (CST) UTC-6 07:00 New York/Washington DC, USA (EDT) UTC-4 09:00 Buenos Aires, Argentina (ART) UTC-3 10:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 14:00 Paris, France (CEST) UTC+2 15:00 Moscow, Russia (MSK) UTC+3 16:00 Singapore (SGT) UTC+8 21:00 Melbourne, Australia (AEST) UTC+10 23:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/2n3uanbb From: Terri Agnew <terri.agnew(a)icann.org> Date: Monday, September 29, 2025 at 8:33 AM To: "council(a)icann.org" <council(a)icann.org>, "liaison6c(a)icann.org" <liaison6c(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: Proposed Agenda | Extraordinary GNSO Council | Thursday, 09 October 2025 Dear all, Please find below the agenda for the Extraordinary GNSO Council on 09 October 2025 at 13:00 UTC This will be posted on the agenda wiki page<https://icann-community.atlassian.net/wiki/x/i4CTHQ> shortly. Thank you. Kind regards, Terri Policy Team Supporting the GNSO Extraordinary GNSO Council Agenda 09 October 2025 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://icann-community.atlassian.net/wiki/x/aACSHQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 15 March 2023. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 09 October 2025 at 13:00 UTC: https://tinyurl.com/vjvhe8w4 06:00 Los Angeles; 09:00 Washington DC; 14:00 London; 15:00 Paris; 16:00 Moscow; 23:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 14 August 2025 were posted on 2 September 2025. Minutes of the GNSO Council Meeting on 18 September 2025 will be posted on 02 October Item 2: COUNCIL VOTE - New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations (30 minutes) During its September meeting<https://icann.zoom.us/rec/play/XYy4NN_IZZv08C-bg6V2CiZv-C_HxrwTqlFeWgVvkHfm…>, the Council discussed an issue that recently arose in the proposed implementation of the Subsequent Procedures PDP recommendations. Specifically, ICANN org staff prepared a discussion paper<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/460783617/2025…> to explain the issue and to provide a path forward. The IRT was not aligned with ICANN org’s proposal. The Council was requested to provide guidance on the intent of relevant recommendations; without this guidance, the timeline for the Board’s adoption of the Applicant Guidebook and launch of the Next Round are likely to be negatively impacted. GNSO support staff sought to identify the underlying question for the Council to consider: What does it mean for the full name identifiers to be “protected,” but available for the relevant organization via an exception procedure? Based upon discussions within the SubPro IRT, there are two interpretations: 1. Protected only means that no organization other than the relevant organization can apply for the exact match of the full name identifier. This implies that an unrelated third party could apply for a confusingly similar string, thereby preventing the relevant organization from securing their protected string in the future. 2. Or, protected means that no organization other than the relevant organization can apply for the exact match of the full name identifier AND the ability for the relevant organization to secure their protected string should persist. This implies that unrelated third parties would need to be prevented from securing confusingly similar strings (i.e., include the protected strings in string similarity). The Council has been asked to help determine whether the intent of the relevant IGO/INGO PDP recommendations are aligned with interpretation 1 or 2 above. Councilors have been asked to consult with their respective groups to help reach alignment on the original intent of the recommendations. Here, the Council will vote on its interpretation of the original intent of the relevant recommendations and to provide that guidance to the SubPro IRT. 2.1 - Introduction of Motion (Anne Aikman-Scalese & Susan Payne, GNSO co-liaisons to the PDP) 2.2 - Council Vote (threshold: simple majority of each House) 2.3 - Next Steps Item 3: COUNCIL DISCUSSION - Board Reversal of its Adoption of a GNSO PDP Recommendation (20 minutes) During the Council’s last Strategic Planning Session (SPS), the Council came to general agreement on an approach for the ICANN Board to reverse its adoption of a GNSO recommendation. The resulting action item was to identify the proper place to document that generally agreed upon process. On 19 August 2025<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/LOD5WHIQ6I…>, GNSO support staff sent a message to the Council, noting that support staff coordinated with ICANN legal colleagues to determine the most appropriate location to capture the process, and, following that discussion, recommended updating the EPDP, PDP, and GGP manuals. Having received no objections to this approach, GNSO Support Staff provided draft redlines for the EPDP, PDP, and GGP manuals for the Council’s consideration on 19 September 2025<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/RMMJYAX6NC…> with an accompanying request to provide comments and concerns prior to this Special Meeting. Here, the Council will discuss the proposed updates to the GNSO processes in preparation for discussing the proposal with the Board at the upcoming ICANN84 ICANN Board and GNSO Council bilateral. 3.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Co-Chair) 3.2 - Council Discussion 3.3 - Next Steps Item 4: Any Other Business (5 minutes) * None _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 13:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 06:00 San José, Costa Rica (CST) UTC-6 07:00 New York/Washington DC, USA (EDT) UTC-4 09:00 Buenos Aires, Argentina (ART) UTC-3 10:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 14:00 Paris, France (CEST) UTC+2 15:00 Moscow, Russia (MSK) UTC+3 16:00 Singapore (SGT) UTC+8 21:00 Melbourne, Australia (AEST) UTC+10 23:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/2n3uanbb

2 1