Thank you Feodora and staff team for making these corrections and also making sure the references in the Charters reflect the language used in the rest of the Final Issue Report. In light of this, I am suggesting a friendly amendment to the motion I brought to Council to align with this updated corrected language: https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/... (original motion) Specifically in whereas clause 9: 9. Informed by the DNS Abuse Small Team`s recommendations, the Public Comment on the Preliminary Issue Report, the ICANN84 DNS Abuse working sessions, and the clear preference for narrowly scoped Policy Development Processes (PDP), the Final Issue Report recommends separate PDPs on: * Associated Domain Checks: A framework A reactive approach requiring registrars to proactively pivot to investigate domains linked to malicious actors, particularly in cases of high-volume domain registrations used for DNS Abuse campaigns; and, * Safeguards for Application Programming Interface (API) access to new customers: A proactive approach that seeks to introduce friction for new customer accounts, prior to gaining access to high volume registration tools until trust is established. I’ve been advised by staff that procedurally I can also accept this amendment as friendly in this same email, and call for a second for the motion. Many thanks to all! Best, Jen From: Feodora Hamza via council <council@icann.org> Sent: Thursday, December 4, 2025 1:20 PM To: council@icann.org Subject: [council] Re: Final Issue Report on a PDP on DNS Abuse Mitigation Dear Councilors, please find below an updated version/link to the Final Issue Report on DNS Abuse Mitigation. Updates were made to the Annex A and B on the DNS Abuse Mitigation Charters, which included some minor typographical errors and the details of the Working Group representative structure that have been carried over from the Preliminary Issue Report and included in the Charters of Annex A and Annex B. The lack of inclusion of these was a formatting error and this was remedied. Finally, the Charter language of the Associated Domain Checks was updated in Annex A on page 48 as follows: Associated Domain Checks: A framework A reactive approach requiring registrars to proactively pivot to investigate domains linked to malicious actors, particularly in cases of high-volume domain registrations used for DNS Abuse campaigns. * Please utilize the updated link here: https://gnso.icann.org/sites/default/files/policy/2025/draft/issue-report-dn... Kind regards, Feodora on behalf of the Support Team From: Feodora Hamza via council <council@icann.org <mailto:council@icann.org> > Reply to: Feodora Hamza <feodora.hamza@icann.org <mailto:feodora.hamza@icann.org> > Date: Monday, 1 December 2025 at 21:02 To: "council@gnso.icann.org <mailto:council@gnso.icann.org> " <council@gnso.icann.org <mailto:council@gnso.icann.org> > Subject: [council] Final Issue Report on a PDP on DNS Abuse Mitigation Dear GNSO Council, Please find below the link to the Final Issue Report on a PDP on DNS Abuse Mitigation – updated based on the Public Comment received. The most notable change compared to the Preliminary Issue Report is the Annex containing two draft charters starting on page 46. Final Issue Report: https://gnso.icann.org/sites/default/files/policy/2025/draft/issue-report-dn... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> Kind regards, Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: <mailto:feodora.hamza@icann.org> feodora.hamza@icann.org Website: <http://www.icann.org> www.icann.org