October 2025 - council - lists.icann.org

GNSO Council Absence Notification Form: Damon Ashcraft
by Terri Agnew Oct. 20, 2025

Oct. 20, 2025

Full Name of Officer: John McElwaine Officer Email Address: john.mcelwaine(a)nelsonmullins.com Date Prepared: 20 October 2025 GNSO Organization: Intellectual Property Constituency Officer Position or Title: Pres. Name of Absent Councilor: Damon Ashcraft Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Damon will be traveling to ICANN84 Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: GNSO Council Informal Session. Please note that it is our understanding that there are no votes. Date upon which the remedy will expire or terminate: 27 October 2025 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. No Our GNSO Councilor has been instructed on how to vote on the matter(s). No Full Name of GNSO Councilor Serving as Voting Proxy: Susan Payne By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy<https://www.icann.org/privacy/policy>, and agree to abide by the website Terms of Service<https://www.icann.org/privacy/tos>. I Agree

1 0

FW: RySG GNSO Vice Chair Selection
by Devan Reed Oct. 20, 2025

Oct. 20, 2025

Dear Councilors, Please see below the CPH’s selection for GNSO Council Vice-Chair. Thank you! Kind regards, Devan From: Elizabeth Bacon <bbacon(a)pir.org> Date: Friday, October 17, 2025 at 2:14 PM To: GNSO-Secs <gnso-secs(a)icann.org> Cc: Owen Smigelski <owen.smigelski(a)namecheap.com>, "jen(a)dot.asia" <jen(a)dot.asia>, Sue Schuler <secretariat(a)rysg.info> Subject: RySG GNSO Vice Chair Selection Hello All, In preparation for the GNSO Chair vote and subsequent announcement of GNSO Chair and Vice Chair position announcements in Dubin, in line with GNSO Operating Procedures Section 2.2.c., the Contracted Parties House has selected Jennifer Chung from the Registries Stakeholder Group to serve as Vice Chair. Please let us know if you need anything further from me. Have a great weekend. Best, Beth on behalf of the CPH Elizabeth Bacon | Chair, RySG

13 12

RESENDING | Updated GAC/GNSO Council Talking Points/Questions ICANN84
by Terri Agnew Oct. 20, 2025

Oct. 20, 2025

Hello all, Please see email below from Sebastien. **Resending, reminder to use: council(a)icann.org<mailto:council@icann.org> Do not use: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Thanks! Terri From: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy> Date: Monday, October 20, 2025 at 10:30 AM To: GNSO Council List <council(a)gnso.icann.org>, GNSO-Secs <gnso-secs(a)icann.org>, Manal Ismail <manal(a)tra.gov.eg>, "Tahir, Rida (ISED/ISDE)" <rida.tahir(a)ised-isde.gc.ca> Subject: Updated GAC/GNSO Council Talking Points/Questions ICANN84 Dear Council Colleagues, Please find below the agreed talking points for our Council / GAC bilateral next Sunday. All questions come from the GAC but for the last one which comes from us - Thank you to the NCSG for proposing it. Kindly, Seb ICANN84 GAC/GNSO Bilateral (26 October 2025) | GAC Questions/Talking Points 1. Introduction 2. RDRS • The GAC appreciated the opportunity to provide comments to the RDRS Standing Committee Council report issued in August. To increase its utility, the GAC reiterates its position that the RDRS should continue beyond the pilot and become mandatory for all gTLD registrars and optional for ccTLD operators. As already discussed during ICANN83, the GAC is concerned by the increasing number of registrars withdrawing from the pilot. • As indicated in its response to the public comment, the GAC further believes that immediate work on the RDRS should include incorporation of the solution for LEAs authentication whenever available and technical enhancements to improve the user friendliness of the tool. The GAC also agrees with the RDRS Standing Committee that work on Privacy/Proxy would be very useful but disagrees on a blanket rejection of all EPDP Phase 2/SSAD Recommendations. • The GAC would appreciate details on the GNSO’s approach towards next steps following the public comment period and particularly on the timeline and options for the future of RDRS, noting that its pilot period is rapidly coming to an end and that the public comment highlighted diverse opinions on what needs to be done within the ICANN community. 3. Urgent Requests / Law Enforcement Authentication • The GAC would like to express satisfaction for the good cooperation between all parties in the Implementation Review Team (IRT) that is tasked with establishing the timeline for urgent requests for registration data. In particular, the GAC is supportive of the current compromise text, pending public comment, that foresees a timeline of 24H with possible extension to 72H in exceptional circumstances (force majeure) • At the same time, the GAC is concerned by the latest insertion in the IRT text, which seems to imply that the authentication mechanism for law enforcement would require new policy development in order to be enshrined in Consensus Policy. As the GNSO is aware, the work to set up the authentication mechanism is already ongoing and progressing well with participation of PSWG, Contracted Parties and ICANN org. • The GAC would appreciate the perspective of the GNSO on this matter, in particular in light of the trilateral agreement between the ICANN Board, the GNSO and the GAC that set up two parallel workstreams (timeline and authentication) as part of the same implementation process of the already established Consensus Policy (EPDP Phase 1). 4. Accuracy • The GAC read with interest the conclusions of the GNSO Small Team on Accuracy and understands that the GNSO Council approved all its (four) recommendations during its meeting of August 2025. • The GAC would appreciate more details on how the GNSO Council plans to implement these recommendations and particularly Recommendation 1 of the Small Team which concerns “examining the existing process for validating and verifying registration data under the 2024 Registrar Accreditation agreement 1 and the potential impact on registrants if this process is modified”. The Small Team did not indicate nor support a specific path for implementing this recommendation although listed potential options such as “referral of the issue to the GNSO Council Small Team on DNS Abuse, further policy work via a narrow PDP, etc.” as a way forward. The GAC highlights that it is important to reduce the time for the verification of registrant contact details from its current 15-day period as abuse associated with maliciously registered domain names tends to occur very shortly after registration. Ideally, validation and verification should be done before the domain name becomes active. • Could the GNSO Council elaborate on what options are under discussion for implementing Recommendation 1 (above) as well as concerning the implementation of other recommendations from the Small Team ? 5. DNS Abuse • The GAC appreciated the work of the GNSO Small Team on DNS abuse (summarized in its final report) and the subsequent preparation from ICANN org of a preliminary issue report on a Policy Development Process on DNS abuse mitigation. The GAC welcomes that the Issue Report takes into account the latest GAC Advice to the Board on the topic of DNS Abuse. The GAC considered both documents thoroughly and submitted a response to the Public Comment proceedings highlighting some elements of importance for governments. • Following the conclusion of the public comment period, the GAC would welcome any reflection from the GNSO on the feedback received from the various communities and any update on the timeline and next steps for launching the PDP on unrestricted APIs and associated domains suggested in the Issue Report. The GAC reiterates that the organization of the upcoming PDP(s) into narrowly scoped track(s) should be conducive to effective and fast delivery of the PDP. • The GAC [as expressed in its Public Comment to be submitted by 18 October 2025] would also welcome further reflections from the GNSO Council on additional paths for addressing policy gaps of importance to the GAC, which are indicated in the GNSO Small Team final report and the Preliminary Issue Report, but which are not prioritized for the first PDP effort, such as: proactive monitoring/preventative measures, accuracy and transparency of reporting obligations. 6. AOB · 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 would be interested to learn from your approach, as we are implementing Human Rights Impact Assessments in every Policy Development Processes moving forward. Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [cid:image001.png@01DC41AD.2EACDAA0] +49 172 690 8418 Germany sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0

