November 2025 - council - lists.icann.org

RrSG Rationale on vote abstention
by Prudence Malinki Nov. 13, 2025

Nov. 13, 2025

Hello everyone Following our discussion on New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations (30 minutes). Please find the RrSG rationale for the abstention for further consideration. With best regards Prudence Malinki Head of Industry Relations, Markmonitor Skype: Malinkip T +44 207 433 4869 Time zone: GMT/BST [cid:image001.png@01DC54A1.11E59A40]

1 0

FW: Amended IGO/INGO Motion (former Motion 4)
by Susan Payne Nov. 13, 2025

Nov. 13, 2025

Trying again with the correct address Hi colleagues Please find below a redline of the draft Motion (4) on the IGO/INGO issue. The amendments are to remove para 3(f) to address concerns of the RySG. There are a couple of minor clean-ups as well, as you will see. I am hoping that Nacho will support this as a friendly amendment. Would you please seek voting instructions from your groups, we will vote on this on 13 November. Thanks Redline: Council Confirmation of Policy Intent regarding Specific IGO/INGO PDP Recommendations Submitted By: Susan Payne Seconded By: Nacho Amadoz Whereas: 1. In November 2013, the Working Group for the Protection of International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) in All gTLDs completed a Policy Development Process (PDP) and submitted its Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/issues/igo-ingo-final-…> to the GNSO Council; 2. On 20 November 2013, the GNSO Council approved [gnso.icann.org]<https://urldefense.com/v3/__http:/gnso.icann.org/en/council/resolutions*201…> all the consensus recommendations in the PDP Final Report; 3. On 30 April 2014, the ICANN Board approved<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> those of the GNSO's consensus recommendations that were not inconsistent with advice received from the Governmental Advisory Committee (GAC) on the topic of IGO and INGO protections, which recommended top-level protections for specific identifiers associated with the Red Cross Red Crescent Movement and the International Olympic Committee and the full names of specific International Governmental Organizations and International Non-Governmental Organizations "the protected organizations"); 4. In the context of implementing the PDP Recommendations in the Next Round Applicant Guidebook, the implementation staff and the Implementation Review Team (IRT) discussed potential alternatives for the implementation of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP ("the Applicable Recommendations"), the so-called "Options 1 and 2" as set out in the staff briefing [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> but could not reach agreement on which option properly reflects the intent and scope of the protections afforded by the Applicable Recommendations. 5. On 15 September 2025 staff referred this matter to the GNSO Council for guidance on the interpretation of the Applicable Recommendations, as a late addition to the agenda of the GNSO Council meeting on 18 September 2025. 6. On 16 September 2025, the ICANN Board sent correspondence<https://www.icann.org/en/system/files/correspondence/sinha-to-samme-nlar-am…> to the GNSO Council, providing the Board's interpretation of the relevant recommendations, while acknowledging that the decision resides with the Council; 7. The Council discussed the request for guidance during its meeting on 18 September, Extraordinary Meeting on 9 October 2025, and meeting on 29 October 2025; and, 8. The Council has now carefully considered the natural meaning and original intent of Recommendations 3.1.1, 3.1.2, 3.2.1, 3.2.2, 3.3.1, 3.3.2, 3.4.1 and 3.4.2 from the Protection of IGO and INGO in All gTLDs PDP. Resolved: 1. The GNSO Council confirms that the intent of the Applicable Recommendations is only to ensure that no organization other than the protected organization can apply for the exact match of the specific, protected identifier associated with that organization, and that as such, Reserved Name strings are now placed in the category formerly-termed "ineligible for delegation" under paragraph 2.2.1.2.3 of the 2012 Round AGB. Accordingly, the relevant identifiers shall not be included in the String Similarity Evaluation in the New gTLD Program and such a relevant identifier shall not operate as a bar to an application by another applicant for a string that could be considered potentially confusingly similar during that evaluation. Objection proceedings and GAC Advice could still be brought against such a third-party application, where applicable, in the usual manner. Pursuant to existing policy, any application submitted by a protected organization for its protected string would remain subject to existing policy barring delegation if such string is found to be visually-confusingly similar to a string previously delegated. Option 1 would align with this interpretation. 2. The GNSO Council acknowledges that this was a difficult issue. Although the majority support this interpretation as best reflecting the intent of the policy recommendations, which were made more than a decade ago, this view was not unanimous. It is clear that reasonable people can differ as to this intent. 3. The GNSO appreciates the Board's consideration of steps which could be taken to ensure that the protected organizations and GAC are made aware, if any application for a confusingly similar string were to be submitted, as set out in the penultimate paragraph of the Board's letter<https://www.icann.org/en/system/files/correspondence/sinha-to-samme-nlar-am…> of 26 September 2025. The GNSO Council would support and encourage the following steps: a) The application process must prominently display and clearly communicate the Reserved Names list this List so that TLD applicants are fully aware of its existence and implications prior to filing its choice of the TLD string. b) That Org should contact the relevant protected organizations after String Confirmation Day to ensure they are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, and are aware of their options for bringing formal Objection or seeking support of the GAC. c) That Org should also contact the GAC after String Confirmation Day to ensure that the GAC are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, in order that GAC members may consider whether any Early Warning(s) or GAC Consensus Advice would be appropriate. d) We also would encourage the GAC to contact the relevant protected organizations to ensure that they are aware of any the applied-for strings and can decide whether to utilize any challenge methods outlined in the AGB. e) That Org should also notify the applicant of the confusingly similar string, and give them the option to withdraw for an appropriate refund. f) The GNSO Council encourages the Board to ensure that Org puts appropriate mechanisms in place to safeguard the strings on the Reserved Names List, pending the conclusion of the Objection period, the outcome of any filed Objection, the outcome of any GAC Consensus Advice against a confusingly similar string, or confirmation from the GAC that it does not intend to issue Consensus Advice. Such an appropriate mechanism might include placing any confusingly similar application on hold, pending such resolution. 4. If the Board considers it timely for the existing policy to be reviewed, the GNSO Council would invite the Board to request an issues report for further potential policy work which might apply to subsequent future rounds. The GNSO Council assumes that Org would again be instructed to take any steps considered appropriate to safeguard the strings on the Reserved Names List from any confusingly similar applications, which might be submitted in any application round pending the future conclusion of such policy work. Susan Payne Head of Legal Policy [cid:image001.png@01DC4E79.43B0ECB0]<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@01DC4E79.43B0ECB0]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DC4E79.43B0ECB0] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DC4E79.43B0ECB0] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DC4E79.43B0ECB0] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DC4E79.43B0ECB0] ________________________________ 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>

