- Gnso-dnsabuse-pdp - lists.icann.org

Proposed Agenda for 23 March 12:30 UTC
by Feodora Hamza March 21, 2026

March 21, 2026

Dear DNSAM PDP1 WG, Please find below the proposed agenda for our call on 23 March at 12:30 UTC. Agenda Item Time Welcome * ICANN85 Recap 5min Update on VC Chair Selection Procedure 5min Introduction of WG members * Name and Affiliation * One sentence on background/expertise * One sentence on “Why am I here?” 30 - 40min Update on Process for Review of workplan 20min Continue Deliberations – Charter Q1 20 - 30min AOB 5min Please note that later today you should receive further information/material regarding the Workplan and collaboration document (strawman document) for the WG deliberations. Thank you. Kind regards, Feodora

3 2

DNS Abuse Mitigation PDP1 WG
by ICANN Policy Calendar March 20, 2026

March 20, 2026

MEETING: DNS Abuse Mitigation PDP1 WG DATE/TIME: Weekly on Mondays at 12:30 UTC for 90 minutes, 23 March – 01 June 2026 Join from PC, Mac, iPad, or Android Zoom webinar: https://icann.zoom.us/j/91807711636?pwd=q6XCt8cWQU9m3fGgSojQ5X07pbnX6a.1 Passcode:+X8RaawVrW Phone one-tap: +13126266799,,91807711636#,,,,*0006343077# US (Chicago) +13462487799,,91807711636#,,,,*0006343077# US (Houston) Webinar ID: 918 0771 1636 Passcode: 0006343077 International numbers available: https://icann.zoom.us/u/a9jfXWLB8 ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…>, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ * Time Zone conversion (23 March): https://tinyurl.com/u3m4kuzv

1 0

Update regarding DNSAM PDP1 Leadership
by Feodora Hamza March 19, 2026

March 19, 2026

Dear DNSAM PDP 1 WG, During the GNSO Council meeting held on 9 March 2026 at ICANN85 the GNSO Council confirmed the nomination of Paul McGrady to serve as the DNS Abuse Mitigation PDP1 WG Chair. You may find the corresponding motion and the resulting resolution published below. * Motion: https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages… * Resolution: https://gnso.icann.org/sites/default/files/policy/2026/vote-result/gnso-cou… Kind regards, Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Notes and Action Items from ICANN85- DNS Abuse Mitigation PDP1
by Feodora Hamza March 17, 2026

March 17, 2026

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: * The VC Vote/Selection * The Work Plan * Agenda for 23 March * Working Documents 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]<https://urldefense.com/v3/__https:/nj88a9rab.cc.rs6.net/tn.jsp?f=001Qgz0GLV…>,Session Two [nj88a9rab.cc.rs6.net]<https://urldefense.com/v3/__https:/nj88a9rab.cc.rs6.net/tn.jsp?f=001Qgz0GLV…>, Session Three [nj88a9rab.cc.rs6.net]<https://urldefense.com/v3/__https:/nj88a9rab.cc.rs6.net/tn.jsp?f=001Qgz0GLV…>, and Session Four [nj88a9rab.cc.rs6.net]<https://urldefense.com/v3/__https:/nj88a9rab.cc.rs6.net/tn.jsp?f=001Qgz0GLV…> 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<https://gnso.icann.org/sites/default/files/policy/2026/draft/charter-dns-ab…> • DNSAM PDP1 Wiki<https://icann-community.atlassian.net/wiki/spaces/DAMP1/overview?homepageId…> 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.»

4 5

Re: Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Monday, 23 March 2026
by Eberhard W Lisse March 12, 2026

March 12, 2026

