2026-03-23 DNS Abuse Mitigation PDP1 WG

2026-03-23 DNS Abuse Mitigation PDP1 WG

The DNS Abuse Mitigation PDP1 WG call will take place on Monday, 23 March 2026 at 12:30 UTC for 90 minutes.

For other places see: https://tinyurl.com/u3m4kuzv

PROPOSED AGENDA


  1. Welcome (5 min)

    1. ICANN85 Recap

  2. Update on VC Chair Seelction (5 min)

  3. Introduction of WG members (30 - 40 min)

    1. Name and Affiliation

    2. One sentence on background/expertise

    3. One sentence on “Why am I here?”

  4. Update on Process for Review of workplan (20 min)

  5. Continue Deliberations - Charter Q1 (20-30 min)

  6. AOB (5 min)

BACKGROUND DOCUMENTS


 

 

PARTICIPATION


Apologies: Michaela Shapiro

 

RECORDINGS


Audio Recording

Zoom Recording (including audio, visual, rough transcript and chat)

GNSO transcripts are located on the GNSO Calendar

 

 

Notes/ Action Items


 [OUTCOMES]

  • None 

[ACTION ITEMS]

 

[NOTES] 

  1. Welcome

  • Recapped what took place at ICANN85, including admin activities, reminders on good habits for consensus building, and deliberations on Charter question 1.

 

  1. Update on VC Chair Selection Procedure

  • Considered a number of options and factors but settled on a relatively simple procedure, as laid out in the slide.

 

Action Item: Members and Participants to complete voting by the deadline.

 

  1. Introduction of WG Members

  • Every member, participant, and alternate was invited to discuss 1) their name, role in WG, affiliation 2) background expertise 3) “why am I here”

  • A number of speakers mentioned implementability, pragmatism, enforceability, proportionality, respect for human rights, scalability, and wishing to make a real difference in further mitigating DNS Abuse.

  • Several speakers mentioned that this PDP would be their first ever. Welcome!

 

  1. Update on Workplan Review

  • Paul will be checking participation levels and hopes to see broad participation.

  • Consider whether all emails, like acknowledgments, need to be sent to all on the WG.

  • Reviewed work plan slide, highlighting all of the milestones. Reminded the WG about homework to identify problematic Mondays, to help determine next steps, if any.

  • Reviewed the more detailed work plan on the following slide. The holistic reviews (HRIA, GPI etc.) will be done iteratively along the way, but also robustly once all recommendations are stable.

  • Reviewed the slide with standard PDP steps and timelines, to illustrate that there are a number of required steps that cannot be removed or shortened. The steps within the WG’s direct control are deliberations to get to the Initial Report and consideration of public comment/drafting of Final Report/consensus call.

  • Concern about using LLM over review of the email list, including providing access to data and training LLMs – doing so was not an ICANN-sanctioned activity.

  • Concern about whether Oman will occur and the potential loss of F2F time. And noted that it would be helpful to know when meetings will take place in Seville. Noted that for Seville, the meetings will occur during the regular meeting, not on day zero or earlier.

  • Question about whether sub-tracks may be useful to progress the work more rapidly.

  • Question about what the minimum number of days are, assuming agreement on recommendations on day 1. Clarified that a number of the mandatory steps are already completed – we are currently in the first green, variable box.

  • Offer to liaise with the meetings planning team, especially in relation to Tech Day.

  • Suggestion to consider stress testing the recommendations, when they are closer to stable.

 

Action Item: Staff to send email about work plan: https://docs.google.com/spreadsheets/d/1gDXM13Io8RJlYZVj0rhbfoMi7und3v9i/edit?gid=213156814#gid=213156814 [docs.google.com]

Action Item: WG Members to review work plan and provide feedback by 30 Mar, if any.

 

  1. Continue Deliberation

  • Recap: At ICANNN85, began deliberations for CQ1, including looking at draft RAA text.

  • Reminders about best practices for deliberations, including minding scope, being creative, being iterative, etc.

  • Not in scope: Compromised domains; ADC across Rrs; dictating the types of mitigation actions in the course of an ADC.

  • Reminder that we will need to review the early input carefully – will be put into a digestible format and discussed at a future meeting.

  • Given time, will not start the review of the charter question.

 

Action Item: Staff to send email about collaboration tool, which seeks to capture and distill verbal and email discussions to date. 

  1. AOB

  • None