7 30

**Starting in 15 minutes | Meeting Invitation | GNSO Council meeting | Thursday, 13 November 2025
by Terri Agnew Nov. 13, 2025

Nov. 13, 2025

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 13 November 2025 at 13:00 UTC for 60 minutes. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> , ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> and, the Community Participant Code of Conduct Concerning Statement of Interest<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…> Visit the Wiki Agenda page: https://icann-community.atlassian.net/wiki/x/SKafBg Check your time zone: https://tinyurl.com/33sjnctx 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/AKifBg> 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

Motion to commemorate Rubens Kuhl
by jen＠dot.asia Nov. 12, 2025

Nov. 12, 2025

Dear All, As part of our consent agenda, we have a Motion to commemorate Rubens Kuhl, please see the motion submitted below. Many thanks to Seb, staff and ICANN community members for helping put this together. There is no need for a formal second, however we have included it as the entire Council in commemoration and recognition of the deep impact Rubens has left on the entire ICANN community and beyond. Respectfully submitted, Jen --------- Motion to commemorate Rubens Kuhl Proposed: Jennifer Chung Seconded: All members of the GNSO Council The Council was informed earlier this month of Rubens Kuhl's passing. We wish to recognize Ruben's significant contribution to the GNSO and the ICANN multi-stakeholder model during his tenure, as well as his professionalism, his friendship and mentorship to many. He will be greatly missed. Whereas: 1. Rubens Kuhl joined the GNSO Council on 21 October 2015 as an elected representative of the Registries Stakeholder Group from the LAC Region. He served 2 full terms between 2015 and 2019. 2. As GNSO Councilor, Rubens brought his professionalism, his deep knowledge of the GNSO Council's best practices and history, his experienced thoughts on topics, to serve the Registries he represented as well as Council as a whole. 3. Rubens made significant contributions to ICANN and was a strong and respected community participant. During his tenure Rubens participated in: * Activities as Councilor that initiated the EPDP on the Temporary Specification * GNSO Guidance Process (GGP) Initiation Request - Select SubPro Topics (Applicant Support) team. * IDNs Small team * Modifications to GNSO Operating Procedures Relating to Elections and Motions * GNSO Council liaison - Translation & Transliteration of gTLD Registration Data IRT * Discussion Group (DG) - New gTLD Subsequent Procedures * Next-Generation gTLD Registration Directory Services to Replace Whois * New gTLD Subsequent procedures - Work Track 1, Work Track 4 as Co-Leader, Sub Group B, Sub Group C * IDN Scoping Team Rubens was also an active and valuable member of many ICANN initiatives, outside of his service to the GNSO Council, including but not limited to: * Activities as Community participant * PDP Phase I and its IRT * Registration Data Policy Implementation IRT + IPT * GeoTLDs - .rio * ccTLDs - .br, and many Brazilian city campaigns at the second level * Latin American and Caribbean Islands Regional At-Large (LACRALO) * Name Collision analysis Project (NCAP) * New gTLD Applicant Group (NTAG) Executive Committee - Vice Chair * Chairing Skills Program (CSP) * ccNSO IDN Policies Preliminary Review Team (IDN PRT) * RSP Sub-Track * Subsequent Procedures Implement Review and ASP Sub-Track * EPDP Drafting Team * gTLD Marketplace Health Index Advisory Panel * Enhancing ICANN Accountability - Work Stream 2 * New gTLD Subsequent procedures 4. Rubens was a well-respected and much appreciated member of not only the GNSO, the CPH and the Registries, but of the broader ICANN Community. He was a friend and quiet mentor to many who are able to trace back when they first encountered him. 5. Rubens was also an active member of the community of ICANN participants within the LAC region and a representative of NIC.br <http://nic.br> , able to both share the dynamics of the ICANN Community to his region and a Latin American perspective to the ICANN discussion. 6. Rubens' passing is a great loss to the many people across the ICANN community who had the pleasure to work and interact with him, and for his many friends at ICANN the loss is significant. 7. In addition to this devotion and set of accomplishments, Rubens endeared himself to those in the community by his willingness to help others and give unselfishly of his time to teach and mentor others. His work is missed but he is missed more. Resolved: 1. The GNSO Council wishes to recognize the significant contribution Rubens Kuhl made to the GNSO Council and the ICANN Community during his tenure and his achievements during this time. 2. Rubens' presence, professionalism and commitment to the ICANN Community will be dearly missed. 3. On behalf of the current and previous GNSO Councils represented today, we offer our deepest and heartfelt sympathies to his family and friends at this most difficult time.

