Dear DNSAM (DNS Abuse Mitigation) PDP1 WG,
Please find below the high-level notes and takeaways from the four ICANN85 sessions on DNS Abuse, as well as the action items.
Our next meeting is scheduled for 23 March 12:30 UTC.
As noted in the Action Items, in the coming days you will receive more information regarding:
For now, please take a look at the notes and action items below. We would like to emphasize, that notes will be kept at a high-level and do not replace each members
responsibility to check the recordings in case a working session could not be attended.
Kind regards,
Feodora on behalf of the Support Staff
Main Takeaways and Action Items – DNSAM PDP1 – ICANN85 Working Sessions
These sessions took place from Saturday, 7 March, through
Monday,
9 March. If you missed them or want to review, visit the session pages for
Session
One [nj88a9rab.cc.rs6.net],Session
Two [nj88a9rab.cc.rs6.net],
Session
Three [nj88a9rab.cc.rs6.net], and
Session
Four [nj88a9rab.cc.rs6.net] to view the available session materials and recordings.
Action Items
1.
Staff to Send ranked choice poll to working group members after ICANN85
for VC selection.
2.
Community groups to submit
early
input on charter
by March 20.
Reminder was sent last week. This is optional.
3.
Support Staff to distribute the draft work plan
to the working group for review.
4.
Working group to provide feedback and adjustments (if any) at the next meeting.
6.
Support Staff to share draft language in shared
working documents to allow asynchronous work.
See Reg`s initial proposal.
Important documents/links:
•
Charter
Main takeaways Session1:
•
The DNS Abuse Mitigation PDP1 had four sessions during ICANN85.
•
The first sessions aimed to establish a baseline of common understanding and cover administrative and procedural matters before substantive
policy work begins.
•
The purpose of the PDP is to consider new requirements for registrars to proactively check associated domains,
once a malicious domain has been confirmed as being used for DNS Abuse.
•
Meeting Cadence: One 90-minute meeting per week-
Mondays 12:30 UTC
•
Conditions for making this feasible: Avoid repetitive statements and “pontification.”
Commit to asynchronous work between meetings.
•
If progress slows due to inefficiency:
Additional meetings may be added.
Main Takeaways Session2:
•
Session 2 focused on what the working group should consider when wanting to reach consensus and how participants should work together during
the PDP.
•
The session revisited the Consensus Playbook, facilitated by Toby Berkman (Consensus Building Institute), who helped develop it.
•
The goal was to reinforce constructive engagement, efficiency, and a shared understanding of the deliberation process.
Main takeaways Session 3:
•
Session 3 focused on understanding how associated domain checks are currently conducted in practice
and voluntarily by some Rrs.
•
The session was designed to inform the working group, not to advocate for any specific method.
•
Presentations were delivered by subject matter experts (SMEs) representing different registrar business models and perspectives.
•
The session emphasized that no decisions would be made; it was intended purely for education and context building.
Main takeaways Session 4:
Session 4 marked the start of substantive PDP work.
•
The working group moved from informational sessions to addressing charter questions.
•
The discussion focused on:
·
scope of the PDP
·
working methodology
·
discussion of Charter Question 1
•
Charter Question 1: What triggers the requirement to investigate associated domain names?
•
WG Members discussed different trigger models and considerations. WG members also provided some draft language to be considered for the WG during
the next meeting.
•
The chair emphasized that the charter defines the boundaries of the PDP, and discussions must remain within that scope.
•
Draft Language provided by WG members
based on discussion: «When
a registrar takes action under Section 3.18 of the Registrar Accreditation Agreement, the registrar shall promptly review other domains that are reasonably associated with that domain when there are clear indicators that other domains registered by the same
customer may be involved in the same abusive activity, using information reasonably available to the registrar at the time of review, and take action against those domains where appropriate.»