March 2026 - Gnso-dnsabuse-pdp

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 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

Invitation: DNS Abuse Mitigation PDP1 WG @ Weekly from 13:30 to 15:00 on Monday from Mon Mar 23 to Tue Jun 2 (GMT+1) (gnso-dnsabuse-pdp@icann.org)
by Bruna Martins dos Santos March 30, 2026

March 30, 2026

DNS Abuse Mitigation PDP1 WG Weekly from 13:30 to 15:00 on Monday from Monday Mar 23 to Tuesday Jun 2 Central European Time - Amsterdam Location 12:30 UTC / https://icann.zoom.us/j/91807711636?pwd=q6XCt8cWQU9m3fGgSojQ5X07pbnX6a.1 https://www.google.com/maps/search/12:30+UTC+%2F+https:%2F%2Ficann.zoom.us%… Moved Monday 06 April to Tuesday 07 April, same time (holiday) 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:&#43;X8RaawVrW Phone one-tap: &#43;13126266799,,91807711636#,,,,*0006343077# US (Chicago) &#43;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@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/page…, the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-p…, and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-commun…. * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ * Time Zone conversion (23 March): https://tinyurl.com/u3m4kuzv Organizer Bruna Martins dos Santos bruna.mrtns(a)gmail.com Guests Bruna Martins dos Santos - organizer john.emery(a)icann.org steve.chan(a)icann.org bruna(a)witness.org feodora.hamza(a)icann.org julie.bisland(a)icann.org dimitris.zacharias(a)icann.org gnso-dnsabuse-pdp(a)icann.org emmanuelvitus(a)gmail.com chris.disspain(a)identity.digital terri.agnew(a)icann.org bburr(a)pir.org devan.reed(a)icann.org manju4icann(a)gmail.com 6.internet(a)gmail.com policycalendar(a)icann.org View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=NjMwaWF2bm9vMmsz… Reply for gnso-dnsabuse-pdp(a)icann.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=NjMwaWF2bm9vMmsz… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 1

Re: [Ext] RE: Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Tuesday, 07 April 2026
by Julie Bisland March 30, 2026

March 30, 2026

