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

FW: Draft Email for WG
by Paul McGrady April 3, 2026

April 3, 2026

Hi Team! Thank you for your active participation in this PDP and on list. There are a few things the leadership team wants to cover to prepare for the upcoming meeting on Tuesday 7 April at 12:30 UTC (yellow highlighted due to the move for Easter Monday). 1. Based on the WG discussion and the input on email list, the leadership team has decided to maintain the Monday meeting schedule unless it conflicts with a major holiday that would impact staff support and a majority of the WG. In those cases: 6 April, 25 May, 7 September the meetings have been moved to the following day on Tuesdays. The 27th of April meeting has been canceled due to the absence of support staff and WG members for the CPH Summit which wouldn't be remedied by a move. For those of us not going to Manchester, enjoy the week off! Calendar invites have gone out, and the schedule is now locked in. If a member is unable to attend a meeting, please have your alternate attend in your place. 1. Having received no additional comments on the Workplan, the revised workplan will be submitted to the GNSO Council by our liaison Jen Chung for discussion at the 16 April GNSO Council meeting. The revised timeline based on WG and community input at ICANN85 and on the WG meetings resulted in an estimated finish date of May/June 2027 instead of October/November 2027. The workplan can be found here: https://docs.google.com/spreadsheets/d/1gDXM13Io8RJlYZVj0rhbfoMi7und3v9i/ed…. Thank you all for getting this wrapped up in time! 1. Leadership has asked staff to clean up the collaboration document a bit for concise and accessible format. https://docs.google.com/document/d/1GxM-Yrgv6sZPEYU8ikW4cRM5YqWsJuWGiQyO39p… With that, there will be two changes going forward: * The "Stable but not final language" will be converted by staff into a preliminary strawperson of preliminary recommendation language and rationale based upon the WG deliberations, comments, in-text work, and the early input from the various groups. This is intended to be a first attempt to distill language taking convergent and divergent views into account. Staff will update that today for Charter Question 1 for discussion on Tuesday's call. This is where we get granular! * Given the robust early input from many groups, the full text of each submission will be linked for each charter question, but staff will work to summarize points of convergence in the collaboration document. This will help speed our work by recognizing places in which we are already in alignment. WG members are encouraged to read the full text of submissions and to raise points of remaining divergence along with solutions on how to converge in the WG calls or in the comments. https://docs.google.com/document/d/1Qk2-h2E8sY1OI64-k8-hnW2FGgaiaQ1M_csEmUM… 1. Staff will send out an agenda of the upcoming meeting shortly. For those of you celebrating a holiday this weekend, I wish you a blessed time with family and friends. Best, Paul [cid:image001.png@01DCC36D.FD2ABB80] 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/>

3 2

Outcomes, Action Items, and Notes - 23 March 2026 - Meeting #6
by Steve Chan April 3, 2026

April 3, 2026