Thank you, please do not remove the main mailing list from correspondence. el -- Sent from my iPhone On Mar 12, 2026 at 11:18 +0530, Terri Agnew <terri.agnew(a)icann.org>, wrote: > Hello, > > Removed main mailing list. > > We have noted your tentative apologies ( in case of connectivity issues) on the wiki agenda page. If we see you join, will adjust. > > Thank you. > > Kind regards, > > Terri > Policy Team Supporting the GNSO > > > From: Eberhard W Lisse <el(a)lisse.na> > Date: Wednesday, March 11, 2026 at 11:43 PM > To: Julie Bisland <julie.bisland(a)icann.org>, ""gnso-dnsabuse-pdp(a)icann.org"" <gnso-dnsabuse-pdp(a)icann.org> > Cc: GNSO-Secs <gnso-secs(a)icann.org> > Subject: Re: [Gnso-dnsabuse-pdp] Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Monday, 23 March 2026 > > I will be in transit but should be in a vehicle with car play so will almost certainly check in. > > el > > -- > Sent from my iPhone > On Mar 11, 2026 at 22:01 +0530, Julie Bisland via Gnso-dnsabuse-pdp <gnso-dnsabuse-pdp(a)icann.org>, wrote: > > > Dear all, > > > > The DNS Abuse Mitigation PDP1 WG call will take place on Monday, 23 March 2026 at 12:30 UTC for 90 minutes. > > > > Join from PC, Mac, iPad, or Android - Zoom Webinar: > > https://icann.zoom.us/j/91807711636?pwd=q6XCt8cWQU9m3fGgSojQ5X07pbnX6a.1 > > Passcode:+X8RaawVrW > > > > Phone one-tap: > > +13126266799,,91807711636#,,,,*0006343077# US (Chicago) > > +13462487799,,91807711636#,,,,*0006343077# US (Houston) > > > > Webinar ID: 918 0771 1636 > > Passcode: 0006343077 > > International numbers available: https://icann.zoom.us/u/a9jfXWLB8 > > > > ALL: Before joining the call > > > > • Please send apologies to gnso-secs(a)icann.org only > > • Please be sure you have read the ICANN Expected Standards of Behavior, the ICANN Community Anti-Harassment Policy, and the ICANN Community Participant Code of Conduct. > > • 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ > > • Time Zone conversion (23 March): https://tinyurl.com/u3m4kuzv > > > > > > > > > > > > > > > > > > Thank you. > > Kind regards, > > > > Julie > > > > > > > > -- > > Julie Bisland > > Policy Operations Analyst (GNSO) > > Internet Corporation for Assigned Names and Numbers (ICANN) > > > > Find out more about the GNSO by visiting: https://learn.icann.org/ > > Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO > > Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar > > _______________________________________________ > > Gnso-dnsabuse-pdp mailing list -- gnso-dnsabuse-pdp(a)icann.org > > To unsubscribe send an email to gnso-dnsabuse-pdp-leave(a)icann.org

1 0

Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Monday, 23 March 2026
by Julie Bisland March 11, 2026

March 11, 2026

Dear all, The DNS Abuse Mitigation PDP1 WG call will take place on Monday, 23 March 2026 at 12:30 UTC for 90 minutes. Join from PC, Mac, iPad, or Android - Zoom Webinar: https://icann.zoom.us/j/91807711636?pwd=q6XCt8cWQU9m3fGgSojQ5X07pbnX6a.1 Passcode:+X8RaawVrW Phone one-tap: +13126266799,,91807711636#,,,,*0006343077# US (Chicago) +13462487799,,91807711636#,,,,*0006343077# US (Houston) Webinar ID: 918 0771 1636 Passcode: 0006343077 International numbers available: https://icann.zoom.us/u/a9jfXWLB8 ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…>, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ * Time Zone conversion (23 March): https://tinyurl.com/u3m4kuzv Thank you. Kind regards, Julie -- Julie Bisland Policy Operations Analyst (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

2 1

Re: Talking behind my back
by Nitin Walia March 10, 2026

March 10, 2026

Dear Paul, Thanks for the note and for encouraging everyone to think a bit more proactively . I agree that informal exchanges across groups can often help move things forward more efficiently than waiting for formal meetings alone. If we can bring ideas that have already seen some discussion across different stakeholder groups, it may help us focus our efforts on proposals that are both practical and broadly workable . The suggestion to think in terms of recommendations that could translate into clear contractual language is also useful, as it keeps the discussion grounded in what can realistically be implemented . Looking forward to continuing the discussions with colleagues and seeing how we can collectively move this work ahead . Warm RegardsNitin WaliaDirectorData Ingenious Globalnitin(a)data.in | नितिन(a)xn--c2bd1gb.xn--h2brj9c www.data.in--------------------------------------------------------------The content of this email is confidential and intended only for the recipient specified.If you received this message in error, please delete it and inform the sender . From: Paul McGrady via Gnso-dnsabuse-pdp MailId : [153688467]To: "gnso-dnsabuse-pdp(a)icann.org" Subject: [Gnso-dnsabuse-pdp] Talking behind my backDate: 10 Mar 2026 03:57:59 pm Please do! Let&rsquos reach out to each other, cook up solutions, bring ideas to the table (especially those that have been kicked around by more than one group), think in terms of Recommendations that consist of contractual clauses ala Reg. Let&rsquos set the land speed record for PDP completion and set the quality record too. Get creative! Best, Paul PaulMcGrady Partner Elster &amp McGrady 434 Houston St, Suite 261 Nashville, TN 37203 3847 N. Lincoln Avenue Second Floor Chicago, IL 60613 Office Direct: +1 (312) 515-4422 paul(a)elstermcgrady.com www.elstermcgrady.com _______________________________________________ Gnso-dnsabuse-pdp mailing list -- gnso-dnsabuse-pdp(a)icann.org To unsubscribe send an email to gnso-dnsabuse-pdp-leave(a)icann.org Do not Remove:[HID]20260310155759268[-HID] [XGENFOOTER] [-XGENFOOTER]

1 0

Talking behind my back
by Paul McGrady March 10, 2026

March 10, 2026

Please do! Let's reach out to each other, cook up solutions, bring ideas to the table (especially those that have been kicked around by more than one group), think in terms of Recommendations that consist of contractual clauses ala Reg. Let's set the land speed record for PDP completion and set the quality record too. Get creative! Best, Paul [cid:image001.png@01DCB0A6.93F3A430] Paul McGrady Partner Elster & McGrady 434 Houston St, Suite 261 Nashville, TN 37203 3847 N. Lincoln Avenue Second Floor Chicago, IL 60613 Office Direct: +1 (312) 515-4422 paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com> www.elstermcgrady.com<http://www.elstermcgrady.com/>