Hello Nitin, all, The invitation you received was only for the 07 April call. Staff is currently identifying the conflicted dates that will be moved to Tuesday and which will be cancelled. More to come! Best regards, Julie -- Julie Bisland Policy Team Supporting the GNSO From: Nitin Walia <nitin(a)data.in> Date: Monday, March 30, 2026 at 11:36 AM 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: [Ext] RE: [Gnso-dnsabuse-pdp] Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Tuesday, 07 April 2026 Dear Julie, Thank you for the update and for rescheduling the upcoming call. Just to clarify does this change apply only to the 7 April meeting, or has a decision been made to move all upcoming DNS Abuse Mitigation PDP1 WG calls from Monday to Tuesday going forward? Appreciate your guidance so we can plan accordingly. Regards Nitin Sent from Xgenplus Mobile App. -------- Original message -------- From: Julie Bisland via Gnso-dnsabuse-pdp <gnso-dnsabuse-pdp(a)icann.org> Date: 30/03/26 9:02 pm (GMT+05:30) To: gnso-dnsabuse-pdp(a)icann.org Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-dnsabuse-pdp] Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Tuesday, 07 April 2026 Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Tuesday, 07 April 2026 at 12:30 UTC for 90 minutes (moved from Monday, 06 April, holiday). Check your timezone. [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/dzwh626t__;!!PtGJab4!9T48p6o…> Join from PC, Mac, iPad, or Android - Zoom Webinar: https://icann.zoom.us/j/91807711636?pwd=q6XCt8cWQU9m3fGgSojQ5X07pbnX6a.1 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/91807711636?pwd=q6XCt8cW…> 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 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/a9jfXWLB8__;!!PtGJab4!9T…> * 2026 Meetings wiki: https://icann-community.atlassian.net/wiki/x/B4CWLQ [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/B4C…> 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

Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Tuesday, 07 April 2026
by Julie Bisland March 30, 2026

March 30, 2026

Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Tuesday, 07 April 2026 at 12:30 UTC for 90 minutes (moved from Monday, 06 April, holiday). Check your timezone.<https://tinyurl.com/dzwh626t> 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…>

2 1

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

March 30, 2026

Moved Monday 06 April to Tuesday 07 April, same time (holiday) 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

Post Call / DNS Abuse Mitigation PDP1 WG / Monday, 30 March 2026
by Julie Bisland March 30, 2026

March 30, 2026

Dear all, All recordings for the DNS Abuse Mitigation PDP1 WG call held on Monday, 30 March 2026 at 12:30 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AYDENw> (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

**15-MINUTE REMINDER** Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Monday, 30 March 2026
by Julie Bisland March 30, 2026

March 30, 2026

**15-MINUTE REMINDER** Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Monday, 30 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 (30 March): https://tinyurl.com/yw2t37uy 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

Another Monday for the list
by Volker Greimann March 27, 2026

March 27, 2026

Hi Paul, I really hate to add onother Monday to the list, but I think I do need to flag that many if not all of the Contracted Parties reps, Alts and Observers may not be available on the 27th of April due to ICANNs Contracted Parties Summit. Sincerely, Volker Greimann General Counsel & Head of Policy and Compliance - Online Division volker.greimann(a)centralnic.com Office: +49-172-6367025 Web: 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.

4 3

**REMINDER** Meeting Invitation / DNS Abuse Mitigation PDP1 WG / Monday, 30 March 2026
by Julie Bisland March 27, 2026

March 27, 2026

Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Monday, 30 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 (30 March): https://tinyurl.com/yw2t37uy 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

Re: REMINDER: Vice Chair eBallot Due 27 March 23:59 UTC
by John Emery March 27, 2026

March 27, 2026

Dear DNSAM PDP WG, A couple of reminders and things to flag for the remaining VC voters: 1. Only WG Members and Participants can vote. Not Alternates. 2. Some of you may have emails from either votenet.com or noreply(a)eballot.com<mailto:noreply@eballot.com>, so if you are struggling to find it, check spam for both senders. We now have 70% participation, so thank you many of you for voting today. All the best, John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: John Emery via Gnso-dnsabuse-pdp <gnso-dnsabuse-pdp(a)icann.org> Reply-To: John Emery <john.emery(a)icann.org> Date: Thursday, March 26, 2026 at 06:34 To: "gnso-dnsabuse-pdp(a)icann.org" <gnso-dnsabuse-pdp(a)icann.org> Subject: [Gnso-dnsabuse-pdp] REMINDER: Vice Chair eBallot Due 27 March 23:59 UTC Dear DNSAM PDP WG, As you are aware, we are in the midst of Vice-Chair elections for this PDP. At the time of this email, just above half of eligible voters have voted. As a reminder, the election will close 27 March 2026 at 23:59 UTC. Recall from Monday's meeting that only Members and Participant were eligible to vote. If you did not receive your ballot from the eBallot platform, please follow these instructions: 1. Check you spam folder to see if the ballot sent to you may have been caught there. The ballot will be delivered from votenet.com [votenet.com]<https://urldefense.com/v3/__http:/votenet.com__;!!PtGJab4!_i0Rf6DOsk6eI7aiF…>. 2. If you do not see the ballot in your inbox or spam folder, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and staff will resolve the issue by contacting you directly. Please do not submit your delivery issue to the PDP mailing list. All the best, GNSO Policy Development Support Team John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

4 3

Proposed Agenda: DNSAM PDP1 30March 12:30 UTC
by Feodora Hamza March 26, 2026

March 26, 2026

Dear DNSAM PDP1, Please find below the proposed agenda for our meeting on Monday, 30 March at 12:30 UTC. Welcome 5min Outcome VC Chair Selection Procedure 5min Update on meeting cadence/public holidays 10min Update on work plan 25min Continue Deliberations 40min AOB * ICANN86 planning 5min Kind regards, Feodora

1 0

REMINDER: Vice Chair eBallot Due 27 March 23:59 UTC
by John Emery March 26, 2026

March 26, 2026

Dear DNSAM PDP WG, As you are aware, we are in the midst of Vice-Chair elections for this PDP. At the time of this email, just above half of eligible voters have voted. As a reminder, the election will close 27 March 2026 at 23:59 UTC. Recall from Monday's meeting that only Members and Participant were eligible to vote. If you did not receive your ballot from the eBallot platform, please follow these instructions: 1. Check you spam folder to see if the ballot sent to you may have been caught there. The ballot will be delivered from votenet.com<http://votenet.com>. 2. If you do not see the ballot in your inbox or spam folder, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and staff will resolve the issue by contacting you directly. Please do not submit your delivery issue to the PDP mailing list. All the best, GNSO Policy Development Support Team John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Re: Action Item: Review Workplan by 30March
by Nitin Walia March 26, 2026

March 26, 2026

Dear Feodora, Thank you for the update and for enabling access. I will review the document and share my inputs directly in the sheet . Appreciate the flexibility to also contribute via email . 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: Feodora Hamza MailId : [153939835]To: Nitin Walia Subject: Re: [Gnso-dnsabuse-pdp] Re: Action Item: Review Workplan by 30MarchDate: 26 Mar 2026 03:18:57 PM Hi Nitin, thank you very much for pointing this out. The access rights to the document have been updated and now you can provide your input directly into the file: https://docs.google.com/spreadsheets/d/1gDXM13Io8RJlYZVj0rhbfoMi7und3v9i/ed… [docs.google.com] However, WG members are also always welcome to provide input via Email. Whichever approach is easier for you. Thank you again. Kind regards, Feodora From: Nitin Walia via Gnso-dnsabuse-pdp Reply to: Nitin Walia Date: Thursday, 26 March 2026 at 10:14 To: feodora hamza via gnso-dnsabuse-pdp Subject: [Gnso-dnsabuse-pdp] Re: Action Item: Review Workplan by 30March Dear Feodora, Thank you for forwarding the email from Paul McGrady regarding the PDP work plan and timeline. I appreciate the clarity provided on the proposed approach, milestones, and workflow . I just had a small clarification regarding the submission of inputs by 30 March. Should we be sharing our feedback on the mailing list, or is it preferred to add comments directly in the WG Inputs tab of the shared Google sheet document? I understand that the WG Inputs tab in the sheet may currently allow inputs only in comment mode from my end, so I wanted to confirm the preferred approach . Warm Regards Nitin Walia Director Data Ingenious Global nitin(a)data.in | नितिन(a)xn--c2bd1gb.xn--h2brj9c www.data.in [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: Feodora Hamza via Gnso-dnsabuse-pdp MailId : [153929934] To: "gnso-dnsabuse-pdp(a)icann.org" Subject: [Gnso-dnsabuse-pdp] Action Item: Review Workplan by 30March Date: 25 Mar 2026 07:31:18 PM Sent on behalf of Paul McGrady Dear DNSAM PDP1 members, During the recent ICANN85 session and our last call on 23 March, we briefly reviewed the proposed approach for progressing the PDP work and the draft timeline that staff shared with the group. I would like to recap the key points from that discussion and invite your feedback . Staff also presented a draft work plan and timeline for the PDP. The Milestones of the proposed plan include: Initial Report to be published in Feb 2027 and Final Report to go to Council in September 2027 . A workflow that pairs discussion during meetings with substantive asynchronous work between meetings . Rolling development of draft recommendations for each charter question . Iterative impact analysis during the drafting process rather than waiting until the end of the PDP . A final review phase before preparation of the Initial Report . Members within the WG and beyond noted during ICANN85 that the timeline may appear lengthy. However, when assessing the timeline it is important to keep in mind that certain procedural timelines are established by the ICANN Bylaws and cannot be shortened. In addition, the days referenced in the work plan represent calendar days, not meeting days. For example, a 10-day period effectively corresponds to roughly two Working Group meetings, which shows the importance of asynchronous review and drafting work between calls if the group aims to accelerate progress . That said, it is for the Working Group to collectively decide on a timeline.. Please review the detailed work plan and let us know where the group believes the timeline could reasonably be shortened. We will collect feedback and discuss potential adjustments during the next Working Group call. Please provide your input by 30 March. Leadership will then look into the feedback provided and adjust the timeline where appropriate . Please see here the workplan document including 3 tabs: One Tab with the draft workplan One Tab with standard PDP timelines as required by the bylaws One Tab for the WG to provide comments regarding the workplan Link:https://docs.google.com/spreadsheets/d/1gDXM13Io8RJlYZVj0rhbfoMi7und3v… [docs.google.com] It is important to note that project plans and timelines are designed as the maximum expected duration of the PDP. From a project management perspective, it is generally preferable to plan conservatively and deliver earlier where possible, rather than risk delays. Any need to extend the timeline would require approval from the GNSO Council . However, we would like to highlight a few areas where the timeline could potentially be shortened, subject to Working Group agreement: Post&ndashInitial Report Public Comment phase: The time allocated between the close of public comment and preparation of the Final Report could potentially be reduced. However, this will depend on the volume and complexity of comments received. Given the high level of interest in this topic, extensions to the public comment period or additional analysis time may still be required. Charter Question sequencing: While the work plan assumes that charter questions are addressed sequentially, initial WG discussions and draft language suggest that deliberations may overlap across questions. Identifying and leveraging these overlaps may create efficiencies and allow certain elements of the work to progress in parallel . We therefore encourage the Working Group to carefully review the detailed work plan and consider where realistic efficiencies can be achieved. Thank you again for your engagement and contributions to the PDP. We look forward to continuing the discussion on the upcoming call . Best regards, Paul _______________________________________________ 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]2026032519311822[-HID] [XGENFOOTER] [-XGENFOOTER]

1 0

Vice Chair DND Abuse Mitigation committee
by anil Jain March 26, 2026

March 26, 2026

Hi, I am Anil Kumar Jain, Participant in DNS Abuse Mitigation PDP I , representing ISPCP Constituency. I am seeking your support for the post of Vice Chair Position in DNS Abuse Mitigation PDP I. 1. I have already lead/ represented three PDPs, hence sufficient experience in leading PDP. 2. I was chair of UASG(23-25), Chair Cummunication WG of UASG(22-25), Vice Chair IDN ccTLD PDP WG4, Vice Chair of IGLC of ccTLD, hence held several leadership positions in ICANN. 3. I was chair of India IGF, chair India DNS Abuse Mitigation Committee, chair UA Day committee (2023). We shall work together to ensure meeting all objectives of Charter well within time , decisions by consensus, ensuring a document which can lead other efforts in same direction. Thanks, Sent from my iPhone

1 0

Re: Action Item: Review Workplan by 30March
by Nitin Walia March 26, 2026

March 26, 2026

Dear Feodora, Thank you for forwarding the email from Paul McGrady regarding the PDP work plan and timeline. I appreciate the clarity provided on the proposed approach, milestones, and workflow . I just had a small clarification regarding the submission of inputs by 30 March. Should we be sharing our feedback on the mailing list, or is it preferred to add comments directly in the WG Inputs tab of the shared Google sheet document? I understand that the WG Inputs tab in the sheet may currently allow inputs only in comment mode from my end, so I wanted to confirm the preferred approach . 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: Feodora Hamza via Gnso-dnsabuse-pdp MailId : [153929934]To: "gnso-dnsabuse-pdp(a)icann.org" Subject: [Gnso-dnsabuse-pdp] Action Item: Review Workplan by 30MarchDate: 25 Mar 2026 07:31:18 PM Sent on behalf of Paul McGrady Dear DNSAM PDP1 members, During the recent ICANN85 session and our last call on 23 March, we briefly reviewed the proposed approach for progressing the PDP work and the draft timeline that staff shared with the group. I would like to recap the key points from that discussion and invite your feedback . Staff also presented a draft work plan and timeline for the PDP. The Milestones of the proposed plan include: Initial Report to be published in Feb 2027 and Final Report to go to Council in September 2027 . A workflow that pairs discussion during meetings with substantive asynchronous work between meetings . Rolling development of draft recommendations for each charter question . Iterative impact analysis during the drafting process rather than waiting until the end of the PDP . A final review phase before preparation of the Initial Report . Members within the WG and beyond noted during ICANN85 that the timeline may appear lengthy. However, when assessing the timeline it is important to keep in mind that certain procedural timelines are established by the ICANN Bylaws and cannot be shortened. In addition, the days referenced in the work plan represent calendar days, not meeting days. For example, a 10-day period effectively corresponds to roughly two Working Group meetings, which shows the importance of asynchronous review and drafting work between calls if the group aims to accelerate progress . That said, it is for the Working Group to collectively decide on a timeline.. Please review the detailed work plan and let us know where the group believes the timeline could reasonably be shortened. We will collect feedback and discuss potential adjustments during the next Working Group call. Please provide your input by 30 March. Leadership will then look into the feedback provided and adjust the timeline where appropriate . Please see here the workplan document including 3 tabs: One Tab with the draft workplan One Tab with standard PDP timelines as required by the bylaws One Tab for the WG to provide comments regarding the workplan Link:https://docs.google.com/spreadsheets/d/1gDXM13Io8RJlYZVj0rhbfoMi7und3v… It is important to note that project plans and timelines are designed as the maximum expected duration of the PDP. From a project management perspective, it is generally preferable to plan conservatively and deliver earlier where possible, rather than risk delays. Any need to extend the timeline would require approval from the GNSO Council . However, we would like to highlight a few areas where the timeline could potentially be shortened, subject to Working Group agreement: Post&ndashInitial Report Public Comment phase: The time allocated between the close of public comment and preparation of the Final Report could potentially be reduced. However, this will depend on the volume and complexity of comments received. Given the high level of interest in this topic, extensions to the public comment period or additional analysis time may still be required. Charter Question sequencing: While the work plan assumes that charter questions are addressed sequentially, initial WG discussions and draft language suggest that deliberations may overlap across questions. Identifying and leveraging these overlaps may create efficiencies and allow certain elements of the work to progress in parallel . We therefore encourage the Working Group to carefully review the detailed work plan and consider where realistic efficiencies can be achieved. Thank you again for your engagement and contributions to the PDP. We look forward to continuing the discussion on the upcoming call . Best regards, Paul _______________________________________________Gnso-dnsabuse-pdp mailing list -- gnso-dnsabuse-pdp(a)icann.orgTo unsubscribe send an email to gnso-dnsabuse-pdp-leave(a)icann.orgDo not Remove:[HID]2026032519311822[-HID] [XGENFOOTER] [-XGENFOOTER]

1 0

Action Item: Review Workplan by 30March
by Feodora Hamza March 25, 2026

March 25, 2026

Sent on behalf of Paul McGrady Dear DNSAM PDP1 members, During the recent ICANN85 session and our last call on 23 March, we briefly reviewed the proposed approach for progressing the PDP work and the draft timeline that staff shared with the group. I would like to recap the key points from that discussion and invite your feedback. Staff also presented a draft work plan and timeline for the PDP. The Milestones of the proposed plan include: * Initial Report to be published in Feb 2027 and Final Report to go to Council in September 2027. * A workflow that pairs discussion during meetings with substantive asynchronous work between meetings. * Rolling development of draft recommendations for each charter question. * Iterative impact analysis during the drafting process rather than waiting until the end of the PDP. * A final review phase before preparation of the Initial Report. Members within the WG and beyond noted during ICANN85 that the timeline may appear lengthy. However, when assessing the timeline it is important to keep in mind that certain procedural timelines are established by the ICANN Bylaws and cannot be shortened. In addition, the days referenced in the work plan represent calendar days, not meeting days. For example, a 10-day period effectively corresponds to roughly two Working Group meetings, which shows the importance of asynchronous review and drafting work between calls if the group aims to accelerate progress. That said, it is for the Working Group to collectively decide on a timeline. Please review the detailed work plan and let us know where the group believes the timeline could reasonably be shortened. We will collect feedback and discuss potential adjustments during the next Working Group call. Please provide your input by 30 March. Leadership will then look into the feedback provided and adjust the timeline where appropriate. Please see here the workplan document including 3 tabs: * One Tab with the draft workplan * One Tab with standard PDP timelines as required by the bylaws * One Tab for the WG to provide comments regarding the workplan * Link:https://docs.google.com/spreadsheets/d/1gDXM13Io8RJlYZVj0rhbfoMi7und3v… It is important to note that project plans and timelines are designed as the maximum expected duration of the PDP. From a project management perspective, it is generally preferable to plan conservatively and deliver earlier where possible, rather than risk delays. Any need to extend the timeline would require approval from the GNSO Council. However, we would like to highlight a few areas where the timeline could potentially be shortened, subject to Working Group agreement: * Post–Initial Report Public Comment phase: The time allocated between the close of public comment and preparation of the Final Report could potentially be reduced. However, this will depend on the volume and complexity of comments received. Given the high level of interest in this topic, extensions to the public comment period or additional analysis time may still be required. * Charter Question sequencing: While the work plan assumes that charter questions are addressed sequentially, initial WG discussions and draft language suggest that deliberations may overlap across questions. Identifying and leveraging these overlaps may create efficiencies and allow certain elements of the work to progress in parallel. We therefore encourage the Working Group to carefully review the detailed work plan and consider where realistic efficiencies can be achieved. Thank you again for your engagement and contributions to the PDP. We look forward to continuing the discussion on the upcoming call. Best regards, Paul

1 0

Kind reminder: Follow-up: WG Collaboration Document
by Feodora Hamza March 25, 2026

March 25, 2026

Dear all, a kind reminder on the Action Item below: 5. Collaboration document for the WG to contribute, provide feedback, and change as the WG sees fit. · Based on the discussions to date and the language provided by Working Group members, leadership and staff have developed a working document to capture discussions and draft language for each charter question. · This document is intended to support clear navigation, transparency, and effective asynchronous work, allowing members to review, comment, and refine proposals between meetings in a structured way. · Each charter question is listed and 3 different coloured boxes are provided for each. · First (orange), the key takeaways from the previous discussion · Second box (green), the draft language provided by the WG and some overarching themes that can be derived from that language · Third (blue), a box for when the WG is ready to stabilise the language for their recommendation on each Charter Question. · Link:https://docs.google.com/document/d/1GxM-Yrgv6sZPEYU8ikW4cRM5YqWsJuWGiQ… Kind regards, Feodora 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> From: Feodora Hamza <feodora.hamza(a)icann.org> Date: Monday, 23 March 2026 at 15:47 To: "gnso-dnsabuse-pdp(a)icann.org" <gnso-dnsabuse-pdp(a)icann.org> Subject: Follow-up: WG Collaboration Document Sent on behalf of Paul McGrady Dear DNSAM PDP1 WG members, thank you for today’s call. As briefly noted before the meeting ended, I would like to take a moment to outline the plan for how the Working Group will approach its deliberations and methodology moving forward. We alluded to this during ICANN85 but it is always good to recap and make sure all members are on the same page. Firstly, it is encouraging to see the level of ambition within the group and the clear willingness to collaborate and develop workable solutions. This is the spirit of volunteerism that I love so much about our community. At the same time, our early discussions have demonstrated that reaching consensus will take time and due consideration, given the range of perspectives, needs, and considerations that proposed recommendations must undergo. There is no “silver bullet” but we do have good tools to accomplish our work in a timely, thorough fashion. 1. Staying within scope: As a reminder, the charter defines the scope of this PDP (the nature of our universe), and it is essential that our discussions remain within those boundaries. Where ideas arise that fall outside of scope, these can certainly be captured for future consideration by Council but should not slow down or divert our current work. I know it would be great to solve every problem all at once, but that is not what Council asked us to do. 2. Focus on recommendations: At this stage and as noted during our ICANN85 session 2 on Consensus Building, the Working Group should prioritize identifying needs and developing policy recommendations, rather than jumping directly to specific implementation/policy language solutions. This will help ensure that our outputs remain policy-focused and aligned with the role of the PDP. However, I do appreciate the specific language provided so far as it helps to inform where recommendations can go and can give us something concrete to haggle over. So, don’t be shy but understand we won’t be recommending specific contract language, just high level Policy. 3. Consensus building throughout the process: As highlighted in our consensus-building discussions, we should ensure that all SGs/Cs and community stakeholders understand not only what the Working Group is proposing, but also why. Drawing on lessons learned and best practices (including those captured in the consensus building playbook and ICANN85 session2), clear rationale and transparency in our recommendations will be key to achieving broad support and avoiding delays later in the process. 4. Iterative and collaborative workflow To support efficient progress, we will follow an iterative workflow, which includes: · Pairing focused discussion during meetings with substantive asynchronous work between meetings; · Rolling development of draft recommendations for each charter question; · Conducting periodic impact checks during the drafting process, rather than deferring all impact analysis to the end of the PDP. 1. Collaboration document for the WG to contribute, provide feedback, and change as the WG sees fit. · Based on the discussions to date and the language provided by Working Group members, leadership and staff have developed a working document to capture discussions and draft language for each charter question. · This document is intended to support clear navigation, transparency, and effective asynchronous work, allowing members to review, comment, and refine proposals between meetings in a structured way. · Each charter question is listed and 3 different coloured boxes are provided for each. · First (orange), the key takeaways from the previous discussion · Second box (green), the draft language provided by the WG and some overarching themes that can be derived from that language · Third (blue), a box for when the WG is ready to stabilise the language for their recommendation on each Charter Question. · Link:https://docs.google.com/document/d/1GxM-Yrgv6sZPEYU8ikW4cRM5YqWsJuWGiQ… Please take a look and provide your feedback within the document by the means of commenting on the document rather than making direct edits to the text. Staff will help us capture the comments and we can wordsmith the draft recommendations together as we iterate. . Thank you all for your continued contributions and great, positive energy that you are bringing to the conversation.Talk soon! Best, Paul

1 0

Re: [Ext] RE: Vice Chair Election Instructions (eBallot to be sent individually)
by John Emery March 24, 2026

March 24, 2026

Hello Marc and WG Members, As requested, the following is a compilation of the WG emails of each self-nomination for the role of Vice Chair. Those present at the first meeting in Mumbai were given a chance to speak as well for their candidacy and the timestamp of their statement can be found next to each name from the ICANN85 zoom recording linked in the google doc. As a disclaimer, this is solely a compilation of the emails sent to the list and the timestamp of speeches given at ICANN85 by the candidates compiled by staff. This is not a formal document of each candidate’s statement. The five Vice Chair candidates are listed in alphabetical order: https://docs.google.com/document/d/1zEV1K-eG15pjSHPNj6oDK2mqSktrF-Bf_HlxA_2… John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: "trachtenbergm(a)gtlaw.com" <trachtenbergm(a)gtlaw.com> Date: Monday, March 23, 2026 at 07:49 To: John Emery <john.emery(a)icann.org>, "gnso-dnsabuse-pdp(a)icann.org" <gnso-dnsabuse-pdp(a)icann.org> Subject: [Ext] RE: Vice Chair Election Instructions (eBallot to be sent individually) Do we want to give the candidates an opportunity to provide a brief written overview to staff which they can consolidate into a single document that the representative can share with their constituencies? Best regards, Marc H. Trachtenberg Shareholder Chair, Internet, Domain Name, e-Commerce and Social Media Practice Greenberg Traurig, LLP Aspen Chicago 411 E. Main Street 360 North Green Street Suite 207 | Aspen, CO 81611 Suite 1300 | Chicago, IL 60607 T +1.970.300.5313 T +1.312.456.1020 M +1.773.677.3305 M +1.773.677.3305 trac(a)gtlaw.com<mailto:trachtenbergm@gtlaw.com> | www.gtlaw.com [gtlaw.com]<https://urldefense.com/v3/__http:/www.gtlaw.com/__;!!PtGJab4!5IILrBTH_qlvfl…> | View GT Biography [gtlaw.com]<https://urldefense.com/v3/__https:/www.gtlaw.com/en/professionals/t/trachte…> [Greenberg Traurig Logo] [Greenberg Traurig Logo] From: John Emery via Gnso-dnsabuse-pdp <gnso-dnsabuse-pdp(a)icann.org> Sent: Monday, March 23, 2026 8:07 AM To: gnso-dnsabuse-pdp(a)icann.org Subject: [Gnso-dnsabuse-pdp] Vice Chair Election Instructions (eBallot to be sent individually) *EXTERNAL TO GT* Dear DNSAM PDP 1 WG, The time has come to elect the Vice Chair for this PDP. There are currently five candidates for Vice Chair: * Ching Chiao * Farell Folly * Anil Kumar Jain * Christabel Mebaghandu * Nick Wenban-Smith Once the Vice Chair is selected from the WG membership, their appointing organization may appoint a new member as a replacement. The process of voting will be a Ranked Choice vote, where every member of the PDP WG: Members and Participants (not Alternates) will have the opportunity to vote. You will vote by ranking all 5 candidates in order of preference. You must rank each candidate 1 through 5. If there is one candidate that receives a majority (>50%) in the first round of voting, they will be selected as Vice Chair. If the first round does not produce a majority in favor of a single candidate, then a second round of a vote will be taken of the top two candidates only. Each Member and Participant will cast a single vote for one of the two remaining candidates. You will be emailed an individual eBallot form for your voting. Please complete the form by Friday 27 March 23:59 UTC. John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<https://urldefense.com/v3/__http:/www.icann.org__;!!DUT_TFPxUQ!HkhQLhSjg9Ew…> ________________________________ If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster(a)gtlaw.com, and do not use or disseminate the information.

5 4

Straw Proposal
by Reg Levy March 23, 2026

March 23, 2026

All— As noted in the chat in the session today, this is the straw proposal a number of us have been working on for the last few days and we’d love additional input: 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. Servus, Reg -- Reg Levy | Associate General Counsel – Domains +1 (323) 880-0831 Tucows #MakingTheInternetBetter UTC +5:30

13 33

Vice Chair Election Instructions (eBallot to be sent individually)
by John Emery March 23, 2026

March 23, 2026

Dear DNSAM PDP 1 WG, The time has come to elect the Vice Chair for this PDP. There are currently five candidates for Vice Chair: * Ching Chiao * Farell Folly * Anil Kumar Jain * Christabel Mebaghandu * Nick Wenban-Smith Once the Vice Chair is selected from the WG membership, their appointing organization may appoint a new member as a replacement. The process of voting will be a Ranked Choice vote, where every member of the PDP WG: Members and Participants (not Alternates) will have the opportunity to vote. You will vote by ranking all 5 candidates in order of preference. You must rank each candidate 1 through 5. If there is one candidate that receives a majority (>50%) in the first round of voting, they will be selected as Vice Chair. If the first round does not produce a majority in favor of a single candidate, then a second round of a vote will be taken of the top two candidates only. Each Member and Participant will cast a single vote for one of the two remaining candidates. You will be emailed an individual eBallot form for your voting. Please complete the form by Friday 27 March 23:59 UTC. John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

2 1

Follow-up: WG Collaboration Document
by Feodora Hamza March 23, 2026

March 23, 2026

Sent on behalf of Paul McGrady Dear DNSAM PDP1 WG members, thank you for today’s call. As briefly noted before the meeting ended, I would like to take a moment to outline the plan for how the Working Group will approach its deliberations and methodology moving forward. We alluded to this during ICANN85 but it is always good to recap and make sure all members are on the same page. Firstly, it is encouraging to see the level of ambition within the group and the clear willingness to collaborate and develop workable solutions. This is the spirit of volunteerism that I love so much about our community. At the same time, our early discussions have demonstrated that reaching consensus will take time and due consideration, given the range of perspectives, needs, and considerations that proposed recommendations must undergo. There is no “silver bullet” but we do have good tools to accomplish our work in a timely, thorough fashion. 1. Staying within scope: As a reminder, the charter defines the scope of this PDP (the nature of our universe), and it is essential that our discussions remain within those boundaries. Where ideas arise that fall outside of scope, these can certainly be captured for future consideration by Council but should not slow down or divert our current work. I know it would be great to solve every problem all at once, but that is not what Council asked us to do. 2. Focus on recommendations: At this stage and as noted during our ICANN85 session 2 on Consensus Building, the Working Group should prioritize identifying needs and developing policy recommendations, rather than jumping directly to specific implementation/policy language solutions. This will help ensure that our outputs remain policy-focused and aligned with the role of the PDP. However, I do appreciate the specific language provided so far as it helps to inform where recommendations can go and can give us something concrete to haggle over. So, don’t be shy but understand we won’t be recommending specific contract language, just high level Policy. 3. Consensus building throughout the process: As highlighted in our consensus-building discussions, we should ensure that all SGs/Cs and community stakeholders understand not only what the Working Group is proposing, but also why. Drawing on lessons learned and best practices (including those captured in the consensus building playbook and ICANN85 session2), clear rationale and transparency in our recommendations will be key to achieving broad support and avoiding delays later in the process. 4. Iterative and collaborative workflow To support efficient progress, we will follow an iterative workflow, which includes: · Pairing focused discussion during meetings with substantive asynchronous work between meetings; · Rolling development of draft recommendations for each charter question; · Conducting periodic impact checks during the drafting process, rather than deferring all impact analysis to the end of the PDP. 1. Collaboration document for the WG to contribute, provide feedback, and change as the WG sees fit. · Based on the discussions to date and the language provided by Working Group members, leadership and staff have developed a working document to capture discussions and draft language for each charter question. · This document is intended to support clear navigation, transparency, and effective asynchronous work, allowing members to review, comment, and refine proposals between meetings in a structured way. · Each charter question is listed and 3 different coloured boxes are provided for each. · First (orange), the key takeaways from the previous discussion · Second box (green), the draft language provided by the WG and some overarching themes that can be derived from that language · Third (blue), a box for when the WG is ready to stabilise the language for their recommendation on each Charter Question. · Link:https://docs.google.com/document/d/1GxM-Yrgv6sZPEYU8ikW4cRM5YqWsJuWGiQ… Please take a look and provide your feedback within the document by the means of commenting on the document rather than making direct edits to the text. Staff will help us capture the comments and we can wordsmith the draft recommendations together as we iterate. . Thank you all for your continued contributions and great, positive energy that you are bringing to the conversation.Talk soon! Best, Paul

1 0

Post Call / DNS Abuse Mitigation PDP1 WG / Monday, 23 March 2026
by Julie Bisland March 23, 2026

March 23, 2026

Dear all, All recordings for the DNS Abuse Mitigation PDP1 WG call held on Monday, 23 March 2026 at 12:30 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/GQCSLQ> (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

Outcomes, Action Items, and Notes - 23 March 2026 - Meeting #5
by Steve Chan March 23, 2026

March 23, 2026

Dear DNSAM PDP 1, Please see the attached outcomes, action items, and notes from Meeting #5. Best, Steve [OUTCOMES] * None [ACTION ITEMS] * Action Item: Members and Participants to complete voting by the deadline. * Action Item: Staff to send email about work plan: https://docs.google.com/spreadsheets/d/1gDXM13Io8RJlYZVj0rhbfoMi7und3v9i/ed… * Action Item: WG Members to review work plan and provide feedback by 30 Mar, if any. * Action Item: Staff to send email about collaboration tool, which seeks to capture and distill verbal and email discussions to date. [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. 2. 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. 3. 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! 4. 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/ed… Action Item: WG Members to review work plan and provide feedback by 30 Mar, if any. 5. 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. 6. AOB * None 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

1 0

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

March 23, 2026

Dear all, The next DNS Abuse Mitigation PDP1 WG call will take place on Monday, 30 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 (30 March): https://tinyurl.com/yw2t37uy 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