3 2

Please read | Upcoming GNSO Council meeting prep | 13 November 2025
by Terri Agnew Nov. 12, 2025

Nov. 12, 2025

Dear all, A few reminders of prep for the Council meeting on 13 November 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…>. * Question of the month and answer found on materials cheat sheet: Is there a place to find ICANN Bylaws? 1. All documents mentioned on the Council agenda<https://icann-community.atlassian.net/wiki/x/SKafBg> will be listed on the Document wiki page<https://icann-community.atlassian.net/wiki/x/AKifBg> 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>. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | GNSO Council meeting | Thursday, 13 November 2025
by Terri Agnew Nov. 12, 2025

Nov. 12, 2025

Dear all, The GNSO Council meeting is scheduled on Thursday, 13 November 2025 at 13:00 UTC for 60 minutes. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> , ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> and, the Community Participant Code of Conduct Concerning Statement of Interest<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…> Visit the Wiki Agenda page: https://icann-community.atlassian.net/wiki/x/SKafBg Check your time zone: https://tinyurl.com/33sjnctx 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/AKifBg> 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

Automatic reply: Your subscription for council mailing list has been disabled
by Julie Bisland Nov. 11, 2025

Nov. 11, 2025

I am out of the office on Tuesday, 11 November 2025, returning on Wednesday, 12 November. Please send all GNSO-related requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Thank you. Kind regards, Julie ************** Julie Bisland Policy Operations Analyst (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org>

1 0

Automatic reply: Your subscription for council mailing list has been disabled
by Terri Agnew Nov. 11, 2025

Nov. 11, 2025

Thank you for your email. I am out of office and responses may be delayed. Will be back Wednesday, 12 November 2025. If it is of urgent concern, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Thank you, Terri

1 0

Automatic reply: Your subscription for council mailing list has been disabled
by Devan Reed Nov. 11, 2025

Nov. 11, 2025

Thank you for your email. I am out of office and will return on Wednesday, 12 November 2025. If it is of urgent concern, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> If you need assistance with the ICANN Policy Development Accelerator, please contact carlos.reyes(a)icann.org<mailto:carlos.reyes@icann.org>, daniel.gluck(a)icann.org<mailto:daniel.gluck@icann.org>, and christian.wheeler(a)icann.org<mailto:christian.wheeler@icann.org>. Thank you. Kind regards, Devan Reed

1 0

UPDATE | Proposed Agenda | GNSO Council | Thursday, 13 November 2025
by Terri Agnew Nov. 10, 2025

Nov. 10, 2025

Dear all, The following has been updated on the 13 November GNSO Council agenda, adjusted below and on the wiki page<https://icann-community.atlassian.net/wiki/x/SKafBg>. Removed the following two Items 3: Consent Agenda (5 minutes) * GNSO Council Review of GAC Communiqué * Confirmation of GNSO Empowered Community Representative Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: Devan Reed <devan.reed(a)icann.org> Date: Monday, November 3, 2025 at 3:53 PM To: "council(a)icann.org" <council(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: Proposed Agenda | GNSO Council | Thursday, 13 November 2025 Dear all, Please find below the agenda for the Thursday, 13 November 2025 GNSO Council Meeting at 13:00 UTC. This will be posted on the agenda wiki page<https://icann-community.atlassian.net/wiki/x/SKafBg>. Thank you! Kind regards, Devan GNSO Council Agenda 13 November 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/AKifBg 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, 13 November 2025 at 13:00 UTC: https://tinyurl.com/33sjnctx 05:00 Los Angeles; 08:00 Washington DC; 13:00 London; 14:00 Paris; 16:00 Moscow; 00:00 Melbourne (Friday) GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 18 September 2025 were posted on 02 October 2025. Minutes of the GNSO Council Meeting on 29 October 2025 will be posted on 15 November 2025. Item 2: Opening Remarks / Review of Projects & Action List (5 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) * Motion to commemorate Rubens Kuhl Item 4: COUNCIL VOTE - New gTLD Subsequent Procedures PDP - Interpretation of Intent for Select IGO/INGO PDP Recommendations (30 minutes) During its September meeting<https://icann.zoom.us/rec/play/XYy4NN_IZZv08C-bg6V2CiZv-C_HxrwTqlFeWgVvkHfm…>, the Council discussed an issue that recently arose in the proposed implementation of the Subsequent Procedures PDP recommendations. Specifically, ICANN org staff prepared a discussion paper<https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/460783617> 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. The Council has discussed the issue during the September meeting, during an Extraordinary Meeting, and during the October meeting. During the October meeting, the Council had four different motions to consider, but were set to consider a motion that confirmed the intent of option 1, but encouraged a number of mitigatory actions as suggested in the Board’s letter to the Council on this issue. That motion, along with the three others that remain submitted, were deferred during the October meeting. Here, the Council will vote on the interpretation of the original intent. 4.1 - Introduction of Topic (Susan Payne, GNSO Chair) 4.2 - Council Vote 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Final Issue Report on a Policy Development Process for DNS Abuse (25 minutes) On <https://urldefense.com/v3/__https:/gac.icann.org/contentMigrated/gac-follow…> 14 August 2025<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the GNSO Council passed a motion, requesting ICANN’s Policy Support Staff to draft a Preliminary Issue Report on DNS Abuse. The objective of the Preliminary Issue Report was for Policy Support Staff to assess all relevant issues related to the GNSO Council request and, following Community Input during the Public Comment phase, to recommend a course of action to the GNSO Council. It remains the GNSO Council’s prerogative to either follow Support Staff’s recommendations or to pursue alternative action. As background, in early 2025, the GNSO Council reconvened its DNS Abuse Small Team to re-examine DNS Abuse mitigation considering new developments, research, and data. Based on data analysis, community consultation, and input from stakeholder groups (SGs), the Small Team recommended the following three gaps be prioritized for policy work in the Issue Report: 1. Unrestricted Application Programming Interface (API) access for domain name registration for new customers 2. Associated Domain Checks: Malicious domains are often part of broader campaigns involving dozens or hundreds of related domains. 3. Limited coordination on Domain Generation Algorithm (DGA)-based abuse: The Preliminary Issue Report concludes that all of the three identified priority issues are appropriate for policy development. However, the paper suggests that only two of the three identified DNS Abuse issues should be prioritized for policy development, while one may be addressed more directly and expeditiously outside of the ICANN policy development process. The Preliminary Issue Report was published for public comment and the GNSO conducted a working session on DNS Abuse at ICANN84; the Final Issue Report and the included draft PDP charter will be adjusted to take into account feedback received from both of these sources. Here, the Council will receive an overview of the anticipated changes to the Final Issue Report on DNS Abuse to inform its decision of whether or not to initiate a PDP at its upcoming meeting in December. 5.1 - Introduction of Topic (Jennifer Chung, GNSO Vice-Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Registration Data Request Service (RDRS) Standing Committee Findings Report (25 minutes) In June 2023, the GNSO Council approved a Charter for the Registration Data Request Service Standing Committee, which outlines the Standing Committee’s tasks. Specifically, the Standing Committee was tasked to review the data that will be produced by ICANN org on a monthly basis following the launch of the RDRS (see data points outlined here). The Scoping Team was expected to analyze the data and consider: * Assignment #1. Trends that can be identified over a month-by-month period; * Assignment #2. Possible technical updates that should be considered to RDRS and/or related messaging and promotion (recognizing that the RDRS will only be running for a two-year period and limited resources may be available to implement such updates); * Assignment #3. Specific lessons learned that should be factored into the consideration of how to proceed with the SSAD recommendations; * Assignment #4. Suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations. The Standing Committee began reviewing monthly data since the inception of the RDRS in November 2023 and distilled its findings into its Findings Report, which was published for public comment on 19 August 2025<https://www.icann.org/en/announcements/details/icann-generic-names-supporti…>. Following its consideration of the public comments received, the RDRS Standing Committee delivered its updated Findings Report, which contains six recommendations for the Council’s consideration. 6.1 - Introduction of Topic (Sebastien Ducos, RDRS Standing Committee Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - GNSO Liaison to the Governmental Advisory Committee (GAC) Annual Report (15 minutes) The GNSO Liaison to the GAC role was first piloted from 1 July 2014 to 30 June 2016 as part of a broader initiative of the GAC-GNSO Consultation Group to facilitate early engagement of the GAC in GNSO policy development activities. Due to the success of the pilot, the GNSO Liaison to the GAC is now a permanent role and an integral part of communications between the GAC and GNSO. The Liaison is primarily responsible for providing timely updates to the GAC on GNSO policy development activities in order to complement the existing notification processes; the Liaison is also a resource for answering questions in relation to these (GNSO) activities that GAC members may have. Furthermore, the Liaison is responsible for providing the GNSO Council with regular updates on progress, including on GAC activities, specifically in so far as these relate to issues of interest to the GNSO. The objective of the liaison mechanism, in combination with other mechanisms and early engagement tools, is to facilitate effective early engagement of the GAC and assist with the flow of information between the GAC and the GNSO. The Liaison is responsible for delivering to the Council an annual report<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/neuma…>, which includes updates on relevant engagement activities and progress. Here, the Council will receive a presentation on the annual report from the Liaison. 7.1 - Introduction of Topic (Sebastien Ducos, GNSO Council Liaison to the GAC) 7.2 - Council Discussion 7.3 - Next Steps Item 8: Any Other Business (10 minutes) 8.1 - SPS Planning 8.2 - Next steps - Expiration Policies _______________________________ 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 November and March 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 05:00 San José, Costa Rica (CST) UTC-6 07:00 New York/Washington DC, USA (EST) UTC-5 08:00 Buenos Aires, Argentina (ART) UTC-3 10:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 14:00 Paris, France (CET) UTC+1 14:00 Moscow, Russia (MSK) UTC+3 16:00 Singapore (SGT) UTC+8 21:00 Melbourne, Australia (AEDT) UTC+11 00:00 (Friday) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/33sjnctx

1 0