June 2026 - Gnso-dnsabuse-pdp

High-level notes and Action Items DNSAM PDP1 22June 12:30UTC
by Feodora Hamza June 22, 2026

June 22, 2026

Dear DNSAM PDP1, Please find below the high-level notes and action items from today’s session. Our next meeting is scheduled for Monday, 29 June at 12:30 UTC. Kind regards, Feodora on behalf of Support Staff 2026-06-22 DNS Abuse Mitigation PDP1 WG<https://icann-community.atlassian.net/wiki/spaces/DAMP1/pages/1001553921/20…> Action Items: 1. Staff to begin populating the Initial Report and update preliminary recommendations based on today’s discussion and share for WG review. 2. WG members to provide alternative language to pending “CANNOT LIVE WITH ITEMS” where relevant. Important Docs/links: * Session Link: https://icann-community.atlassian.net/wiki/spaces/DAMP1/pages/1001553921/20… * Prelim Rec Review Doc: https://docs.google.com/document/d/1udLt1o9rwCc4xNRsuw6B-5onjpI63VDA/edit?u… High-Level notes: 1. Welcome (5min) 2. PDP Updates (10min) * Preliminary Recommendation 7 (List of Topics to Council) has been removed. Instead, a separate document will be shared with Council via Council Liaison listing all topics for further consideration. * These items are not being negotiated as policy recommendations. * The purpose is to inform Council of issues that emerged during PDP deliberations. * Staff to prepare a more structured document for working group review. * Relevant groups to provide additional rationale where needed to allow for Council to better understand the issue and why this is being proposed for further consideration. * Initial Update to be provided to Council at the July meeting. 1. Update on pending “CANNOT LIVE WITH” items (60min) * Discussion on GAC raised concern regarding past and future abuse to be considered when conducting ADC. * WG members welcomed the effort and requested additional explanation of proposed recommendation changes. * Some members questioned whether the proposed language is logically consistent with existing mitigation obligations. * WG members explained the intent is to allow ADCs based on evidence of past or intermittent abuse without creating new mitigation obligations. * General support for addressing intermittent abuse scenarios. * Staff and leadership to develop synthesis language combining proposals and discussion points. * Staff to produce revised consolidated text for review. * IPC requested that the definition of "reasonably accessible data" be moved from implementation guidance into the recommendation text itself. * IPC and Registrars held bilateral discussions. * Additional registrar text proposal expected. * Parties agreed further discussion is needed before resolution. * NCSG sought clarification that an ADC should not be interpreted as a broad audit or unrestricted review of all domains associated with a registrant. * Proposed WG Language: ADCs should remain evidence-driven and proportionate. * WG members supported retaining the principle of proportionality, but update IG to provide some baseline understanding of “proportionate”. * WG members agreed that "audit" is not the preferred term and that "review" better reflects intended practice. * Discussion focused on what records registrars should maintain to demonstrate ADC compliance. * Some WG members argued that some record must exist showing what an ADC consisted of or otherwise compliance cannot be assessed. * WG members noted against requirements that would create extensive new logging or tracking systems. 1. Next steps on Initial Report (10min) 2. AOB (5min)

1 0

Post Call / DNS Abuse Mitigation PDP1 WG / Monday, 22 June 2026
by Julie Bisland June 22, 2026

June 22, 2026

Dear all, All recordings for the DNS Abuse Mitigation PDP1 WG call held on Monday, 22 June 2026 at 12:30 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AYCyOw> (attendance included), which can also be accessed via the GNSO Master calendar<https://gnso.icann.org/en/group-activities/calendar/2026>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat) * Transcript * Agenda and Notes/Action Items For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-dnsabuse-pdp@icann.org/> and the main wiki page<https://icann-community.atlassian.net/wiki/x/zoKmLQ>. Thank you. With 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…>

1 0

Meeting Invitation | DNS Abuse Mitigation PDP1 WG | Monday, 29 June 2026
by Julie Bisland June 22, 2026

June 22, 2026

Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Monday, 29 June 2026 at 12:30 UTC for 90 minutes. 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 * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only (members: please include if an alternate is joining on your behalf) * 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…>. * Staff will promote members, participants, and alternates to panelist once joined. OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. 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…>

1 0

**15-MINUTE REMINDER** Meeting Invitation | DNS Abuse Mitigation PDP1 WG | Monday, 22 June 2026
by Julie Bisland June 22, 2026

June 22, 2026

