Thank you, Feodora and Support Team. I’ve put a list of options for community engagement in the Google doc you set up for the team to review. I appreciate the help in getting this set up! Thanks, Sam From: Feodora Hamza via gnso-dnsabuse-smallteam <gnso-dnsabuse-smallteam@icann.org> Reply-To: Feodora Hamza <feodora.hamza@icann.org> Date: Tuesday, December 16, 2025 at 12:35 PM To: Julie Bisland <julie.bisland@icann.org>, farzaneh badii <farzaneh.badii@gmail.com>, "lawrence@microboss.org" <lawrence@microboss.org>, "Mohr, Susan" <Susan.Mohr@lumen.com>, Vivek Goyal <vivekg@ldotr.red>, "compsoftnet@GMAIL.COM" <compsoftnet@GMAIL.COM>, "gnso-dnsabuse-smallteam@icann.org" <gnso-dnsabuse-smallteam@icann.org> Cc: GNSO-Secs <gnso-secs@icann.org> Subject: [EXTERNAL] [gnso-dnsabuse-smallteam] Action Items and high-level notes: DNS Abuse Draft Charter Team / Tuesday, 16 December 2025 at 13:00 UTC Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Dear draft charter team, Please find below the high-level notes and action items from today`s meeting. The next meeting is scheduled for Friday, 19 December at 14:00 UTC. Kind regards, Feodora on behalf of the Support Team Action Items 1. Small Team to consult with their respective groups on membership model preference and seat allocation proposal 2. Sam to work on a Google document outlining potential mechanisms (e.g., special sessions, input channels, guardrails) to address openness and community input concerns within a representative model. 3. Staff to provide a starting point on Google Doc for Sam to develop further. 4. During the next meeting the group is expected to: i. Decide on the membership model ii. Progress toward resolving concerns with the seat allocation iii. Discuss pending comments on the draft charter Summary of discussion Majority support emerged for a representative working group model. Multiple SGs expressed support for a representative model as the most effective structure for this PDP, citing efficiency, continuity, and the need for relevant expertise. ALAC, some NCSG participants, and individual contributors continued to advocate for a representative-plus-open, emphasizing inclusivity. Consensus that expertise and continuity are critical success factors of a good WG model It was reaffirmed that all PDP participation models will allow observers by default, addressing some transparency and newcomer concerns. No agreement on seat allocation; issue remains unresolved a. Significant disagreement remains regarding: i. Whether NCSG should receive six seats ii. Whether existing two-seat-per-constituency allocations should remain unchanged iii. Whether registrars should receive additional seats due to implementation impact (3 seats) It was clarified that the PDP chair selection is separate from member seat allocation and handled via Council leadership and/or the Standing Selection Committee, not by working group member vote. From: Feodora Hamza <feodora.hamza@icann.org> Date: Monday, 15 December 2025 at 18:12 To: Julie Bisland <julie.bisland@icann.org>, farzaneh badii <farzaneh.badii@gmail.com>, "lawrence@microboss.org" <lawrence@microboss.org>, "Mohr, Susan" <Susan.Mohr@lumen.com>, Vivek Goyal <vivekg@ldotr.red>, "compsoftnet@GMAIL.COM" <compsoftnet@GMAIL.COM>, "gnso-dnsabuse-smallteam@icann.org" <gnso-dnsabuse-smallteam@icann.org> Cc: John Emery <john.emery@icann.org>, Steve Chan <steve.chan@icann.org>, GNSO-Secs <gnso-secs@icann.org> Subject: Action Items and high-level notes: DNS Abuse Draft Charter Team / Monday, 15 December 2025 at 13:00 UTC Dear draft charter team, Please find below the high-level notes and action items from today`s meeting. Due to the tight deadline of this group we are using the individual Email addresses instead of the distribution list, because not all members have enrolled via ICANN join. Important: We cannot add you to the small team’s roster or mailing list until we have received your enrollment. In addition, we cannot add you to attendance for today’s call until you have enrolled. If you have not yet enrolled, please enroll immediately (see email from Terri “Action needed | ICANN Join…” sent to ntfy-gnso-council@icann.org list); once enrolled, you will be added to the mailing list and member wiki page. Kind regards, Feodora on behalf of the Support Team ========== DNS Abuse PDP1 Draft Charter Team - Meeting 15 December Action Items Staff to circulate a redlined version of the charter reflecting discussion points. Councilors to Review the updated charter questions and redlines. Provide specific proposed text and rationale for any suggested changes, particularly where concerns exist about scope, safeguards, or impacts. to clarify that triggers are tied to DNS abuse cases, without embedding PDP answers in the question text. to Address potential overlap between questions on association criteria and investigation steps, including possible consolidation. Ensure questions on data access and privacy safeguards explicitly consider impacts on registrants and end users, and potential remedies. Councilors to prepare to discuss the WG model during the next call. Deadline for final input Friday 19 December. Discussion on Charter · The charter must be fit for purpose and finalized before the PDP on Associated Domain Checks can convene. · The charter must not pre-empt or perform the work of the PDP; it should only define the framework and questions for the PDP to answer. · The charter questions should: o Focus on what the PDP should examine, not how registrars must operationalize outcomes. o Avoid being overly prescriptive or revealing investigative methods that could be exploited by bad actors. o Several questions were identified as potentially overlapping (notably those on defining associations and investigation steps), and there was agreement to review consolidation or re-ordering. Human rights considerations · The GPI framework and Human Rights Impact Assessment are mandatory PDP requirements and are reflected in the charter. · There was agreement that repeating human rights language throughout every question is unnecessary and risks cluttering the charter. · Instead, participants agreed it is preferable to: o Capture these considerations once, clearly, in an overarching section (e.g., a chapeau, scope, or dedicated section), and o Avoid duplicating the same language in every charter question. o Where core values or standards are referenced, the preference is to link to authoritative sources rather than restating or partially listing them. Registrar business models · There was agreement that the PDP/Charter must take into account different registrar business models. · Similar to human rights considerations, participants agreed this should be stated once at a high level, rather than added to each individual question.