July 2025 - council - lists.icann.org

GNSO Council resolutions 10 July 2025
by Terri Agnew July 10, 2025

July 10, 2025

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 10 July 2025 which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. Thank you. Kind regards, Terri Policy Team Supporting the GNSO CONSENT AGENDA Motion to Confirm the GNSO-Appointed Member for the Universal Acceptance (UA) Expert Working Group (EWG) Submitted by: Tomslin Samme-Nlar WHEREAS, 1. On 7 May 2025, ICANN opened a Call for Nominations<https://www.icann.org/en/announcements/details/icann-call-for-nominations-u…> inviting the At-large Advisory Committee (ALAC), the Country Code Names Supporting Organization (ccNSO), the Governmental Advisory Committee (GAC), the Generic Names Supporting Organization (GNSO), and the Security and Stability Advisory Committee (SSAC) to each submit one nomination for the formation of a new Universal Acceptance (UA) Expert Working Group (EWG) to provide guidance on promoting UA adoption. 2. On 2 June 2025, the GNSO announced a Call for Expressions of Interest (EOI)<https://gnso.icann.org/en/en/announcements/announcement-02jun25-en.htm> to solicit volunteers for the GNSO nominee position, closing the process on 13 June 2025. 3. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing the UA EWG Member applications and recommending one individual for the GNSO Council to appoint. 4. On 24 June 2025, the SSC convened to review and deliberate on the six (6) applications received, taking into account the selection criteria outlined in the announcements. 5. On 30 June 2025, the SSC submitted its Full Consensus recommendation to the GNSO Council, by way of submission of the relevant motion. 6. The GNSO Council considered the recommendation of the SSC. RESOLVED, 1. The GNSO Council confirms Nitin Walia as the SSC’s selection of the GNSO nominee for the UA EWG. 2. The GNSO Council asks the GNSO Secretariat to communicate the confirmation of Nitin Walia’s appointment as the GNSO nominee for the UA EWG to the staff supporting the UA EWG. 3. The GNSO Council asks the GNSO Secretariat to inform the GNSO-appointee for the UA EWG that he has been selected. 4. The GNSO Council asks the GNSO Secretariat to send a response to those applicants who were not appointed, thanking them for their interest and encouraging them to apply for future opportunities as they arise. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> Motion for GNSO Council Review of ICANN83 GAC Communiqué Submitted by: Tomslin Samme-Nlar Whereas, 1. The Governmental Advisory Committee (GAC) advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The Generic Names Supporting Organization (GNSO) is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO Council has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present, or future gTLD policy activities that may directly or indirectly relate to Advice provided by the GAC. 4. The GNSO Council's review of GAC Communiqué Advice and Issues of Importance is intended to further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board, and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the ICANN83 Prague Communiqué Advice<https://docs.google.com/document/d/10hMkkf9GZuvtt0i2wMF_1nImmiBhBRNj9cSNmjD…> and Issues of Importance<https://docs.google.com/document/d/1zxpWVB3u9F37Rb_c5SFeTCE-OdJl-28K/edit> and requests that the GNSO Council Chair communicate the GNSO Council Review of ICANN83 GAC Communiqué Advice and Issues of Importance to the ICANN Board. 2. The GNSO Council requests that the GNSO Liaison to the GAC also informs the GAC of the communication between the GNSO Council and the ICANN Board. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> Request for Consideration of Motion on Short Notice Submitted by: Susan Payne Seconded by: Anne Aikman-Scalese 1. Pursuant to GNSO Operating Procedures s3.3.2 a, b and c the IPC requests that the GNSO Council considers the below [Motion on Reviews], despite submission after the Submission Deadline. RESOLVED 1. The GNSO Council resolves to consider and vote on the [Motion on Reviews] during the meeting on 10 July 2025, despite submission after the Submission deadline. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…> Motion on Reviews (DEFERRED to the August 2025 meeting) Submitted by: Susan Payne Seconded by: Anne Aikman-Scalese WHEREAS, 1. Article 4.6 (b) of ICANN’s Bylaws, requires that the ICANN Board shall cause a periodic Accountability and Transparency Review which shall be conducted no less frequently than every five years measured from the date the previous Accountability and Transparency Review Team (ATRT) was convened. 2. The Third ATRT (ATRT3) was convened in April 2019, and therefore the next review, the Fourth ATRT (ATRT4), should have been initiated in April 2024. 3. ICANN org consulted with the Supporting Organizations and the Advisory Committees, through their Chairs, on the timing and potential deferral of ATRT4 for a limited period of time. Three of the five responding SOs and ACs expressed support for the deferral of ATRT4, citing unimplemented ATRT3 recommendations and capacity issues with running multiple reviews-related projects in parallel. Two of the responding ACs indicated their preference for ATRT4 to initiate on schedule, citing adherence to ICANN Bylaws and the role that Accountability and Transparency Reviews play in providing oversight of ICANN's core commitment. 4. Following that consultation, on 29 April 2024, the Board resolved <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> to defer ATRT4 for a limited time not to exceed twelve months. 5. The Board received feedback from many parts of the ICANN community that the current status of review program activities, including the potential overlap of the Continuous Improvement Program (CIP), a Pilot Holistic Review, and pending ATRT4 are causing confusion and stressing community resources. The Board also received, on 15 April 2025, statements from the Registries Stakeholder Group (RySG)<https://www.icann.org/en/system/files/correspondence/bacon-to-sinha-14apr25…>, the Country Code Names Supporting Organization (ccNSO)<https://www.icann.org/en/system/files/correspondence/reynoso-to-sinha-15apr…>, and At-Large Advisory Committee (ALAC)<https://www.icann.org/en/system/files/correspondence/zuck-to-sinha-15apr25-…> regarding the broad issue of reviews, which did not align on the best path forward. 6. On 19 May 2025 the Board resolved <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> to continue the deferral of the ATRT4, and other Specific Reviews, pending community dialogue to inform next steps, and notwithstanding the timing mandated under the Bylaws for the commencement of ATRT4. 7. During the ICANN 84 meeting ICANN org further consulted with the Supporting Organizations and the Advisory Committees, through their Chairs. A potential path forward was proposed and appeared to gain support, whereby: * The community would urgently propose a Bylaws amendment to the Board that would amend the Bylaws to allow for a one-time review of all Reviews currently required by the Bylaws and to suspend the conduct of all Reviews until this exercise is completed; * With the explicit safeguard of a time frame for completion, absent which the current Reviews obligations come back fully into force. 8. On 19 June 2025 the At Large Advisory Committee (ALAC) submitted an Empowered Community Reconsideration Petition seeking reconsideration of the 19 May Board resolution to defer ATRT4 and related resolutions relating to community dialogue on and development of a revised reviews program. 9. As a Decisional Participant of the Empowered Community, the GNSO has until 10 July 2025 to decide to support the ALAC Petition as a Supporting Petitioner. Although the Intellectual Property Constituency (IPC) has expressed its support, the feedback from other Stakeholder Groups and Constituencies indicates that there is insufficient support from the GNSO as a whole, at this time, to meet the voting threshold required to give such support. In particular: * The NCSG expressed continued support for the potential path forward referred to at paragraph 7 above; * The RrSG noted it understands and appreciates the ALAC concerns but does not believe an EC petition is warranted at this juncture when dialogue on how to best proceed is ongoing; and * RySG expressed that it recognizes the importance of Reviews in general, as well as the need for ICANN to abide by its Bylaws, and that it has been discussing the path forward initially proposed by the SO/AC leaders in Prague. RESOLVED, 1. The GNSO Council expresses its appreciation for the concerns expressed by the ALAC as reflected in the Empowered Community Reconsideration Petition. 2. The GNSO Council supports, at this time and on a non-precedential basis, the potential path forward initially proposed at the SO/AC leaders meeting at ICANN 84, namely: * The community would urgently propose a Bylaws amendment to the Board that would amend the Bylaws to allow for a one-time review of all Reviews currently required by the Bylaws and to suspend the conduct of all Reviews until this exercise is completed; * With the explicit safeguard of a time frame for completion, absent which the current Reviews obligations come back fully into force. 3. The GNSO Council will convene a Small Team of volunteers to draft both a proposed Bylaws amendment and a potential plan for the conduct of the one-time review of all reviews, to share with other SOs and ACs and ICANN Board.The GNSO Council urges the ICANN Board to initiate and conduct the Standard Bylaws Amendment process without any undue delay and at the next Board Meeting after the amendment receives indications of support or non-objection of the other SOs and ACs, taking the GNSO’s proposal as a guideline. Vote Results<https://gnso.icann.org/sites/default/files/policy/2025/vote-result/gnso-cou…>