**15-MINUTE REMINDER** Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Monday, 22 June 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 * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only (members: please include if an alternate is joining on your behalf) * 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…>. * Staff will promote members, participants, and alternates to panelist once joined. OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. 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…>

1 0

Proposed Agenda for 22 June DNSAM PDP1 WG Call
by Feodora Hamza June 20, 2026

June 20, 2026

Dear DNSAM PDP1, Please find below the proposed agenda for our call on Monday 22 June at 12:30 UTC. 1. Welcome (5min) 2. PDP Updates (10min) 3. Update on pending “CANNOT LIVE WITH” items (60min) 4. Next steps on Initial Report (10min) 5. AOB (5min) Please find below the Prelim Rec Review Doc as prep for the Monday meeting. We have added some suggested language (highlighted in suggestion mode) for WG consideration to be discussed during the next call. * Prelim Rec Review Doc: https://docs.google.com/document/d/1udLt1o9rwCc4xNRsuw6B-5onjpI63VDA/edit?u… Kind regards, Feodora on behalf of Support Staff

4 4

**REMINDER** Meeting Invitation | DNS Abuse Mitigation PDP1 WG | Monday, 22 June 2026
by Julie Bisland June 19, 2026

June 19, 2026

Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Monday, 22 June 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 * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only (members: please include if an alternate is joining on your behalf) * 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…>. * Staff will promote members, participants, and alternates to panelist once joined. OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. 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…>

1 0

Notes and AIs from ICANN86 Session 3 and 4 DNSAM PDP1
by Feodora Hamza June 17, 2026

June 17, 2026

Dear DNSAM PDP1, Please find below the high-level notes and action items from the DNSAM PDP1 WG Session 3 and 4 and ICANN86. Our next meeting is scheduled for 22 June at 12:30 UTC. Please note, we have archived the last version of the Prelim Rec Review Doc for reference purposes. In the updated version we have added a column to each table noting the status of the “cannot live with item” etc. Further changes based on action items will be added and shared in due time prior to the next meeting. * Prelim Rec Review Doc: https://docs.google.com/document/d/1udLt1o9rwCc4xNRsuw6B-5onjpI63VDA/edit?u… Kind regards, Feodora on behalf of Support Staff DNS Abuse PDP1 ICANN86 Session 3 and 4 Action Items: * LT with support from Staff to provide updated language and Rec Review Document prior to next WG call. * WG members to provide alternative language to currently unresolved/still in discussion “cannot live with” items. * WG members to review Prelim Recs and provide any further feedback. Important Docs/links: * Session Link: * Session 3; https://icann86.sched.com/event/2NQNK/gnso-dns-abuse-mitigation-pdp-1-3-of-4 * Session 4: https://icann86.sched.com/event/2NQQf/gnso-dns-abuse-mitigation-pdp-1-4-of-4 * Prelim Rec Review Doc: https://docs.google.com/document/d/1udLt1o9rwCc4xNRsuw6B-5onjpI63VDA/edit?u… * Scoped Impact Assessment: https://docs.google.com/document/d/18xVFX-IXfEgPnIj2UaXmwiXsWE8FY-Jo/edit?u… High- Level Notes: Session 3: * Implementation Guidance vs Compliance Guidance: WG members noted about references to “implementation guidance” throughout the review doc. LT clarified that Implementation Guidance (IG) accompanies policy recommendations and is intended for the Implementation Review Team (IRT). It captures WG expectations and considerations for implementation. In some cases, a working group wants to recommend that the contracted parties MUST take some action and, in addition, the working group generally shares a view about the details about how, why, etc that action MUST happen. However, the how/why/etc is viewed by the WG as the preferred implementation approach or path envisioned by the WG based on the information available to them. This could be included in IG instead of in a policy recommendation to provide some flexibility in the implementation process. This guidance is duly taken into account during the implementation process and should be followed, unless there is a clear reason why the IG should be deviated from. In this case, a rationale would be shared with the IRT for their input. * Charter Question 8: Rec direction is a review should be conducted two years after implementation to assess whether the policy is achieving its intended purpose. Whether improvements are needed. * Some WG members suggested that reviews should not rely solely on ICANN Org and should incorporate stakeholder input to identify implementation challenges. * LT noted that upheld complaints concerning wrongly suspended domains could be included in effectiveness assessments. * Monthly reporting (incorporated into current ICANN DNS Abuse Mitigation reporting) was proposed to provide visibility from implementation onward rather than waiting two years. * Charter Question 9: Rec focuses on registrars must be able to demonstrate compliance through records and documentation maintained in the ordinary course of business. * Some WG members noted that argued that the Rec should include the time of when the trigger occurred. * Some WG members noted that compliance requirements could become a bureaucratic burden, because some ADC activities are simple database queries that are not currently logged. Session 4: * Scoped Impact Assessment: Chair provided executive summary of the Scoped Impact Assessment done by the WG on current Rec language. * Chair asked the WG to review and provide feedback in case anything is missing. * The final review will be done once all Recs are more stable. * “CANNOT LIVE WITH” Discussion: * NPOC proposed changing the trigger standard so that registrars would need a reasonable basis to believe that other domains are associated with the same abusive actor, activity, or campaign before conducting an ADC. After discussion NPOC indicated the concern had largely been addressed by the updated recommendations. * The GAC highlighted scenarios where domains are used intermittently for abuse or Malicious activity may be active only briefly. The concern was that ADC obligations could be circumvented by claiming the domain was not abusive at the precise moment reviewed. WG members recognized the concerns but noted one should avoid creating obligations based on speculative future abuse. GAC to provide alternative language they can live with, that covers language to address established abuse patterns and intermittent abuse scenarios. * IPC noted the definition on “reasonably accessible data” is placed within implementation guidance. They would prefer it moved up to Policy Rec. WG members noted that this could be interpreted by Compliance as requiring registrars to review every available data source whenever conducting an ADC. LT clarified that the Policy Rec already clarifies and provides language on that a Rr does need to review each and every data source for every ADC. * RrSG/NPOC/NCSG noted to remove language from Rec 5 “unless necessary and proportionate to establish sufficient and reliable evidence”. * NCSG added language to Rec 3 that an ADC is not to be confused with a general Audit. LT and WG members clarified that the word “proportionate” in the Rec language provides that caveat. More language in glossary or rationale could provide further clarification.