FW: [Ext] NEW: ICANN's Progress and Next Steps in Enforcing DNS Abuse Mitigation Requirements
by Julie Bisland Oct. 20, 2025

Oct. 20, 2025

FYI: From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, October 20, 2025 at 10:04 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: ICANN's Progress and Next Steps in Enforcing DNS Abuse Mitigation Requirements [https://danh45uab.cc.rs6.net/on.jsp?ca=a252bc60-1fc9-4472-a9d3-b179a125d538…] Monday, 20 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=0014oPkjrw…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> 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 · NEW: ICANN84 GNSO Policy Briefing · ICANN84 Schedule · FAQ's · ICANN84 Time Change Notice · Next Round Status Update · PRSP Pre-ICANN84 Briefing · Policy Outlook Report · Welcome to Dublin: A Preview of the ICANN84 Annual General Meeting · New gTLD Program: Next Round Community Briefing Sessions at ICANN84 Information Sharing · NEW: ICANN's Progress and Next Steps in Enforcing DNS Abuse Mitigation Requirements · NEW: Call for Expressions of Interest for the ICANN Director Nominated by At-Large · NEW: ICANN Seeks Input on Name Collision IPv6 Research Study 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 🚨 · DEADLINE EXTENDED: ICANN Generic Names Supporting Organization Calls for Volunteers for SPIRT · CLOSES TOMORROW: 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: Name Collision IPv6 Research Study · 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 · 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 Events · These events occur in October 2025. ICANN84 GNSO Policy Briefing [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> ICANN84 SCHEDULE [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> FAQ's [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> Next Round Status Update [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> PRSP Pre-ICANN84 Briefing [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> Policy Outlook Report [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> Welcome to Dublin: A Preview of the ICANN84 Annual General Meeting The ICANN community has taken the lead in organizing the six-day program. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> New gTLD Program: Next Round Community Briefing Sessions at ICANN84 The New gTLD Program team will provide overviews of the various Applicant Guidebook sections at ICANN84. Although the titles indicate “SubPro IRT Work Session”, the sessions have been repurposed as open community sessions. Please join them and ask any questions you may have! - SubPro IRT Work Session (1 of 6): Applicant Journey | Community Input, Objections, and Appeals [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> - SubPro IRT Work Session (2 of 6): Application Evaluation [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> - SubPro IRT Work Session (3 of 6): Contention Set Resolution [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> - SubPro IRT Work Session (4 of 6): Application and Applicant Evaluation [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> - String Evaluation in the Next Round: DNS Stability, String Similarity, and IDN Variant Justification [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> 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=0014oPkjrw…> Information Sharing NEW: ICANN's Progress and Next Steps in Enforcing DNS Abuse Mitigation Requirements Since the introduction of the new Domain Name System (DNS) Abuse mitigation requirements [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> in April 2024, ICANN Contractual Compliance has taken a multifaceted approach to enforcement that blends complaint-driven investigations with proactive and audit-related actions. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> NEW: 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. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> NEW: ICANN Seeks Input on Name Collision IPv6 Research Study ICANN is seeking input on a study conducted to identify one or more IPv6 candidate prefixes that may be suitable for use in an AAAA record during controlled interruption, which is a name collision mitigation strategy. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> 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=0014oPkjrw…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> 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=0014oPkjrw…>. 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=0014oPkjrw…>. 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=0014oPkjrw…> 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 DEADLINE EXTENDED: 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, 07 November 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> 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=0014oPkjrw…> 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=0014oPkjrw…>. 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=0014oPkjrw…> 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=0014oPkjrw…>source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> on where to find reliable data. Happy editing! Public Comment NEW: Name Collision IPv6 Research Study [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> Submissions Opening Date: Monday, 20 October 2025 Submissions Closing Date: Monday, 22 December 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=0014oPkjrw…> 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=0014oPkjrw…> 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=0014oPkjrw…> 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=0014oPkjrw…> 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=0014oPkjrw…> 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=0014oPkjrw…> Submissions Opening Date: Thursday, 16 October 2025 Submissions Closing Date: Thursday, 4 December 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…>. 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=0014oPkjrw…>. · Training for Fresh Graduates and Women in ICT-Oman 2025 · Tech Policy Week - CITRIS · Domain Days Dubai 2025 · Apply for a Top-Level Domain at ICANN · ICANN Webinar Series for Europe: Fighting Digital Threats - How Poland's CSIRT Tackles Phishing, Spam and Malicious SMS · Webrazzi Summit 2025 · 2025 CDT Tech Prom · ICANN84 Dublin Annual General Meeting · CyberChess · NANOG 95 · Bread and Net 2025 · ARIN 56 · DNSSEC Training Latvia Volume 7, Issue 78 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…> | Next Issue: Thursday, 23 October 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=0014oPkjrw…>

1 0

FINAL REMINDER | Document and Motion deadline | Sunday, 19 October 2025 at 23:59 UTC for GNSO Council Meeting 29 October 2025 at 13:15 UTC /IST
by Terri Agnew Oct. 20, 2025

Oct. 20, 2025

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 19 October 2025 at 23:59 UTC) for the GNSO Council Meeting on Wednesday, 29 October 2025 at 13:15 UTC/IST 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/VKifBg Thank you. Kind regards, Terri Policy Team Supporting the GNSO

3 8

Additional Council Motion on Policy Intent regarding Specific IGO/INGO PDP Recommendations October 2025
by Susan Payne Oct. 20, 2025

Oct. 20, 2025

Council colleagues Please find attached an additional proposed Motion on the policy intent of the IGO/INGO PDP recommendations - taking the form of a proposed vote on Option 1, together with some additional resolved clauses to seek to address the concerns of the protected entities. This is submitted in order to meet the Motions deadline date, so that Councillors have the opportunity to review and reflect. Noting Operating Procedures 4.3.5, and per Anne's earlier email, the expectation is that not all of these Motions are likely to go forward to a vote, one or more will likely be withdrawn following further discussion. Susan Payne Head of Legal Policy [cid:image001.png@01DC4122.27CAD510]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 Ext 255 comlaude.com<http://comlaude.com> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAFJfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAFJfAADw_RQA0> [cid:image002.png@01DC4122.27CAD510]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DC4122.27CAD510] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DC4122.27CAD510] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DC4122.27CAD510] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DC4122.27CAD510] ________________________________ 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>

5 7

FYI | FW: [CORRESPONDENCE] Tripti Sinha to Nacho Amadoz and Tomslin Samme-Nlar RE GNSO Council SPS Report
by Terri Agnew Oct. 17, 2025

Oct. 17, 2025

Dear GNSO Council, Please see attached letter from ICANN Board Chair Tripti Sinha in response to the 19 August 2025 letter and the GNSO Council’s Strategic Planning Session Report. This will be posted shortly on the GNSO Correspondence page<https://gnso.icann.org/en/council/correspondence/2025>. Happy Friday, Terri From: Wendy Profit <wendy.profit(a)icann.org> Date: Friday, October 17, 2025 at 3:38 PM To: "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org>, GNSO-Secs <gnso-secs(a)icann.org>, Mary Wong <mary.wong(a)icann.org> Cc: Tripti Sinha <tripti.sinha(a)board.icann.org>, Correspondence <Correspondence(a)icann.org>, Board Ops Team <board-ops-team(a)icann.org>, Secretary <secretary(a)icann.org> Subject: [CORRESPONDENCE] Tripti Sinha to Nacho Amadoz and Tomslin Samme-Nlar RE GNSO Council SPS Report Dear Nacho Amadoz and Tomslin Samme-Nlar, Please find the attached letter from ICANN Board Chair Tripti Sinha in response to your 19 August 2025 letter and the GNSO Council’s Strategic Planning Session Report. Thank you and best regards, Wendy Profit Board Operations Senior Manager ICANN

1 0

UPDATE | Proposed Agenda | GNSO Council | Wednesday, 29 October 2025 Part 1 & Part 2
by Terri Agnew Oct. 17, 2025

Oct. 17, 2025

Added wiki page for Part 2 below. Thanks! Terri From: Terri Agnew <terri.agnew(a)icann.org> Date: Friday, October 17, 2025 at 12:52 PM 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 | GNSO Council | Wednesday, 29 October 2025 Part 1 & Part 2 Dear all, Please find below the agenda for the GNSO Council Part 1 ( at 13:15 IST/ UTC ) and Part 2 ( at 15:30 IST/UTC) on 29 October 2025. This will be posted on the agenda wiki page https://icann-community.atlassian.net/wiki/x/QKafBg (part 1) and https://icann-community.atlassian.net/wiki/x/T4AuGQ (part 2) shortly. Thank you. Kind regards, Terri Policy Team Supporting the GNSO ********** Draft GNSO Council Agenda 29 October 2025 - Part I 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/LJqfBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting held in Dublin, Ireland 13:15 - 15:15 GMT: https://tinyurl.com/3m7ru8zw Coordinated Universal Time: 13:15 - 15:15 UTC 03:15 Los Angeles; 06:15 Washington DC; 10:15 London; 11:15 Paris; 13:15 Moscow; 21:15 Melbourne GNSO Council Meeting Remote Participation: Zoom link to be shared 24 hours in advance 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 18 September 2025 were posted on 2 October 2025. Minutes of the GNSO Extraordinary Council Meeting on 09 October 2025 will be posted on 25 October 2025. Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: COUNCIL VOTE: New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations (20 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> 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. 3.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Vice-Chair) 3.2 - Council Vote (voting threshold: majority of each house) 3.3 - Next Steps Item 4: COUNCIL DISCUSSION - Celebrating GNSO Accomplishments between ICANN Meetings (10 minutes) During the GNSO Council’s most recent Strategic Planning Session in January 2025, the Council discussed ideas for highlighting the work of the GNSO to a larger audience. To that end, Councilors agreed to highlight the GNSO Council’s accomplishments or milestones between each ICANN meeting during the Council’s public meeting. In the period between ICANN83 and ICANN84, the Council and the groups under its remit accomplished the following milestones: 1. DNS Abuse - GNSO Council voted to request a Preliminary Issues Report, and the public comment period on this report recently closed. 2. Accuracy - GNSO Council Accuracy Small Team delivered a report with four Council recommendations, which the Council voted to approve in August. 3. Board readiness - The Council’s Board Readiness Small Team delivered its Findings Report to the GNSO Council, and the Council has started discussing the next steps for these recommendations. 4. Registration Data Request Service Standing Committee (“RDRS SC”) - the RDRS SC published its Findings Report for public comment, and has been reviewing the public comments during ICNAN84. The RDRS SC will soon deliver its Findings Report to the Council in preparation for the Board and GNSO Council dialogue on the System for Standardized Access/Disclosure (“SSAD”) recommendations. 5. Council Privacy Proxy Services Accreditation Issues (PPSAI) Small Team - the Council’s PPSAI Small Team completed its draft responses to the threshold questions from ICANN org and the Implementation Review Team (“IRT”), which will be discussed later in this meeting. Here, the Council will briefly highlight these milestones. 4.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Vice-Chair) 4.2 - Council Discussion 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Council PPSAI Small Team Responses to Threshold Questions (30 minutes) On 9 August 2016, the ICANN Board approved the Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> of the Privacy Proxy Services Accreditation Issues (PPSAI) Working Group, which contains 21 policy recommendations. ICANN org convened an Implementation Review Team (IRT) in 2016 and worked on the implementation of the policy recommendations until 2019 when the implementation work was paused due to overlapping issues around the General Data Protection Regulation (GDPR), data processing, and the Temporary Specification<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…>. In June 2024, ICANN org reconvened the PPSAI IRT and has been refining a set of overarching threshold questions that require input from the GNSO Council in order for ICANN org to, in consultation with the IRT, move forward on implementation of the 21 policy recommendations from the Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…>. ICANN org sent the threshold questions<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/7WQUZAK2VH…> to the GNSO Council for further guidance. The threshold questions are: 1. Are there any policy questions or items the IRT already wants to bring to the GNSO Council for guidance? 2. Implementation Model: Accreditation Program or Alternative Implementation: * Can an implementation model without a new standalone accreditation program remain consistent with the policy recommendations? 3. Disclosure Frameworks (Intellectual Property and Law Enforcement) * Are there specific areas to revisit under new law/policy? * Can these frameworks be aligned with existing work on the Registration Data Request Service (RDRS), Registration Data Policy, and other existing procedures and remain consistent with the policy recommendations? The PPSAI Small Team delivered its proposed responses<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> to the Council on 29 September 2025. Here, the PPSAI Small Team will present its draft responses, and the Council will determine next steps. 5.1 - Introduction of Topic (Paul McGrady, Council PPSAI Small Team Lead) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Prioritization of Upcoming Work (35 minutes) During the GNSO Council’s second Working Session at ICANN82<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the Council discussed its immediate and longer term pipeline of work, including work that the Council has previously committed to, e.g. Latin Diacritics, RPMs Phase 2, and a list of potential topics the GNSO Council could consider for future PDPs. Specifically, the GNSO Council discussed: (i) a newly-started PDP: Latin Diacritics; (ii) a previously committed to PDP: Rights Protection Mechanisms (RPMs) in gTLDs, Phase 2, and (iii) identified topics for potential future work: * DNS Abuse * RDDS (Accuracy, RDRS, PPSAI) * New gTLDs (from rounds to open process) * Expiration Policies * Transfers (dispute mechanism for registrants) The Council generally aligned around the need to prioritize the DNS Abuse work, requesting an Issue Report on 14 August. The RDRS Standing Committee published its Council Report for public comment<https://www.icann.org/en/public-comment/proceeding/registration-data-reques…>; the report provides some insight into anticipated next steps. The Council suggested that level of effort be integrated into the prioritization document, to help provide important context for the prioritization exercise. An updated prioritization document<https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-p…> was shared with Council on 05 September 2025. Following the Council’s September meeting, Councilors were asked to share the updated prioritization document<https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-p…> with their respective groups for further feedback and guidance. Here, the Council will continue this discussion for how to prioritize these topics given limited resources. 6.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Co-Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: Open Mic (10 minutes) Here, interested individuals may use this time to address the GNSO Council directly with comments, ideas, and feedback. Comments may be provided virtually via the Zoom room or via the microphone in the meeting room. 7.1 - Introduction of Topic (Nacho Amadoz, GNSO Interim Co-Chair) 7.2 - Council Discussion 7.3 - Next Steps Item 8: Any Other Business (10 minutes) 8.1 - Update to Council on Latin Diacritics PDP Timeline (Prudence Malinki, GNSO Council Liaison to LD PDP WG) 8.2 - Proposed Updates to ICANN Bylaws and Customer Standing Committee (CSC) Charter 8.3 - Farewell to Outgoing Councilors _______________________________ 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:15 UTC Local time between October and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PST) UTC-8 03:15 San José, Costa Rica (CST) UTC-6 04:15 New York/Washington DC, USA (EST) UTC-5 06:15 Buenos Aires, Argentina (ART) UTC-3 07:15 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 11:15 Paris, France (CET) UTC+1 11:15 Moscow, Russia (MSK) UTC+3 13:15 Singapore (SGT) UTC+8 18:15 Melbourne, Australia (AEDT) UTC+11 21:15 ---------------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/3m7ru8zw Draft GNSO Council Agenda 29 October 2025 - Part II (Admin) 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/LJqfBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting held in Dublin, Ireland 15:30-16:00 GMT: https://tinyurl.com/3dwc8fvr Coordinated Universal Time: 15:30-16:00 UTC 05:30 Los Angeles; 08:30 Washington DC; 12:30 London; 13:30 Paris; 15:30 Moscow; 23:30 Melbourne GNSO Council Meeting Remote Participation: posted 24 hours before meeting 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: Seating of the 2025-2026 Council (10 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest INCOMING COUNCILORS & LIAISONS: Susan Mohr SOI<https://icann-community.atlassian.net/wiki/x/2c1dBg> Commercial Stakeholder Group (ISPCP) Tapani Taravainen SOI<https://icann-community.atlassian.net/wiki/x/7YFdBg> Non-Commercial Stakeholder Group (NCSG) Benjamin Akinmoyeje SOI<https://icann-community.atlassian.net/wiki/x/a5FdBg> Non-Commercial Stakeholder Group (NCSG) Gaurav Vedi SO<https://icann-community.atlassian.net/wiki/x/FwAVGg>I Contracted Parties House (CPH) Nominating Committee Appointee (NCA) Christian Dawson SOI<https://icann-community.atlassian.net/wiki/x/1YddBg> Non-Contracted Party House (NCPH) Nominating Committee Appointee (NCA) 1.3 - Review / Amend Agenda Item 2. Election of the Chair (10 minutes) One nomination was received for this position from Susan Payne of the Non-Contracted Party House (NCPH). Susan circulated her candidate statement to the GNSO Council on 10 October 2025. Here the GNSO Council will proceed to hold the election for its Chair for 2025-2026, according to the GNSO Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on Officer Elections: Chair and Vice-Chairs (see Appendix 1 below)). Item 3. Selection of GNSO Council Vice Chair 2025-2026 (05 minutes) Non-Contracted Party House - TBD Contracted Party House - TBD Item 4. ANY OTHER BUSINESS (05 minutes) 4.1 - TBD Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2) 2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: 1. The GNSO Chair shall be elected by a 60 percent vote of each house. 2. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. a. All ballots will include the “none of the above” option. In the event that a 60 percent vote of each house selects the “none of the above” option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. b. In the case of a tie for the most votes between the two candidates, or between a candidate and “none of above,” a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. c. The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and “none of the above.” d. In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and “none of the above.” e. If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. 1. Each house shall select a Council Vice-Chair from within its respective house. 2. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 3. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 4. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair’s term, the Vice-Chairs will serve as Interim GNSO Co- Chairs to jointly oversee the new Chair election and conduct Council business until a successful election can be held. In the event that one or both Vice-Chairs’ terms ends concurrently with the term of the previous Chair, the procedures described in Section 2.2.1 below shall apply. 5. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws,<https://www.icann.org/resources/pages/governance/bylaws-en/#article11> Article 11, Section 3) (i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or Annex A-2 hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: (i) Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (ii) Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority (as defined in Section 11.3(i)(xix)). (iv) Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. (vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under (iv) or (v) above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. (vii) Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. (viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. (ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, (x) Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xi) Modification of Approved PDP Recommendation: Prior to Final Approval by the Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. (xii) Initiation of an Expedited Policy Development Process ("EPDP"): requires an affirmative vote of a GNSO Supermajority. (xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO Supermajority. (xiv) Approval of EPDP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xv) Approve an EPDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xvi) Initiation of a GNSO Guidance Process ("GGP"): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (xvii) Rejection of Initiation of a GGP Requested by the Board: requires an affirmative vote of a GNSO Supermajority. (xviii) Approval of GGP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xix) A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf 4.4 Absentee Voting 4.1.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. Fill a Council position open for election. 4.1.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting’s adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.1.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.1.4 Absentee balloting does not affect quorum requirements.

1 0

Proposed Agenda | GNSO Council | Wednesday, 29 October 2025 Part 1 & Part 2
by Terri Agnew Oct. 17, 2025

Oct. 17, 2025

Dear all, Please find below the agenda for the GNSO Council Part 1 ( at 13:15 IST/ UTC ) and Part 2 ( at 15:30 IST/UTC) on 29 October 2025. This will be posted on the agenda wiki page<https://icann-community.atlassian.net/wiki/x/QKafBg> shortly. Thank you. Kind regards, Terri Policy Team Supporting the GNSO ********** Draft GNSO Council Agenda 29 October 2025 - Part I 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/LJqfBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting held in Dublin, Ireland 13:15 - 15:15 GMT: https://tinyurl.com/3m7ru8zw Coordinated Universal Time: 13:15 - 15:15 UTC 03:15 Los Angeles; 06:15 Washington DC; 10:15 London; 11:15 Paris; 13:15 Moscow; 21:15 Melbourne GNSO Council Meeting Remote Participation: Zoom link to be shared 24 hours in advance 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 18 September 2025 were posted on 2 October 2025. Minutes of the GNSO Extraordinary Council Meeting on 09 October 2025 will be posted on 25 October 2025. Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: COUNCIL VOTE: New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations (20 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> 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. 3.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Vice-Chair) 3.2 - Council Vote (voting threshold: majority of each house) 3.3 - Next Steps Item 4: COUNCIL DISCUSSION - Celebrating GNSO Accomplishments between ICANN Meetings (10 minutes) During the GNSO Council’s most recent Strategic Planning Session in January 2025, the Council discussed ideas for highlighting the work of the GNSO to a larger audience. To that end, Councilors agreed to highlight the GNSO Council’s accomplishments or milestones between each ICANN meeting during the Council’s public meeting. In the period between ICANN83 and ICANN84, the Council and the groups under its remit accomplished the following milestones: 1. DNS Abuse - GNSO Council voted to request a Preliminary Issues Report, and the public comment period on this report recently closed. 2. Accuracy - GNSO Council Accuracy Small Team delivered a report with four Council recommendations, which the Council voted to approve in August. 3. Board readiness - The Council’s Board Readiness Small Team delivered its Findings Report to the GNSO Council, and the Council has started discussing the next steps for these recommendations. 4. Registration Data Request Service Standing Committee (“RDRS SC”) - the RDRS SC published its Findings Report for public comment, and has been reviewing the public comments during ICNAN84. The RDRS SC will soon deliver its Findings Report to the Council in preparation for the Board and GNSO Council dialogue on the System for Standardized Access/Disclosure (“SSAD”) recommendations. 5. Council Privacy Proxy Services Accreditation Issues (PPSAI) Small Team - the Council’s PPSAI Small Team completed its draft responses to the threshold questions from ICANN org and the Implementation Review Team (“IRT”), which will be discussed later in this meeting. Here, the Council will briefly highlight these milestones. 4.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Vice-Chair) 4.2 - Council Discussion 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Council PPSAI Small Team Responses to Threshold Questions (30 minutes) On 9 August 2016, the ICANN Board approved the Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> of the Privacy Proxy Services Accreditation Issues (PPSAI) Working Group, which contains 21 policy recommendations. ICANN org convened an Implementation Review Team (IRT) in 2016 and worked on the implementation of the policy recommendations until 2019 when the implementation work was paused due to overlapping issues around the General Data Protection Regulation (GDPR), data processing, and the Temporary Specification<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…>. In June 2024, ICANN org reconvened the PPSAI IRT and has been refining a set of overarching threshold questions that require input from the GNSO Council in order for ICANN org to, in consultation with the IRT, move forward on implementation of the 21 policy recommendations from the Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…>. ICANN org sent the threshold questions<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/7WQUZAK2VH…> to the GNSO Council for further guidance. The threshold questions are: 1. Are there any policy questions or items the IRT already wants to bring to the GNSO Council for guidance? 2. Implementation Model: Accreditation Program or Alternative Implementation: * Can an implementation model without a new standalone accreditation program remain consistent with the policy recommendations? 3. Disclosure Frameworks (Intellectual Property and Law Enforcement) * Are there specific areas to revisit under new law/policy? * Can these frameworks be aligned with existing work on the Registration Data Request Service (RDRS), Registration Data Policy, and other existing procedures and remain consistent with the policy recommendations? The PPSAI Small Team delivered its proposed responses<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> to the Council on 29 September 2025. Here, the PPSAI Small Team will present its draft responses, and the Council will determine next steps. 5.1 - Introduction of Topic (Paul McGrady, Council PPSAI Small Team Lead) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Prioritization of Upcoming Work (35 minutes) During the GNSO Council’s second Working Session at ICANN82<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the Council discussed its immediate and longer term pipeline of work, including work that the Council has previously committed to, e.g. Latin Diacritics, RPMs Phase 2, and a list of potential topics the GNSO Council could consider for future PDPs. Specifically, the GNSO Council discussed: (i) a newly-started PDP: Latin Diacritics; (ii) a previously committed to PDP: Rights Protection Mechanisms (RPMs) in gTLDs, Phase 2, and (iii) identified topics for potential future work: * DNS Abuse * RDDS (Accuracy, RDRS, PPSAI) * New gTLDs (from rounds to open process) * Expiration Policies * Transfers (dispute mechanism for registrants) The Council generally aligned around the need to prioritize the DNS Abuse work, requesting an Issue Report on 14 August. The RDRS Standing Committee published its Council Report for public comment<https://www.icann.org/en/public-comment/proceeding/registration-data-reques…>; the report provides some insight into anticipated next steps. The Council suggested that level of effort be integrated into the prioritization document, to help provide important context for the prioritization exercise. An updated prioritization document<https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-p…> was shared with Council on 05 September 2025. Following the Council’s September meeting, Councilors were asked to share the updated prioritization document<https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-p…> with their respective groups for further feedback and guidance. Here, the Council will continue this discussion for how to prioritize these topics given limited resources. 6.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Interim Co-Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: Open Mic (10 minutes) Here, interested individuals may use this time to address the GNSO Council directly with comments, ideas, and feedback. Comments may be provided virtually via the Zoom room or via the microphone in the meeting room. 7.1 - Introduction of Topic (Nacho Amadoz, GNSO Interim Co-Chair) 7.2 - Council Discussion 7.3 - Next Steps Item 8: Any Other Business (10 minutes) 8.1 - Update to Council on Latin Diacritics PDP Timeline (Prudence Malinki, GNSO Council Liaison to LD PDP WG) 8.2 - Proposed Updates to ICANN Bylaws and Customer Standing Committee (CSC) Charter 8.3 - Farewell to Outgoing Councilors _______________________________ 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:15 UTC Local time between October and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PST) UTC-8 03:15 San José, Costa Rica (CST) UTC-6 04:15 New York/Washington DC, USA (EST) UTC-5 06:15 Buenos Aires, Argentina (ART) UTC-3 07:15 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 11:15 Paris, France (CET) UTC+1 11:15 Moscow, Russia (MSK) UTC+3 13:15 Singapore (SGT) UTC+8 18:15 Melbourne, Australia (AEDT) UTC+11 21:15 ---------------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/3m7ru8zw Draft GNSO Council Agenda 29 October 2025 - Part II (Admin) 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/LJqfBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting held in Dublin, Ireland 15:30-16:00 GMT: https://tinyurl.com/3dwc8fvr Coordinated Universal Time: 15:30-16:00 UTC 05:30 Los Angeles; 08:30 Washington DC; 12:30 London; 13:30 Paris; 15:30 Moscow; 23:30 Melbourne GNSO Council Meeting Remote Participation: posted 24 hours before meeting 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: Seating of the 2025-2026 Council (10 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest INCOMING COUNCILORS & LIAISONS: Susan Mohr SOI<https://icann-community.atlassian.net/wiki/x/2c1dBg> Commercial Stakeholder Group (ISPCP) Tapani Taravainen SOI<https://icann-community.atlassian.net/wiki/x/7YFdBg> Non-Commercial Stakeholder Group (NCSG) Benjamin Akinmoyeje SOI<https://icann-community.atlassian.net/wiki/x/a5FdBg> Non-Commercial Stakeholder Group (NCSG) Gaurav Vedi SO<https://icann-community.atlassian.net/wiki/x/FwAVGg>I Contracted Parties House (CPH) Nominating Committee Appointee (NCA) Christian Dawson SOI<https://icann-community.atlassian.net/wiki/x/1YddBg> Non-Contracted Party House (NCPH) Nominating Committee Appointee (NCA) 1.3 - Review / Amend Agenda Item 2. Election of the Chair (10 minutes) One nomination was received for this position from Susan Payne of the Non-Contracted Party House (NCPH). Susan circulated her candidate statement to the GNSO Council on 10 October 2025. Here the GNSO Council will proceed to hold the election for its Chair for 2025-2026, according to the GNSO Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on Officer Elections: Chair and Vice-Chairs (see Appendix 1 below)). Item 3. Selection of GNSO Council Vice Chair 2025-2026 (05 minutes) Non-Contracted Party House - TBD Contracted Party House - TBD Item 4. ANY OTHER BUSINESS (05 minutes) 4.1 - TBD Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2) 2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: 1. The GNSO Chair shall be elected by a 60 percent vote of each house. 2. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. a. All ballots will include the “none of the above” option. In the event that a 60 percent vote of each house selects the “none of the above” option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. b. In the case of a tie for the most votes between the two candidates, or between a candidate and “none of above,” a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. c. The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and “none of the above.” d. In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and “none of the above.” e. If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. 1. Each house shall select a Council Vice-Chair from within its respective house. 2. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 3. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 4. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair’s term, the Vice-Chairs will serve as Interim GNSO Co- Chairs to jointly oversee the new Chair election and conduct Council business until a successful election can be held. In the event that one or both Vice-Chairs’ terms ends concurrently with the term of the previous Chair, the procedures described in Section 2.2.1 below shall apply. 5. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws,<https://www.icann.org/resources/pages/governance/bylaws-en/#article11> Article 11, Section 3) (i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or Annex A-2 hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: (i) Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (ii) Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority (as defined in Section 11.3(i)(xix)). (iv) Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. (vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under (iv) or (v) above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. (vii) Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. (viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. (ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, (x) Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xi) Modification of Approved PDP Recommendation: Prior to Final Approval by the Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. (xii) Initiation of an Expedited Policy Development Process ("EPDP"): requires an affirmative vote of a GNSO Supermajority. (xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO Supermajority. (xiv) Approval of EPDP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xv) Approve an EPDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xvi) Initiation of a GNSO Guidance Process ("GGP"): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (xvii) Rejection of Initiation of a GGP Requested by the Board: requires an affirmative vote of a GNSO Supermajority. (xviii) Approval of GGP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xix) A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf 4.4 Absentee Voting 4.1.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. Fill a Council position open for election. 4.1.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting’s adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.1.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.1.4 Absentee balloting does not affect quorum requirements.

1 0

FW: RAA Requirements Related to Billing Contact [ ref:!00D1a0Y7OU.!500Qk0OIDFY:ref ]
by Devan Reed Oct. 17, 2025

Oct. 17, 2025

Dear Councilors, Please find attached a letter regarding RAA Requirements Related to Billing Contact. This has been posted on the GNSO Correspondence webpage: https://gnso.icann.org/en/council/correspondence/2025. Thank you! Kind regards, Devan From: Correspondence <correspondence(a)ces.icann.org> Date: Thursday, October 16, 2025 at 11:25 AM To: Tomslin Samme-Nlar <mesumbeslin(a)gmail.com>, "nacho.amadoz(a)corenic.org" <nacho.amadoz(a)corenic.org> Cc: Isabelle Colas-Adeshina <isabelle.colasadeshina(a)icann.org>, Karen Lentz <karen.lentz(a)icann.org>, GNSO-Secs <gnso-secs(a)icann.org>, Theresa Swinehart <theresa.swinehart(a)icann.org> Subject: RAA Requirements Related to Billing Contact [ ref:!00D1a0Y7OU.!500Qk0OIDFY:ref ] Dear Tomslin Samme-Nlar and Nacho Amadoz, Please find attached a letter from Theresa Swinehart, Senior Vice President, Global Domains & Strategy, at ICANN. This letter will be posted shortly to the ICANN Correspondence page (https://www.icann.org/resources/pages/correspondence) Please submit any questions you may have about this message to correspondence(a)icann.org<mailto:correspondence@icann.org>. Best Regards, Michael Kovach The Correspondence Team Internet Corporation for Assigned Names and Numbers (ICANN) correspondence(a)icann.org www.icann.org ref:!00D1a0Y7OU.!500Qk0OIDFY:ref [https://icanncrm.my.salesforce.com/servlet/servlet.ImageServer?oid=00D1a000…]

1 0