Dear DNSAM PDP 1, Please see the attached outcomes, action items, and notes from Meeting #6. Best, Steve [OUTCOMES] * Nick Wenban-Smith elected vice-chair [ACTION ITEMS] * Staff to post election results and onboard Nick to the leadership team. * Leadership and staff to provide a path forward for the WG meeting schedule, taking into account Monday holidays. * WG members to provide further input on the proposed updated work plan, no later than 3 April [updated work plan attached]. * Jennifer Chung, as Council liaison to the WG, to submit work plan to the Council no later than 6 April. [NOTES] 1. Welcome * None 2. Update on VC Chair Selection * Nick Wenban-Smith elected vice-chair Action Item: Staff to post election results and onboard Nick to the leadership team. 3. Meeting Cadence/Public Holidays * With so many meetings on Monday, leadership is proposing to move the meetings to the second most common acceptable day based on Doodle poll results. * Suggestion from many to leave on Monday and only move to Tuesday if there are “enough” WG members that cannot attend, but don’t cancel. Action Item: Leadership and staff to provide a path forward for the WG meeting schedule, taking into account Monday holidays. 4. Update on Workplan * Leaders and staff have taken into consideration input and has suggested changes to shorten the timeline. Key changes are initial deliberations and time between Initial and Final Report. Some appreciation, but also some discomfort for the shortened work plan. * The initial proposal for the work plan was potentially too conservative; the updated work plan is still designed to be achievable. * Next step is for the work plan to go to Council for acknowledgement via the Council liaison, Jennifer Chung. Action Item: WG members to provide further input on the proposed updated work plan, no later than 3 April [updated work plan attached]. Action Item: Jennifer Chung, as Council liaison to the WG, to submit work plan to the Council no later than 6 April. 5. Continue Deliberation * Early input received from the BC, GAC, IPC, ISPCP, NCSG, RrSG – input is aggregated and stored on the Wiki. Each piece of input will be added into the collaboration tool, relative to the Charter question. * Reviewed Overarching Themes so far from WG discussions, both verbal and on email. Also included relevant sections from Early Input, though full comments should be reviewed on the Wiki: https://icann-community.atlassian.net/wiki/spaces/DAMP1/pages/983433230/Com… * Concern that if the trigger requires action every single time, it represents costs and efforts for the registrars, impacting the ability of registrars to effectively combat DNS Abuse. Noted that we still have a question to determine what the investigation will look like. * Suggestion/reminder to define a maliciously registered domain name based on RAA 3.18.2. * “When Registrar has actionable evidence that a Registered Name sponsored by Registrar is being used for DNS Abuse, Registrar must promptly take the appropriate mitigation action(s) that are reasonably necessary to stop, or otherwise disrupt, the Registered Name from being used for DNS Abuse.” * Reminder that we need to allow for some flexibility in the solutions as bad actors will change their methods. However, the requirements still ultimately need to be enforceable. * The GAC early input talks about how to perform the ADC, as in what represents association – this input connects to a later Charter question. We are blending the charter questions a bit. * If the trigger is not a single maliciously registered domain name based on RAA 3.18.2, what would be the alternative? * Caution from some to avoid listing all ways to identify associated domain names engaging in DNS Abuse as defined by 3.18.2. * Question about proportionality in respect of initial trigger versus ADC – answer from those that are particularly concerned about proportionality, is both. * Reminder from ISPCP early input that the ADC should also be based on the same standard as in 3.18.2. Are there any members suggesting to go beyond these limitations? Seems to be alignment to stick with the RAA definition. * A balance is needed to avoid listing every ADC action, but also not to leave so vague that bad actors can exploit the holes. * Several mentions of a “reasonableness” standard for the ADC, in terms of what needs to be looked at. Continued caution against creating a prescriptive matrix. * Suggestion to create an advisory to help guide what the ADC should include, which can be updated from time to time. Question about how advisories are updated – answer is that there are a multitude of ways to update advisories. * Several members reminded that proportionality is important. However, question about potential harms from investigating whether other DNS Abuse is occurring. * Noted that reasonableness is already a component of the RAA, including for RAA 3.18.2. There is a difference between “what” reasonableness represents for initial trigger versus the reasonableness of “how” the ADC is performed. The advisory notion is more relevant to the latter of “how”. * Some discussion about compromised domains, which are not within scope of this PDP. Question about whether a compromised domain should trigger investigation of the account. * We have not yet discussed what the ADC itself should involve, other than it should not be prescriptive. This aspect is when proportionality will be more relevant. * Reasonableness of the ADC will vary based on the circumstances. And question about how that should be passed on to the reseller. 6. AOB * Planning to have 4 sessions during the standard meetings days for ICANN86. Will try to avoid conflicts to the extent possible. * There will also be a prep-week webinar to provide an update on the progress of this PDP. * Will need to confirm work plan – get it to Council by the 6th. * Staff will continue to update the collaboration tool and the WG should continue to review and provide feedback. Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Mobile: +1.310.339.4410

5 7

Call dates until ICANN87 / DNS Abuse Mitigation PDP1 WG calls
by Julie Bisland April 2, 2026

April 2, 2026

Dear all, Please find the .ics attached for the DNS Abuse Mitigation PDP1 WG calls taking place 22 June – 05 October 2026. Please download it to your calendar. Calls take place every Monday at 12:30 UTC for 90 minutes, except those noted below: * Monday, 07 September was moved to Tuesday, 08 September In addition, some already-scheduled calls in April and May falling on Monday holidays have been adjusted, see below: * Monday, 06 April was moved to Tuesday, 07 April * Monday, 27 April has been cancelled * Monday, 25 May has been moved to Tuesday, 26 May Wiki pages can be found here: https://icann-community.atlassian.net/wiki/x/B4CWLQ The email invitation for each call will be sent out closer to the date of the meeting. The next call is taking place on Tuesday, 07 April 2026 and the invite has already been sent. Please reach out to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> with questions. Thank you! Kind regards, Julie Policy Team Supporting the GNSO -- 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