1 0

Presenting your “can’t live with” items
by Paul McGrady June 14, 2026

June 14, 2026

There remain a handful of items that have been tagged “can’t live with”. You’ll be called upon tomorrow to present yours if you still have one in the collaboration document. To be ready, please: 1. Indicate what problem you are trying to solve. 2. Explain how it’s not already resolved by updates made to the documents and/or in other Recommendations. 3. Indicate whether or not your proposed text is mandatory from your point of view or if you are open to it being iterated by the WG 4. If not open to iteration, please confirm that the group that sent you has authorized you to walk away from the negotiation table if you doing get this specific text. I’ve asked staff to send around slides for tomorrow’s session as soon as practical (within an hour or so). Please keep an eye out so that you have a chance to review them before we meet Thanks all. See you tomorrow. Best, Paul Sent from my iPhone

2 2

Re: Presenting your “can’t live with” items
by Feodora Hamza June 9, 2026

June 9, 2026

Dear DNSAM PDP1, Following up on Paul's previous Email, please find below the updated Prelim Rec Revie Doc: - Review Doc: https://docs.google.com/document/d/1udLt1o9rwCc4xNRsuw6B-5onjpI63VDA/edit?u… - The updates include Prelim Rec on CQ8 and Prelim Rec on CQ9 Please also find attached the slides for tomorrow's session for your consideration and preparation. Kind regards, Feodora on behalf of Support Staff On 09/06/2026, 14:19, "Paul McGrady via Gnso-dnsabuse-pdp" <gnso-dnsabuse-pdp(a)icann.org <mailto:gnso-dnsabuse-pdp@icann.org>> wrote: There remain a handful of items that have been tagged “can’t live with”. You’ll be called upon tomorrow to present yours if you still have one in the collaboration document. To be ready, please: 1. Indicate what problem you are trying to solve. 2. Explain how it’s not already resolved by updates made to the documents and/or in other Recommendations. 3. Indicate whether or not your proposed text is mandatory from your point of view or if you are open to it being iterated by the WG 4. If not open to iteration, please confirm that the group that sent you has authorized you to walk away from the negotiation table if you doing get this specific text. I’ve asked staff to send around slides for tomorrow’s session as soon as practical (within an hour or so). Please keep an eye out so that you have a chance to review them before we meet Thanks all. See you tomorrow. Best, Paul Sent from my iPhone _______________________________________________ Gnso-dnsabuse-pdp mailing list -- gnso-dnsabuse-pdp(a)icann.org <mailto:gnso-dnsabuse-pdp@icann.org> To unsubscribe send an email to gnso-dnsabuse-pdp-leave(a)icann.org <mailto:gnso-dnsabuse-pdp-leave@icann.org>

