2026-05-11 DNS Abuse Mitigation PDP1 WG
The DNS Abuse Mitigation PDP1 WG call will take place on Monday, 11 May 2026 at 12:30 UTC for 90 minutes.
For other places see: https://tinyurl.com/sy6uau4z
PROPOSED AGENDA
Welcome (5min)
PDP Updates (10min)
Start deliberations on CQ5 (35min)
Start deliberations on CQ6 (35min)
AOB (5min)
BACKGROUND DOCUMENTS
PARTICIPATION
Apologies: Paul McGrady
RECORDINGS
Zoom Recording (including audio, visual, rough transcript and chat)
GNSO transcripts are located on the GNSO Calendar
Notes/ Action Items
Action Items:
Staff to provide strawperson language on CQ5 and 6 based on today`s WG discussion.
WG members to review and provide feedback to CQ1-4
Important documents/links:
CollabDoc: https://docs.google.com/document/d/1GxM-Yrgv6sZPEYU8ikW4cRM5YqWsJuWGiQyO39pLqNE/edit?usp=sharing [docs.google.com]
High-Level Notes:
1.Welcome (5min)
Nick Wenban-Smith chaired the meeting,
2.PDP Updates (10min)
Vice Chair presented the path towards ICANN86 and what to expect.
VC shared some best practices when discussing and drafting policy recommendations.
Please provide rationale and alternative language, in case you/your SG cannot live with current draft language.
3.Start deliberations on CQ5 (35min)
WG members noted that ADCs are primarily investigative mechanisms intended to identify related abusive domains, while mitigation actions (such as suspension etc.) fall under existing RAA obligations and are out of scope for this PDP.
WG members noted that a recourse mechanism (outside of current PDP scope) should be added to the list of topics that can be addressed in the future by GNSO Council.
The group discussed whether ADC activities themselves could create adverse impacts for legitimate registrants and what these could be.
WG noted that should ADC have adverse impact on legitimate registrants the PDP should discuss whether remedies exist.
WG members noted existing procedures related to abuse mitigation and registrant protections.
4.Start deliberations on CQ6 (35min)
WG members discussed whether ADC reviews and mitigation actions should be governed by fixed timelines or continue under the existing RAA “promptly” standard.
Many members supported maintaining the existing flexible standard:
They noted DNS abuse cases vary significantly in complexity, urgency, registrar size, and evidentiary requirements.
Members noted that “promptly” already appears multiple times in the RAA and is enforceable through contextual compliance review.
WG members noted potential concerns that rigid deadlines could encourage rushed investigations, false positives, fragmented operational processes, or inconsistent mitigation quality.
Other WG members noted more specific guidance or timelines and pointed out that defined timelines would improve accountability, consistency, and auditability.
5.AOB (5min)