1 0

FW: [Ext] NEW: ICANN Announces Publication of Continuous Improvement Program Framework
by Julie Bisland July 10, 2025

July 10, 2025

FYI-- From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, July 10, 2025 at 10:11 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: ICANN Announces Publication of Continuous Improvement Program Framework [https://danh45uab.cc.rs6.net/on.jsp?ca=e0a7baed-2a3b-4077-92ff-71020a8ca401…] Thursday, 10 July 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=001w4k_xpm…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents Information Sharing · NEW: ICANN Announces Publication of Continuous Improvement Program Framework · NEW: ICANN’s Organizational Objectives for Fiscal Year 2026 · NEW: How Choice of Reputation Blocklists Affects DNS Abuse Metrics · NEW: Publication: SAC129 SSAC Comments on GNSO Domain Name Registration Data Accuracy Concept Proposal Next Round · Next Round Outreach, Engagement, and Communications Snapshot · ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics · Next Round Champions Toolkit Available in the Six ICANN Languages 🚨 Action Items 🚨 · ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building · Call for ASP Mentors · ICANNWiki Seeking Volunteers Public Comment · MONDAY: Updated ICANN Community Participant Code of Conduct Concerning SOIs · Proposed Next Round Base gTLD Registry Agreement - Public Comment 1 of 2 · Final Proceeding for Proposed Language for the Draft Next Round Applicant Guidebook (AGB) · Root Zone Label Generation Rules Version 6 (RZ-LGR-6) · Maximal Starting Repertoire Version 6 (MSR-6) Events · These events occur in July 2025. Information Sharing NEW: ICANN Announces Publication of Continuous Improvement Program Framework With the framework now published, the work of the CIP-CCG is complete and the CIP enters the implementation phase, during which each SO and AC, and the NomCom will begin planning and executing an assessment of the CIP. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> NEW: ICANN’s Organizational Objectives for Fiscal Year 2026 The FY26 Organizational Objectives will act as the organizational Objectives and Key Results to track the ICANN organization's (org) progress on the FY26 Operating Plan and Budget. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> NEW: How Choice of Reputation Blocklists Affects DNS Abuse Metrics Reputation blocklists (RBLs) are fundamental for identifying and measuring Domain Name System (DNS) Abuse. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> NEW: Publication: SAC129 SSAC Comments on GNSO Domain Name Registration Data Accuracy Concept Proposal This is a comment to the GNSO Council in response to their Concept Proposal on Accuracy Scoping from the ICANN SSAC. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> Next Round Next Round Outreach, Engagement, and Communications Snapshot We’re excited to introduce the Next Round Snapshot, a new monthly recap that highlights key updates shared during the IRT Outreach meetings. This report covers recent activities across the Applicant Support Program (ASP), Registry Service Provider (RSP) evaluation, regional and topical engagement, web traffic stats, and communications milestones. Developed in response to GAC feedback, this snapshot supports visibility and alignment across teams working on the New gTLD Program: Next Round. 📅 Published monthly following each IRT Outreach meeting 📎 Check out the inaugural April/May edition here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…>. For questions, contact globalsupport(a)icann.org.<mailto:globalsupport@icann.org> 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=001w4k_xpm…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> 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=001w4k_xpm…>. 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>. Action Items ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building It recognizes ICANN community members for significant efforts in developing aptitude in areas related to ICANN's mission. Deadline: 31 July 2025 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> 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=001w4k_xpm…>. 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=001w4k_xpm…> 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>. 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=001w4k_xpm…>. 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=001w4k_xpm…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> on where to find reliable data. Happy editing! Public Comment MONDAY: Updated ICANN Community Participant Code of Conduct Concerning SOIs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> Submissions Opening Date: Monday, 12 May 2025 Submissions Closing Date: Monday, 14 July 2025 Proposed Next Round Base gTLD Registry Agreement - Public Comment 1 of 2 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> Submissions Opening Date: Wednesday, 4 June 2025 Submissions Closing Date: Monday, 21 July 2025 Final Proceeding for Proposed Language for the Draft Next Round Applicant Guidebook (AGB) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> Submissions Opening Date: Friday, 30 May 2025 Submissions Closing Date: Wednesday, 23 July 2025 Root Zone Label Generation Rules Version 6 (RZ-LGR-6) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> Open for Submissions: 17 June 2025 Closed for Submissions: 29 July 2025 Maximal Starting Repertoire Version 6 (MSR-6) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> Open for Submissions: 17 June 2025 Closed for Submissions: 29 July 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…>. Events These events occur in July 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=001w4k_xpm…>. · CANTO 2025 Conference · Africa Law Tech Festival 2025 · DNS Operations and DNSSEC Hands-On Workshop - Pakistan 2025 · AAU 16th Quadrienal General Conference · VNNIC Internet Conference 2025 · Asia Pacific Advanced Network Conference (APAN60) Volume 7, Issue 50 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…> | Next Issue: Monday, 14 July 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001w4k_xpm…>

1 0

Fwd:
by Anne ICANN July 10, 2025

July 10, 2025

Dear Councilors and staff, Could not resist forwarding this picture from our three Council members active at WSIS+20 in Geneva - a dynamic trio! Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

1 0

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 10 July 2025
by Terri Agnew July 10, 2025

July 10, 2025

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 10 July 2025 at 13:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> 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/KKafBg Check your time zone: https://tinyurl.com/58frfr46 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/4KefBg> 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

Jennifer Chung Selection to WSIS Informal Multistakeholder Sounding Board!
by Anne ICANN July 9, 2025

July 9, 2025

Dear Councilors, The WSIS IG Tracking Team is happy to report that Jen has been selected by the UN's Co-Facilitators of the WSIS+20 Review to serve on the Informal Multistakeholder Sounding Board! Congratulations are also due to Board Seat 14 Director Chris Buckridge as well as Theresa Swinehart and Jimson Olufuye. Full list appears below as per ICANN's report to the WSIS list. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com * Valeria Betancourt (Ecuador), Civil Society – Latin America and the Caribbean – MAG member * Chris Buckridge (Australia), Technical Community – Western European and Others Group – MAG member * Amrita Choudhury (India), Civil Society – Asia Pacific – MAG member * Jennifer Chung (China), Technical Community – Asia Pacific – MAG member * Hossam Reda Elgamal (Egypt), Private Sector – Africa – MAG member * Maria Fernanda Garza (Mexico), Private Sector – Latin America and the Caribbean – Leadership Panel member * Tereza Horejsova (Czechia), Civil Society – Eastern Europe – MAG member * Wolfgang Kleinwächter (Germany), Civil Society – Western European and Others Group – MAG member * Jimson Olufuye (Nigeria), Private Sector – Africa – MAG member * Theresa Swinehart (United States), Technical Community – Western European and Others Group – MAG member Ex Officio * Vinton Cerf (United States) — At-large – Western European and Others Group – Chair of the IGF Leadership Panel

2 1

Updated agenda #2 | Proposed Agenda | GNSO Council Meeting | Thursday, 10 July 2025
by Terri Agnew July 9, 2025

July 9, 2025

Dear GNSO Council, There has been a second update to the 10 July 2025 GNSO Council agenda. Changes: * The following two items are now one item: Item 4: COUNCIL VOTE - GNSO Support - Community Reconsideration Supporting Decisional Participant (15 minutes) and Item 5: Board deferral of Bylaws-mandated Reviews and steps needed for Community Input (25 minutes) * Updated item appears as: Item 4: COUNCIL VOTE - Council Next Steps Regarding ICANN Reviews(40 minutes) * Additional item numbers have been adjusted due to above merged items. All changes can be seen on the wiki agenda page: https://icann-community.atlassian.net/wiki/x/KKafBg **Updated agenda GNSO Council Agenda 10 July 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/4KefBg 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, 10 July 2025 at 13:00 UTC: https://tinyurl.com/58frfr46 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 [Published 24 hours prior to meeting]: https://icann83.sched.com/event/246XL/gnso-council-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: 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 15 May 2025 were posted on 02 June 2025. Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 11 June 2025 were posted on 30 June 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: Consent Agenda (5 minutes) * Confirmation of the GNSO-appointed Member for the Universal Acceptance (UA) Expert Working Group (EWG) * GNSO Council Review of GAC Communiqué Item 4: COUNCIL VOTE - Council Next Steps Regarding ICANN Reviews(40 minutes) On 27 May 2025<https://www.icann.org/en/system/files/correspondence/sinha-to-holen-et-al-2…>, the Board wrote to SO/AC Leaders with an update on the ICANN Reviews. Specifically, following input from the community, the Board informed SO/AC leaders that it took the following actions related to reviews during its 19 May meeting: 1. Continue the deferral of Organizational Reviews until the completion of one CIP cycle (estimated at 3 years). 2. Conclude the Pilot Holistic Review and following the completion of the CIP cycle, consider whether to rename and re-charter an effort focused solely on designing a review of the CIP. 3. Continue the community dialogue to support a broader discussion on reviews. This will include an engagement session at ICANN84 focused on the purpose and essential subject areas for reviews. 4. Continue the deferral of the fourth Accountability and Transparency Review (ATRT4) to support the community’s capacity to participate in the dialogues, and any related activities that may result from such discussions. Please see the relevant Board Resolution<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> for further information. During its May meeting, the Council had agreed to send correspondence to the Board, sharing its thoughts on next steps for ICANN Reviews. With the Board’s suggested approach generally in line with sentiments shared during the Council’s May meeting, it seems that circumstances may have overtaken the need to send correspondence in the context of that action item. During ICANN83, the SO/AC Chairs met with ICANN org to discuss a potential path forward. During the Council’s Wrap-Up<https://icann83.sched.com/event/246XW/gnso-council-wrap-up> session, GNSO Chair Greg DiBiase shared a high-level overview of that approach, asking that Councilors begin socializing the approach with their respective groups. Additional options were subsequently circulated to the GNSO Council. 1. The ICANN Board amends the Bylaws to allow for a one-time review of all Reviews currently required by the Bylaws (with solutions for the issues we face today with Reviews as output recommendations) and to suspend the initiation of all Reviews until this exercise is completed. (this option was discussed by the SOAC leaders at ICANN83 and put forth by the NCSG on list) 2. The ICANN Board amends the Bylaws to change the cadence of mandated Reviews to alleviate concerns about non-compliance with current Bylaws and initiates a one-time review of all Reviews through other means (i.e., the review of all Reviews is NOT outlined in a Bylaws amendment). 3. The ICANN Board does not amend any Bylaws but continues to defer Reviews while the Community initiates a review of all Reviews. (this option is essentially the path envisioned in the Board’s resolution) 4. ATRT4 is convened with the mandate to conduct a review of Reviews (although this would not be binding, and the ATRT 4 team would be able to change scope as indicated in the relevant Bylaws text) Here, the Council will continue its discussion from ICANN83, discuss feedback from SG/Cs on the potential options, and determine next steps. If Councilors are able to agree on an approach, the Council would then vote to approve that approach. 4.1 - Vote on Request for Consideration (voting threshold: unanimity) 4.2 - Presentation of motion<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…> (Susan Payne, IPC Councilor) 4.3 - Council Discussion 4.4 - Council Vote (voting threshold: simple majority) Item 5: COUNCIL BRIEFING - Second IANA Naming Function Review Team (IFR2) Draft Report (20 minutes) The IANA Naming Function Review is an accountability mechanism created as part of the Internet Assigned Numbers Authority (IANA) stewardship transition to ensure that ICANN’s IANA work through Public Technical Identifiers (PTI) meets the needs and expectations of its naming customers. Under the ICANN Bylaws, the ICANN Board must convene an IFR no less frequently than every five years, measured from the date the previous IFR was convened. The board convened<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> the first IFR on 16 September 2018. The second IFR team (IFR2) conducted the review in accordance with the scope specified in the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en/#article18>. The review focuses on PTI’s performance of the IANA naming function against the contractual requirements in the IANA Naming Function Contract and the IANA Naming Function Statement of Work<https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30s…>. The naming functions under review include management of the DNS root zone, a critical function for the ongoing operation of the Internet. The IFR2 recently sought public comments<https://www.icann.org/en/public-comment/proceeding/second-iana-naming-funct…> on its Draft Report, which contained findings and recommendations in three key areas: * Presence of specific Domain Name System Security Extensions (DNSSEC) policy details in the IANA Naming Function Contract * Transparency and availability of Contract amendments * Frequency of reviews After considering public comment received and making adjustments as appropriate, the IFR2 team is working to reach consensus on its Final Report. The Draft Report included two recommendations that will amend the IANA Naming Function Contract; neither recommendation received objections during the public comment period. However, Section 18.6 (b) of the Bylaws reads that any recommendations by the IFR that would amend the IANA Naming Function Contract shall only become effective if: (i) The IFR Recommendation has been approved by the vote of (A) a supermajority of the ccNSO Council (pursuant to the ccNSO's procedures or, if such procedures do not define a supermajority, two-thirds (2/3) of the ccNSO Council's members) and (B) a GNSO Supermajority;” Here, the Council will hear an update on the status of the IFR2 Report and expected next steps from the GNSO Council. 5.1 - Introduction of Topic (Ashley Heineman and Peter Koch, IFR2 Co-Chairs) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work (15 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 will soon be sending the threshold questions to the GNSO Council for further guidance. The threshold questions currently under discussion 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? 1. 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? Here, the Council will receive an update on the anticipated timeline of work for the Council. 6.1 - Introduction of Topic (Paul McGrady, GNSO Council Liaison to the PPSAI IRT) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL UPDATE: GNSO Council Small Team on Accuracy Draft Report (10 minutes) During the Council’s March 2025 meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the Council agreed to form a dedicated small team on accuracy, which would be tasked with: * Reviewing the written input received on the Council’s threshold questions; and * Providing a detailed summary of the input received, taking into consideration the potential other sources that can inform the discussion - i.e. (but not limited to) INFERMAL study, EU NIS2 cooperation group, recommendation CC.1, and provide a recommendation to the Council on how to best make progress on the topic of registration data accuracy, e.g., relaunch scoping team with updated assignment, request Issues Report, request additional study (including the recommended form and aim of the study), etc. The Small Team, led by Paul McGrady, began meeting on 15 May 2025 and has been drafting recommendations for the Council’s consideration related to: * Examining the current timeline for validation and verification of registration data under the 2024 RAA * Assembling a diverse and representative group of interested stakeholders who could work together on producing clear and user-friendly registrant educational materials related to the importance of accurate registration data * Further work on a previously-approved Whois2 Review Team recommendation (CC.1) related to the inclusion of a notation in the RDDS record that the domain name is suspended due to incorrect data Here, the Council will discuss the Small Team’s draft report in preparation for acceptance during its August meeting. 7.1 - Introduction of Topic (Paul McGrady, Small Team Lead) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE: GNSO Council Small Team on DNS Abuse (10 minutes) The Council’s small team on DNS abuse began meeting on 15 May 2025, working on its Assignment Form<https://gnso.icann.org/sites/default/files/policy/2025/draft/assignment-for…>. The assignment form includes the review and analysis of DNS Abuse mitigation efforts across the broader ICANN ecosystem, the impact of the RA and RAA amendments, the INFERMAL study, as well as other data sources. The goal of the small team was to determine, after reviewing available data sources, whether or not gaps remain in mitigating DNS abuse. The small team quickly came to the conclusion that there are indeed gaps remaining and have worked diligently to catalogue the issues. In developing that catalogue of issues, the small team also solicited input from SG/C/SO/ACs. The small team expects to put forward a recommendation to the GNSO Council that an Issue Report be requested during its August meeting, based upon the catalogue of issues the small team has developed. Here, the Council will be provided with an overview of the small team’s progress, including a high-level understanding of the catalogue of issues that are envisioned to be analyzed in the Issue Report; the purpose of this update is to better ensure that the Council is able to vote to request the Issue Report in August. 8.1 - Introduction of Topic (Jennifer Chung, Small Team Lead) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Any Other Business (15 minutes) 9.1 - ccNSO Council Update (Desiree Miloshevic) 9.2 - Customer Standing Committee (CSC) Effectiveness Review Deferral 9.3 - Celebration of Greg DiBiase, Outgoing GNSO Chair _______________________________ 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/58frfr46 ****** **Updated agenda GNSO Council Agenda 10 July 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/4KefBg 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, 10 July 2025 at 13:00 UTC: https://tinyurl.com/58frfr46 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 [Published 24 hours prior to meeting]: https://icann83.sched.com/event/246XL/gnso-council-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: 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 15 May 2025 were posted on 02 June 2025. Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 11 June 2025 were posted on 30 June 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: Consent Agenda (5 minutes) * Confirmation of the GNSO-appointed Member for the Universal Acceptance (UA) Expert Working Group (EWG) * GNSO Council Review of GAC Communiqué Item 4: COUNCIL VOTE - GNSO Support - Community Reconsideration Supporting Decisional Participant (15 minutes) On 19 June 2025, the ALAC initiated a petition<https://www.icann.org/en/system/files/correspondence/alac-to-eca-19jun25-en…> for an Empowered Community (EC) Request for Reconsideration related to the ICANN Board’s resolution<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> related to ICANN’s Reviews Program. According to ICANN’s Bylaws Annex D, Section 4.3, the GNSO as a Decision Participant has 21 days to decide if it supports the request. This Council Vote item was not originally included in this agenda and as such, did not meet the motion submission deadline (i.e., 10 calendar days before the GNSO Council meeting). As such, it is subject to the procedures detailed in section 3.3.2 of the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> (emphasis added). a. The motion (including any report or other supporting documentation) is submitted to the GNSO Council at least 24 hours in advance of the GNSO Council meeting; b. The motion is accompanied by a request to consider the motion despite submission after the Submission Deadline (a “Request for Consideration”); c. A vote on the Request for Consideration shall be called as the first order of business for the agenda item that deals with the motion. The vote on the Request for Consideration must be unanimous (i.e., all Councilors or their proxies must vote and all votes cast must be in favor of considering the motion at such GNSO Council meeting) for the motion to be considered at such GNSO Council meeting. Here, if the Request for Consideration passes, the Council will vote to determine whether it wishes to support the ALAC’s Community Reconsideration Request. 4.1 - Presentation of motion<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…> (Susan Payne, IPC Councilor) 4.2 - Council discussion 4.3 - Council vote (voting threshold: simple majority) Item 5: Board deferral of Bylaws-mandated Reviews and steps needed for Community Input (25 minutes) On 27 May 2025<https://www.icann.org/en/system/files/correspondence/sinha-to-holen-et-al-2…>, the Board wrote to SO/AC Leaders with an update on the ICANN Reviews. Specifically, following input from the community, the Board informed SO/AC leaders that it took the following actions related to reviews during its 19 May meeting: 1. Continue the deferral of Organizational Reviews until the completion of one CIP cycle (estimated at 3 years). 2. Conclude the Pilot Holistic Review and following the completion of the CIP cycle, consider whether to rename and re-charter an effort focused solely on designing a review of the CIP. 3. Continue the community dialogue to support a broader discussion on reviews. This will include an engagement session at ICANN84 focused on the purpose and essential subject areas for reviews. 4. Continue the deferral of the fourth Accountability and Transparency Review (ATRT4) to support the community’s capacity to participate in the dialogues, and any related activities that may result from such discussions. Please see the relevant Board Resolution<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> for further information. During its May meeting, the Council had agreed to send correspondence to the Board, sharing its thoughts on next steps for ICANN Reviews. With the Board’s suggested approach generally in line with sentiments shared during the Council’s May meeting, it seems that circumstances may have overtaken the need to send correspondence in the context of that action item. During ICANN83, the SO/AC Chairs met with ICANN org to discuss a potential path forward. During the Council’s Wrap-Up<https://icann83.sched.com/event/246XW/gnso-council-wrap-up> session, GNSO Chair Greg DiBiase shared a high-level overview of that approach, asking that Councilors begin socializing the approach with their respective groups. Additional options were subsequently circulated to the GNSO Council. Here, the Council will continue its discussion from ICANN83, discuss feedback from SG/Cs on the potential options, and determine next steps (e.g., send correspondence to the ICANN Board regarding any input the Council may have). 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL BRIEFING - Second IANA Naming Function Review Team (IFR2) Draft Report (20 minutes) The IANA Naming Function Review is an accountability mechanism created as part of the Internet Assigned Numbers Authority (IANA) stewardship transition to ensure that ICANN’s IANA work through Public Technical Identifiers (PTI) meets the needs and expectations of its naming customers. Under the ICANN Bylaws, the ICANN Board must convene an IFR no less frequently than every five years, measured from the date the previous IFR was convened. The board convened<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> the first IFR on 16 September 2018. The second IFR team (IFR2) conducted the review in accordance with the scope specified in the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en/#article18>. The review focuses on PTI’s performance of the IANA naming function against the contractual requirements in the IANA Naming Function Contract and the IANA Naming Function Statement of Work<https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30s…>. The naming functions under review include management of the DNS root zone, a critical function for the ongoing operation of the Internet. The IFR2 recently sought public comments<https://www.icann.org/en/public-comment/proceeding/second-iana-naming-funct…> on its Draft Report, which contained findings and recommendations in three key areas: * Presence of specific Domain Name System Security Extensions (DNSSEC) policy details in the IANA Naming Function Contract * Transparency and availability of Contract amendments * Frequency of reviews After considering public comment received and making adjustments as appropriate, the IFR2 team is working to reach consensus on its Final Report. The Draft Report included two recommendations that will amend the IANA Naming Function Contract; neither recommendation received objections during the public comment period. However, Section 18.6 (b) of the Bylaws reads that any recommendations by the IFR that would amend the IANA Naming Function Contract shall only become effective if: (i) The IFR Recommendation has been approved by the vote of (A) a supermajority of the ccNSO Council (pursuant to the ccNSO's procedures or, if such procedures do not define a supermajority, two-thirds (2/3) of the ccNSO Council's members) and (B) a GNSO Supermajority;” Here, the Council will hear an update on the status of the IFR2 Report and expected next steps from the GNSO Council. 6.1 - Introduction of Topic (Ashley Heineman and Peter Koch, IFR2 Co-Chairs) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work (15 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 will soon be sending the threshold questions to the GNSO Council for further guidance. The threshold questions currently under discussion 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: a. Can an implementation model without a new standalone accreditation program remain consistent with the policy recommendations? 1. Disclosure Frameworks (Intellectual Property and Law Enforcement) a. Are there specific areas to revisit under new law/policy? b. 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? Here, the Council will receive an update on the anticipated timeline of work for the Council. 7.1 - Introduction of Topic (Paul McGrady, GNSO Council Liaison to the PPSAI IRT) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE: GNSO Council Small Team on Accuracy Draft Report (10 minutes) During the Council’s March 2025 meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the Council agreed to form a dedicated small team on accuracy, which would be tasked with: * Reviewing the written input received on the Council’s threshold questions; and * Providing a detailed summary of the input received, taking into consideration the potential other sources that can inform the discussion - i.e. (but not limited to) INFERMAL study, EU NIS2 cooperation group, recommendation CC.1, and provide a recommendation to the Council on how to best make progress on the topic of registration data accuracy, e.g., relaunch scoping team with updated assignment, request Issues Report, request additional study (including the recommended form and aim of the study), etc. The Small Team, led by Paul McGrady, began meeting on 15 May 2025 and has been drafting recommendations for the Council’s consideration related to: * Examining the current timeline for validation and verification of registration data under the 2024 RAA * Assembling a diverse and representative group of interested stakeholders who could work together on producing clear and user-friendly registrant educational materials related to the importance of accurate registration data * Further work on a previously-approved Whois2 Review Team recommendation (CC.1) related to the inclusion of a notation in the RDDS record that the domain name is suspended due to incorrect data Here, the Council will discuss the Small Team’s draft report in preparation for acceptance during its August meeting. 8.1 - Introduction of Topic (Paul McGrady, Small Team Lead) 8.2 - Council Discussion 8.3 - Next Steps Item 9: COUNCIL UPDATE: GNSO Council Small Team on DNS Abuse (10 minutes) The Council’s small team on DNS abuse began meeting on 15 May 2025, working on its Assignment Form<https://gnso.icann.org/sites/default/files/policy/2025/draft/assignment-for…>. The assignment form includes the review and analysis of DNS Abuse mitigation efforts across the broader ICANN ecosystem, the impact of the RA and RAA amendments, the INFERMAL study, as well as other data sources. The goal of the small team was to determine, after reviewing available data sources, whether or not gaps remain in mitigating DNS abuse. The small team quickly came to the conclusion that there are indeed gaps remaining and have worked diligently to catalogue the issues. In developing that catalogue of issues, the small team also solicited input from SG/C/SO/ACs. The small team expects to put forward a recommendation to the GNSO Council that an Issue Report be requested during its August meeting, based upon the catalogue of issues the small team has developed. Here, the Council will be provided with an overview of the small team’s progress, including a high-level understanding of the catalogue of issues that are envisioned to be analyzed in the Issue Report; the purpose of this update is to better ensure that the Council is able to vote to request the Issue Report in August. 9.1 - Introduction of Topic (Jennifer Chung, Small Team Lead) 9.2 - Council Discussion 9.3 - Next Steps Item 10: Any Other Business (15 minutes) 10.1 - ccNSO Council Update (Desiree Miloshevic) 10.2 - Customer Standing Committee (CSC) Effectiveness Review Deferral 10.3 - Celebration of Greg DiBiase, Outgoing GNSO Chair _______________________________ 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/58frfr46 Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: Terri Agnew <terri.agnew(a)icann.org> Date: Monday, June 30, 2025 at 3:07 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)icann.org" <liaison6c(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: Proposed Agenda | GNSO Council Meeting | Thursday, 10 July 2025 Dear all, Please find below the agenda for the GNSO Council Meeting on 10 July 2025 at 13:00 UTC This will be posted on the agenda wiki page<https://icann-community.atlassian.net/wiki/x/KKafBg> shortly. Thank you. Kind regards, Terri Policy Team Supporting the GNSO GNSO Council Agenda 10 July 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/4KefBg 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, 10 July 2025 at 13:00 UTC: https://tinyurl.com/58frfr46 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 [Published 24 hours prior to meeting]: https://icann83.sched.com/event/246XL/gnso-council-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: 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 15 May 2025 were posted on 02 June 2025. Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 11 June 2025 were posted on 30 June 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: Consent Agenda (5 minutes) Tomslin * Confirmation of the GNSO-appointed Member for the Universal Acceptance (UA) Expert Working Group (EWG) * GNSO Council Review of GAC Communiqué Item 4: COUNCIL BRIEFING - Second IANA Naming Function Review Team (IFR2) Draft Report (20 minutes) The IANA Naming Function Review is an accountability mechanism created as part of the Internet Assigned Numbers Authority (IANA) stewardship transition to ensure that ICANN’s IANA work through Public Technical Identifiers (PTI) meets the needs and expectations of its naming customers. Under the ICANN Bylaws, the ICANN Board must convene an IFR no less frequently than every five years, measured from the date the previous IFR was convened. The board convened<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> the first IFR on 16 September 2018. The second IFR team (IFR2) conducted the review in accordance with the scope specified in the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en/#article18>. The review focuses on PTI’s performance of the IANA naming function against the contractual requirements in the IANA Naming Function Contract and the IANA Naming Function Statement of Work<https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30s…>. The naming functions under review include management of the DNS root zone, a critical function for the ongoing operation of the Internet. The IFR2 recently sought public comments<https://www.icann.org/en/public-comment/proceeding/second-iana-naming-funct…> on its Draft Report, which contained findings and recommendations in three key areas: * Presence of specific Domain Name System Security Extensions (DNSSEC) policy details in the IANA Naming Function Contract * Transparency and availability of Contract amendments * Frequency of reviews After considering public comment received and making adjustments as appropriate, the IFR2 team is working to reach consensus on its Final Report. The Draft Report included two recommendations that will amend the IANA Naming Function Contract; neither recommendation received objections during the public comment period. However, Section 18.6 (b) of the Bylaws reads that any recommendations by the IFR that would amend the IANA Naming Function Contract shall only become effective if: (i) The IFR Recommendation has been approved by the vote of (A) a supermajority of the ccNSO Council (pursuant to the ccNSO's procedures or, if such procedures do not define a supermajority, two-thirds (2/3) of the ccNSO Council's members) and (B) a GNSO Supermajority;” Here, the Council will hear an update on the status of the IFR2 Report and expected next steps from the GNSO Council. 4.1 - Introduction of Topic (Ashley Heineman and Peter Koch, IFR2 Co-Chairs) 4.2 - Council Discussion 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Outcome of Transfer Policy Review PDP Human Rights Impact Assessment (15 minutes) During its 12 March 2025<https://icann.zoom.us/rec/play/c9JJyD0XyDGkIJUQWGMtr1CETstmof0VoboRyhXT6AAE…> meeting, the GNSO Council voted to approve all 47 recommendations of the Transfer Policy Review Working Group’s Final Report. While the Working Group’s Charter<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/novoa…> did not include a Human Rights Impact Assessment (HRIA), the Council agreed to conduct an HRIA following the vote on the Final Report. Farzaneh Badii, the GNSO Councilor who volunteered to lead the HRIA effort, met with Roger Carney, the chair of the Transfer Policy Review PDP, on 16 April 2025. Farzaneh presented the outcome of the HRIA discussion to the Council during its meeting on 15 May 2025<https://icann.zoom.us/rec/play/Vew12tHCU11uhBpXCbzCcht0hmEzbE14Ollr8GfOcC4-…>. Here, the Council will discuss the outstanding items from the HRIA and determine if further action is needed or if additional items need to be added to the continued discussion of the Council’s prioritization of work. 5.1 - Introduction of Topic (Farzaneh Badii, GNSO Councilor) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work (15 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 will soon be sending the threshold questions to the GNSO Council for further guidance. The threshold questions currently under discussion 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: a. Can an implementation model without a new standalone accreditation program remain consistent with the policy recommendations? 1. Disclosure Frameworks (Intellectual Property and Law Enforcement) a. Are there specific areas to revisit under new law/policy? b. 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? Here, the Council will receive an update on the anticipated timeline of work for the Council. 6.1 - Introduction of Topic (Paul McGrady, GNSO Council Liaison to the PPSAI IRT) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL UPDATE: GNSO Council Small Team on Accuracy Draft Report (10 minutes) During the Council’s March 2025 meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the Council agreed to form a dedicated small team on accuracy, which would be tasked with: * Reviewing the written input received on the Council’s threshold questions; and * Providing a detailed summary of the input received, taking into consideration the potential other sources that can inform the discussion - i.e. (but not limited to) INFERMAL study, EU NIS2 cooperation group, recommendation CC.1, and provide a recommendation to the Council on how to best make progress on the topic of registration data accuracy, e.g., relaunch scoping team with updated assignment, request Issues Report, request additional study (including the recommended form and aim of the study), etc. The Small Team, led by Paul McGrady, began meeting on 15 May 2025 and has been drafting recommendations for the Council’s consideration related to: * Examining the current timeline for validation and verification of registration data under the 2024 RAA * Assembling a diverse and representative group of interested stakeholders who could work together on producing clear and user-friendly registrant educational materials related to the importance of accurate registration data * Further work on a previously-approved Whois2 Review Team recommendation (CC.1) related to the inclusion of a notation in the RDDS record that the domain name is suspended due to incorrect data Here, the Council will discuss the Small Team’s draft report in preparation for acceptance during its August meeting. 7.1 - Introduction of Topic (Paul McGrady, Small Team Lead) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE: GNSO Council Small Team on DNS Abuse (10 minutes) The Council’s small team on DNS abuse began meeting on 15 May 2025, working on its Assignment Form<https://gnso.icann.org/sites/default/files/policy/2025/draft/assignment-for…>. The assignment form includes the review and analysis of DNS Abuse mitigation efforts across the broader ICANN ecosystem, the impact of the RA and RAA amendments, the INFERMAL study, as well as other data sources. The goal of the small team was to determine, after reviewing available data sources, whether or not gaps remain in mitigating DNS abuse. The small team quickly came to the conclusion that there are indeed gaps remaining and have worked diligently to catalogue the issues. In developing that catalogue of issues, the small team also solicited input from SG/C/SO/ACs. The small team expects to put forward a recommendation to the GNSO Council that an Issue Report be requested during its August meeting, based upon the catalogue of issues the small team has developed. Here, the Council will be provided with an overview of the small team’s progress, including a high-level understanding of the catalogue of issues that are envisioned to be analyzed in the Issue Report; the purpose of this update is to better ensure that the Council is able to vote to request the Issue Report in August. 8.1 - Introduction of Topic (Jennifer Chung, Small Team Lead) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Board deferral of Bylaws-mandated Reviews and steps needed for Community Input (25 minutes) On 27 May 2025<https://www.icann.org/en/system/files/correspondence/sinha-to-holen-et-al-2…>, the Board wrote to SO/AC Leaders with an update on the ICANN Reviews. Specifically, following input from the community, the Board informed SO/AC leaders that it took the following actions related to reviews during its 19 May meeting: 1. Continue the deferral of Organizational Reviews until the completion of one CIP cycle (estimated at 3 years). 2. Conclude the Pilot Holistic Review and following the completion of the CIP cycle, consider whether to rename and re-charter an effort focused solely on designing a review of the CIP. 3. Continue the community dialogue to support a broader discussion on reviews. This will include an engagement session at ICANN84 focused on the purpose and essential subject areas for reviews. 4. Continue the deferral of the fourth Accountability and Transparency Review (ATRT4) to support the community’s capacity to participate in the dialogues, and any related activities that may result from such discussions. Please see the relevant Board Resolution<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> for further information. During its May meeting, the Council had agreed to send correspondence to the Board, sharing its thoughts on next steps for ICANN Reviews. With the Board’s suggested approach generally in line with sentiments shared during the Council’s May meeting, it seems that circumstances may have overtaken the need to send correspondence in the context of that action item. During ICANN83, the SO/AC Chairs met with ICANN org to discuss a potential path forward. During the Council’s Wrap-Up<https://icann83.sched.com/event/246XW/gnso-council-wrap-up> session, GNSO Chair Greg DiBiase shared a high-level overview of that approach, asking that Councilors begin socializing the approach with their respective groups. Here, the Council will continue its discussion from ICANN83, discuss feedback from SG/Cs on the suggested approach, if available, and determine next steps. 9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: Any Other Business (15 minutes) 10.1 - ccNSO Council Update (Desiree Miloshevic) 10.2 - Customer Standing Committee (CSC) Effectiveness Review Deferral 10.3 - Celebration of Greg DiBiase, Outgoing GNSO Chair _______________________________ 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/58frfr46

3 2

ALAC’s EC Request Reconsideration.
by Osvaldo Novoa July 9, 2025

July 9, 2025

Dear all, The ISPCP does not support the GNSO signing onto the ALAC Petition as a supporting Decisional Participant. We support ALAC’s view that the Board’s postponement of ATRT4 without a readily defined alternative leaves ICANN Bylaws in limbo for what they relate to specific reviews, and is for that matter unacceptable However, we also consider that the Board’s Rationale for Resolutions 2025.05.19.01 – 2025.05.19.06 in its deferral of ATRT4 remains founded, notably for what relates to community resources, and that withdrawing that decision would only take the Community backward instead of addressing the issue. Withdrawing the deferral would only reinstate the situation that existed before the Pilot Holistic Review without taking into consideration its recognition of the need to review the ICANN structures as a whole Rather than reconsidering the deferral, we would support a time-limited bylaws amendment to initiate a ‘Review of reviews’ to address the issues that were identified in the Board’s resolution, and in particular those stemming from the Pilot Holistic Review’s findings and the need for changes to ICANN's structures. Best regards, Osvaldo

1 0

Please read | Upcoming GNSO Council meeting prep | 10 July 2025 at 13:00 UTC
by Terri Agnew July 9, 2025

July 9, 2025

Dear all, A few reminders of prep for the Council meeting on 10 July 2025 at 13:00 UTC. 1. Have question on prep materials for this meeting? Check out the Council Preparatory Materials Cheat Sheet found here<https://docs.google.com/document/d/1lQ9fqEjD-inZWpni7tx_EKij6_19oGvi/edit?u…>. 1. Question of the month and answer found on materials cheat sheet: How to find out more information on GNSO PDP 3.0 Final Report. 1. All documents mentioned on the Council agenda<https://icann-community.atlassian.net/wiki/x/KKafBg> will be listed on the Document wiki page<https://icann-community.atlassian.net/wiki/x/4KefBg> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio,<https://icann-community.atlassian.net/wiki/x/WQyfBg> in particular the Action Decision Radar<https://icann-community.atlassian.net/wiki/x/cAyfBg> and the Project List<https://icann-community.atlassian.net/wiki/x/ZAyfBg> . 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. We do have votes. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 10 July 2025
by Terri Agnew July 9, 2025

July 9, 2025

Dear all, The GNSO Council meeting is scheduled on Thursday, 10 July 2025 at 13:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> 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/KKafBg Check your time zone: https://tinyurl.com/58frfr46 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/4KefBg> 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

GNSO Council Absence Notification Form: Bruna Martins dos Santos
by Terri Agnew July 9, 2025

July 9, 2025

Full Name of Officer: Rafik Dammak Officer Email Address: Rafik.dammak(a)gmail.com Date Prepared: 09 July 2025 GNSO Organization: Non-Commercial Stakeholder Group Officer Position or Title: Chair Name of Absent Councilor: Bruna Martins dos Santos Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Bruna is attending a conference and might not be able to join Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: To vote on any matter before the council Date upon which the remedy will expire or terminate: 12 July 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. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: Julf Helsingius 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