1 0

Updates and Action items - DNSAM PDP1 Session 1 and 2
by Feodora Hamza June 8, 2026

June 8, 2026

Dear DNSAM PDP1, Please find below the high-level notes and action items form today’s session 1 and 2. Please note our next session is scheduled for Wednesday, 9 June at 10:00. Staff has updated the Prelim Rec Review Doc with the discussed changes from today (in suggestion mode), please see below: * Prelim Rec Review Doc (we have archived last version to have a reference point): https://docs.google.com/document/d/1udLt1o9rwCc4xNRsuw6B-5onjpI63VDA/edit?u… Action Items: * WG to review in case any update or suggestion from today was missed. * WG to review Prelim Rec language and discuss/add potential “cannot live with” * WG to review the glossary in the Prelim Rec Review Doc (last tab) Thank you. Kind regards, Feodora on behalf of Support Staff ICANN86 Policy Forum – DNSAM PDP1 Session 1 and 2 Action Items: * LT with support from Staff to develop prelim rec language for CQ8 and 9 * Staff to update the Prelim Rec Review Document with the updates and suggestion agreed on during Session 1 and 2. * WG members to discuss with their groups the updated Rec and note any “cannot live with” items (if any). Important links/docs: * Prelim Rec Review Doc (we have archived last version to have a reference point): https://docs.google.com/document/d/1udLt1o9rwCc4xNRsuw6B-5onjpI63VDA/edit?u… * Session link: * Session 1 https://icann86.sched.com/event/2NQMr/gnso-dns-abuse-mitigation-pdp-1-1-of-4 * Session 2 https://icann86.sched.com/event/2NQMt/gnso-dns-abuse-mitigation-pdp-1-2-of-4 High Level Meeting Minutes – ICANN86 DNSAM PDP Session 1 & 2 Discussion on CQ8 * WG members noted including a sunset or review mechanism in the policy. * WG members generally supported periodic policy evaluation, with a two-year holistic review suggested. * Concerns were raised about making the policy overly prescriptive. * LT noted to not “overthink” this CQ and focus on the “policy goal” and effort made. * Discussion acknowledged challenges in measuring effectiveness. Discussion on CQ9 * Discussion cantered on requiring registrars to maintain internal documentation describing ADC procedures in the course of conducting their ordinary business. * WG members suggested to remove the last sentence of straw proposal. * ICANN Org noted “different documentation format” I * Concerns were raised regarding ineffective “check-the-box” reviews and transparency around whether ADCs are performed. * Existing registry agreement language (Spec 11.3.B) was discussed as a potential language model. * Some participants supported strengthening language from “should” to “must” where appropriate. Discussion on PR1: * WG members agreed to add proposed definition of Compromised Domains in glossary. * The advisory definition of compromised domains was discussed as a basis for further work. * WG agreed to add in rationale that mitigation on existing contractual obligation should not be substantively delayed due to ADC trigger. Discussion on PR2: * Discussion addressed concerns regarding the phrase “reasonable investigation.” * WG agreed on proposed update based on slide – removal of “review at least one data point” Discussion on PR3: * No major concerns were raised regarding replacing “reasonably available” with “reasonably accessible.” * Participants discussed reseller obligations and registrar responsibility under consensus policy requirements. * Agreement that registrars remain responsible for relevant contractual obligations, including reseller compliance. * Discussion noted that “reasonable” is widely used in existing agreements and Compliance is comfortable with its current interpretation. Discussion on PR5: * Participants discussed simplifying language related to privacy safeguards. * Support was expressed for referencing compliance with applicable law(s). Discussion on PR6: * Extensive discussion occurred on whether to establish fixed timelines. * Participants generally favoured retaining “promptly” rather than specifying 24-hour or 72-hour requirements. * IPC expressed interest in measuring response times as part of effectiveness metrics rather than as a strict policy requirement. * Concerns were raised that strict timelines could be counterproductive and could allow abuse to continue longer. * BC ultimately accepted use of “promptly” in place of a 24-hour timeline proposal. * Outcome: broad alignment on “promptly”. Discussion on PR7: * Agreement that several topics should be flagged for future policy consideration rather than included as policy recommendations. * Topics identified included: * Transparency regarding mitigation actions. * Recourse mechanisms. * Cross-registrar intelligence sharing. * Registry-level abuse patterns. * Frameworks for contracted-party information sharing. * LT suggested communicating these issues to Council through a letter rather than an annex to the report.

1 0