DNS Abuse Mitigation PDP1 WG
by ICANN Policy Calendar April 2, 2026

April 2, 2026

Moved from Monday, 07 September to Tuesday, 08 September, same time. MEETING: DNS Abuse Mitigation PDP1 WG call DATE/TIME: Weekly on Mondays at 12:30 UTC for 90 minutes, 22 June – 05 October 2026 Zoom webinar, Join from PC, Mac, iPad, or Android: 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…>. * Staff will promote members, participants, and alternates to panelist once joined. * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ * Time Zone conversion (22 June call): https://tinyurl.com/55d3xesr 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.

1 0

Re: Call 2026-03-30
by Eberhard W Lisse April 2, 2026

April 2, 2026

Thank you, el On 2026-04-02 18:37, Julie Bisland wrote: > Dear Eberhard, > > > > Attendance has been updated and posted to reflect you attended the call. > > > > Thank you. > Kind regards, > > > > Julie [...] > *From: *Eberhard W Lisse <el(a)lisse.na> [...] > > > > Please update the attendance list to reflect the below. > > > > el [...] -- Eberhard W. Lisse \ /Obstetrician & Gynaecologist (retired) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht\ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

DNS Abuse Mitigation PDP1 WG
by ICANN Policy Calendar April 2, 2026

April 2, 2026

MEETING: DNS Abuse Mitigation PDP1 WG call DATE/TIME: Weekly on Mondays at 12:30 UTC for 90 minutes, 22 June – 05 October 2026 Zoom webinar, Join from PC, Mac, iPad, or Android: 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…>. * Staff will promote members, participants, and alternates to panelist once joined. * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ * Time Zone conversion (22 June call): https://tinyurl.com/55d3xesr 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.

1 0

DNS Abuse Mitigation PDP1 WG
by ICANN Policy Calendar April 2, 2026

April 2, 2026

MEETING: DNS Abuse Mitigation PDP1 WG call DATE/TIME: Weekly on Mondays at 12:30 UTC for 90 minutes, 22 June – 05 October 2026 Zoom webinar, Join from PC, Mac, iPad, or Android: 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 (22 June call): https://tinyurl.com/55d3xesr

1 0

DNS Abuse Mitigation PDP1 WG
by ICANN Policy Calendar April 2, 2026

April 2, 2026

Moved Monday, 25 May to Tuesday, 26 May, same time. 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: https://tinyurl.com/zxe3njhu

1 0

Canceled: DNS Abuse Mitigation PDP1 WG
by ICANN Policy Calendar April 2, 2026

April 2, 2026

CANCELLED 27 APRIL ONLY 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

Call 2026-03-30
by Eberhard W Lisse April 2, 2026

April 2, 2026

Nick, congrats. Staff, I was on the call today, using Carplay while cruising on the German Autobahn to the Frankfurt Airport and wanted to make some technical remarks: Carplay Zoom is plain Audio so references to the chat and slides went by me. So should they be summarized if there is any one on Audio only. I think you can see that in the Participant pod. Carplay does not have a touch screen option to raise hand, and touching the phone while driving is dangerous and illegal. I don't have a solution for that. The quality of Zoom is impressive, it automatically increased volume after a second or so if the speaker was faint. The phone quality (Paul) was a bit worse than the ones from the microphones connected directly. I personally use AirPods on the laptop, and a Sennheiser USB-C headset when at home. I reached FRA 15 minutes before the end and my chat was disabled. I checked and the Zoom on my travel phone had me as Nicky Lisse as the default. We have two licenses and I mainly use the other one, but will in the future try and make sure I show the right screen name, so staff can identify me as participant. All in all I was surprised how well this worked. Paul, i wonder about the trigger issue. Are we not re-inventing the wheel here? My understanding is that currently the RAA specifies how to identify an abusive domain and how to mitigate. Please correct me if I am wrong, but that could be the minimal requirement for a trigger. If we use that we have normalized it, so that changes in the current definition of abuse in the RAA would be automatically reflect in the Policy. Now, I have no opinion on how many of those would have to have been (required to be) mitigated in order to trigger "our" investigation (at least one). As far as reasonableness is concerned there are legal definitions, which boil down to "I know it when I see it" :-)-O, so one could look for one or a combination of definitions for our context. With regard to the action the Registrar would have to take, if associated names were found to be abusive, we could again refer to the RAA and use the mitigation described there. Does any of this help? el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (retired) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 1