Thanks Jen for sharing this CPH input. Desiree -- On Thursday, 24 July 2025 at 01:50, jen--- via gnso-dnsabuse-smallteam <gnso-dnsabuse-smallteam@icann.org> wrote:
Dear All,
Please find attached the CPH DNS Abuse WG session report and input to further our discussions tomorrow. The report is directed to the GNSO Council, but is relevant to our work. In particular I note that in the last paragraph of the report the CPH DNS Abuse WG has responded to our draft text as follows:
"Finally, the CPH DNS Abuse WG encourages the GNSO Council to start a PDP on DNS Abuse Mitigation by requesting an Issues Report that focuses on one of the preventative measures discussed on this session report: 1) A Requirement to Pivot on Actionable Reports of Malicious Registered Domains, 2) Strengthening of API Clauses to address bulk registrations, and 3) Discussing a gTLD-wide operational and policy framework to mitigate Botnet DGAs at scale."
Best, Jen
-----Original Message----- From: Owen Smigelski owen.smigelski@namecheap.com
Sent: Wednesday, July 23, 2025 7:42 PM To: jen@dot.asia Cc: Elizabeth Bacon beth@pir.org; GNSO-Secs gnso-secs@icann.org
Subject: ICAN83 CPH DNS Abuse Community Update
Hi Jen,
On behalf of the CPH, attached is the "ICANN 83 Session Report: CPH DNS Abuse Community Update” for consideration by the GNSO Council prior to tomorrow’s meeting. Please let us know if you need anything further regarding this update.
Regards,
Owen & Beth
_______________________________________________ gnso-dnsabuse-smallteam mailing list -- gnso-dnsabuse-smallteam@icann.org To unsubscribe send an email to gnso-dnsabuse-smallteam-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.