1 0

Fwd: Possible approach to kick off discussions on Associated Domain Checks
by anil Jain March 9, 2026

March 9, 2026

1 0

Possible approach to kick off discussions on Associated Domain Checks
by Volker Greimann March 9, 2026

March 9, 2026

Dear Paul, dear colleagues, During our kick-off meeting, Paul emphasized his preference for keeping our discussions short, meaningful, and focused on practical solutions. I think that is a very helpful framing for this PDP, particularly given the breadth of stakeholders participating in this working group, truly a first in the long chain of PDPs I have participated in over the years. In that spirit, I would like to suggest a possible approach for structuring the early phase of our discussions on Associated Domain Checks (ADC) in a more cooperative spirit. One of the realities that I assume we all recognize is that DNS abuse actors frequently operate across multiple registrars, resellers, and TLDs. Because of this, any meaningful approach to detecting and acting on associated abusive domains that is based on individual parties acting on their own will likely fall short of making a meaningful impact and any ultimately successful effort (however we define success) will likely require contributions from multiple actors in the ecosystem. No single party — whether a registrar, registry operator, reporter, injured party or ICANN itself — is likely to have the full set of data, visibility, or operational tools needed to address the issue on its own. At the same time, this PDP brings together a very wide range of stakeholders: contracted parties, the various ICANN stakeholder groups, advisory committees, and even the ccNSO and GAC are represented in a GNSO PDP in an active role for what appears to me the first time. ICANN Org, Compliance, and others also have a role to play. Each of these groups operates under different mandates, capabilities, and constraints but at the same time has a unique view on the issue and unique skills and information that when put together can be bigger than the sum of its parts. Given that diversity, early discussions in policy processes can sometimes gravitate toward defining obligations for others rather than identifying what each participant can realistically contribute to a solution. With Paul’s goal of solution-oriented discussions in mind, I would therefore like to float a simple procedural idea for the first phase of our work that would run in parallel to the already proposed work track. When done right, this proposal would short-circuit our thinning and let us achieve meaningful progress much faster. So, after this lengthy exposition, here is my proposal: During the first month, starting the day we return from Mumbai, each stakeholder group (or constituency, if that is more practical), as well as associated participants, including ICANN org, would be invited to develop a short strawman proposal describing how ADC could work — with one important constraint: the proposal should focus exclusively on what that group itself could bring to the table. In other words, rather than framing proposals around “others should do X,” the framing would be “this is what we could do.” To keep the exercise focused and productive, these strawman proposals would ideally avoid outlining desired outcomes or wish lists for the broader system, and instead remain tightly focused on potential contributions and capabilities of each group of interested parties. The intention would be to achieve three things right off the bat: • Start from capabilities rather than obligations. By identifying what each group can realistically contribute, we may get a clearer picture of the practical building blocks available for ADC approaches. • Encourage a constructive and cooperative tone early in the process. Beginning with “we will” rather than “you must” could help set the stage for collaborative problem-solving instead of prolonged negotiations. • Create a practical map of available tools and data. Once these strawman contributions are on the table, the working group may be better positioned to identify complementarities and develop workable solution models, and potentially bring in third parties to present their capabilities. Importantly, these initial proposals would not bind anyone to a specific policy position. Their purpose would simply be to seed the discussion and help us understand where meaningful contributions might exist across the ecosystem. Some could execute on the work, some could provide valuable information, some could provide overview, some could provide funding for necessary tool development or platform operations. Some will be better placed than others to contribute, and that is natural given the issues we face, but all in all I believe every single group in this ecosystem has something to give that could be a key element in achieving our mutual goal of reducing DNS abuse. If this exercise works as intended, it might allow us to begin the PDP with exactly the kind of focused, solution-oriented discussion Paul encouraged at the outset. Instead of patching catch-up with the criminals, we would coordinate. Instead of pushing them from platform to platform, we would project a unified front against their actions. I would be very interested to hear whether colleagues think this could be a useful way to get the conversation started. Given the unique composition of this group, I believe we are uniquely placed to tackle this issue from a holistic perspective. I do not wish to hijack the conversation, but I think this could be worth our while and might be worth discussing as a basis for our work. I would be very interested to hear whether colleagues think this could be a useful way to get the conversation started, or how to tweak this proposal to make it workable. Best regards, Volker Greimann, RrSG -- Sincerely, Volker Greimann General Counsel - Registrar Division volker.greimann(a)centralnic.com<mailto:volker.greimann@centralnic.com> Office: +49-172-6367025<tel:+491726367025> Web: www.teaminternet.com<http://www.teaminternet.com> Team Internet Group PLC (AIM:TIG). Registered Office: 4th Floor, Saddlers House, 44 Gutter Lane, London, United Kingdom, EC2V 6BR. Team Internet is a company registered in England and Wales with the company number 8576358.

2 1