July 2025 - gnso-dnsabuse-smallteam

17 July 2025 Meeting Notes
by John Emery July 18, 2025

July 18, 2025

Dear DNS Abuse Small Team, Please see attached below the meeting notes and action items from our 17 July meeting of the DNS Abuse Small Team. Please look out for an email from Jen later today with the leadership and staff priorities list based on Small Team input thus far for discussion. DNS Abuse Small Team Wiki<https://icann-community.atlassian.net/wiki/x/iQCiCg> Slides<https://icann-community.atlassian.net/wiki/download/attachments/178389129/1…> ACTION ITEMS AI: Each group to come up with top 3 priorities for next week’s meeting that are appropriate for policy development. AI: Leadership and staff to provide priorities list for discussion and reaction from input already received. AI: Staff will start preparing the draft motion to present to small team to provide feedback 1. Welcome 2. Update on Preliminary Recommendations Document * Update on the Draft Report<https://docs.google.com/document/d/18AMsedMhKEox1196No0yS6ktqFbcTs2l/edit?u…> with additional two recommendations for discussion * The chart at the end of the document was removed and the full list of gaps in the matrix<https://docs.google.com/spreadsheets/d/18PdZnH3OQ65NT9g0lGE6Y2toFaCrtxyf/ed…> * Updated the list of gaps in the matrix including the phases and merged agreed upon cells and integrated CSG and NCSG input 3. Discussion on Issue Report * Previously 1 issue report resulted in 1 PDP, this Issue report will look more deeply in the list of gaps and will encompass all of that * Result of this one issue report will be a narrowly chartered PDP on one or two topics/gaps to complete the work expeditiously. * Subsequent PDPs could be initiated from this original issue report when the initial PDP completes it work 4. Discussion on “Prioritization” * How would we like to prioritize there have been indications of SGs/Cs for what should be prioritized * Who will decide? This will be a Council decision, the Small Team can recommend from the prioritization exercise. * Good to have priorities here to then make a recommendation to Council and then while Issue report is being worked on there may be other factors to consider * Suggestion to launch next PDP during public comment period going with a single issue report * As PDP is underway the next step can be a chartering team for the next set of work In the Chat: CSG priorities are: 1. Associated domain check. 2. Continual review and update of DNS abuse definitions. 3. Validation of registrant details. 4. Access to bulk / API registrations * Caution prioritization exercise from Council that a continuing small team. A PDP, a charter drafting team, a small team, and another PDP there could be resource constraints * How this Small Team wants to prioritize with the At Large priorities in the slides<https://icann-community.atlassian.net/wiki/download/attachments/178389129/1…> * ALAC input based on the matrix and were careful not to go into solutions to provide input on the gap itself. The possible solutions list can be litigated later as it is a raw list based on the matrix. * ALAC list could be revised based on how the inputs will be resolved and the priorities of the other groups * Do we prioritize low hanging fruit? For those items for the first PDP, do they necessarily need to be topics where PDPs are appropriate to address? * Calling for the issue report will lay foundational work for the first and subsequent PDPs. This will be looking at whether the gaps will be fit for PDP. * AI: each group come up with top 3 priorities for next week’s meeting that are appropriate for policy development * Also CPH DNS Abuse working group will have something coming along soon * Determine what is a PDP focus and what is for other parts of the community. We can cover more gaps if some things should just be referred back to ICANN compliance * Intention is to focus on what makes most sense for inclusion in PDP specifically, framing for low hanging fruit. PDP work with topics that are important and impactful, wide agreement, and perhaps easier to implement * Reminder: only two more meetings with this Small Team * AI: Leadership and staff to provide priorities list for discussion and reaction from input already received * There is a time crunch meeting on the 31st need to have finalized recommendation and matrix for the annex for the 4 August deadline * Limiting scope to topics appropriate for policy development and put in writing the low hanging fruit * AI: Staff will start preparing the draft motion 5. AOB- Next Steps 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

Post Call | GNSO Council DNS Abuse Small Team meeting | 17 July 2025
by Julie Bisland July 17, 2025

July 17, 2025

Dear all, Please use link below to access the attendance and the recording links on the small team wiki page for the GNSO Council DNS Abuse Small Team meeting held on Thursday, 17 July 2025 at 14:00 UTC. DNS Abuse Small Team Wiki: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you! Kind regards, Julie Policy Team Supporting the GNSO

1 0

Meeting Invitation | GNSO Council's DNS Abuse Small Team call | Thursday, 24 July 2025
by Julie Bisland July 17, 2025

July 17, 2025

Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 24 July 2025 at 14:00 UTC for 60 minutes. Join from PC, Mac, iPad, or Android: Zoom Webinar link: https://icann.zoom.us/j/91555564642?pwd=QnlKeXhycVVJdklMUHJTTjlsdnhRQT09 Passcode:4^NT$6A9$. Audio only: Webinar ID: 915 5556 4642 Passcode: 6982547835 International numbers available: https://icann.zoom.us/u/abKXhMNgh Wiki space: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | GNSO Council's DNS Abuse Small Team call | Thursday, 17 July 2025
by Terri Agnew July 17, 2025

July 17, 2025

Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 17 July 2025 at 14:00 UTC for 60 minutes. Join from PC, Mac, iPad, or Android: Zoom Webinar link: https://icann.zoom.us/j/91555564642?pwd=QnlKeXhycVVJdklMUHJTTjlsdnhRQT09 Passcode:4^NT$6A9$. Audio only: Webinar ID: 915 5556 4642 Passcode: 6982547835 International numbers available: https://icann.zoom.us/u/abKXhMNgh Wiki space: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you. Kind regards, Terri Policy Team Supporting the GNSO

5 4

**15-MINUTE REMINDER** Meeting Invitation | GNSO Council's DNS Abuse Small Team call | Thursday, 17 July 2025
by Julie Bisland July 17, 2025

July 17, 2025

**15-MINUTE REMINDER** Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 17 July 2025 at 14:00 UTC for 60 minutes. Join from PC, Mac, iPad, or Android: Zoom Webinar link: https://icann.zoom.us/j/91555564642?pwd=QnlKeXhycVVJdklMUHJTTjlsdnhRQT09 Passcode:4^NT$6A9$. Audio only: Webinar ID: 915 5556 4642 Passcode: 6982547835 International numbers available: https://icann.zoom.us/u/abKXhMNgh Wiki space: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Meeting Notes 9 July 2025 DNS Abuse
by Steve Chan July 17, 2025

July 17, 2025

Dear All, Please see the notes and actions items from the DNS Abuse Small Team call on 3 July 2025. Best, Steve DNS Abuse Small Team Wiki<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/iQC…> Action Items * Transpose new comments from At-Large * Councilors to check in with their groups and identify its priority topics and/or what represents low hanging fruit. Welcome * Greetings from World Summit on the Information Society (WSIS)+20 High-Level Event 2025! * Handing off to staff for facilitation today, about halfway through. Continued Discussion of List of Gaps – New Feedback * Reviewing G5 & G32 – no comments * Reviewing G8 & G14 * Might not be relevant for policy making necessarily * Reviewing G18 & G22 * Justine to check in with At-Large on input related to items that did not poll as high-priority. However, new input has been added. * For RySG/RrSG, detailed info about mitigating DNS Abuse provides blueprint to bad actors. Need to be mindful of this concern in thinking how/what info to share in reporting. This seems like another item that ICANN Compliance could take on not directly (perhaps suggested by this small team/Issue Report). * Where policy development may not be the optimal path forward, capture the intention and cascade throughout the documentation (small team report/gap analysis, in Issue Report, reflect (or not) in draft charter). * DGA work headed up by Keith Drazek and being discussed in the ccNSO. Might be evidence that this work doesn’t need to be in policy development. * Reminder – Compliance is undertaking new initiatives to evolve their enforcement. Should seek to integrate the impact of these new initiatives in both our small team report and in the Issue Report, if relevant. * Generally appreciative of the approach of making progress where possible, without always relying on policy development. However, for audits, there is often pushback about being asked for certain things, especially if the action is not required (e.g., gathering certain types of data). There is some nervousness about the PDP being too big/broad in scope and the PDP gets bogged down. How can we make sure to capture the point that this work can be done efficiently and effectively? Capturing alternative methods to address may help, especially in the small team report. As well as Councilors communicating to their constituents. The report can also emphasize where consensus can be found. * Reviewing G3 & G30 – no comments * Reviewing G11, G23, & G26 * NCSG comments added by staff where it seemed appropriate. NCSG Councilors should take a look to ensure that the comments were assigned appropriately. * Reviewing new CSG input – no comments Action Item – Transpose new comments from At-Large Review Preliminary Recommendations Document * The suggested edits come from the mindset of getting the scope and sequencing of work right. * Clarifying comments - draft charter is integrated into the Preliminary Issue Report, subject to public comment, and subject to further amendment from Council. * There is concern about the efficiency and effectiveness of a PDP. One idea is to only include a charter for the first topic (or two). Some concerns about the approach though as it might not be apparent which items should be prioritized. * Question about who drafts the subsequent charters for future work if not everything is captured in the first chartered work. It would be Council or a small team of Councilors. * Initial thought from staff is to frame as a multi-phased PDP but taking into account comments from small team members, perhaps limited to just two or maybe no more than 3 topics. * In terms of identifying items, the GAC has suggested their priority topics. * Generally, it’s presented as 1:1 between Issue Report and PDP. However, there could be creative options available, like only initiating work on a subset of issues. * Suggestion from staff that the associated domain check and gating of APIs seem to be the topics where the community has aligned. Councilors unable to respond on the fly. Action Item – Councilors to check in with their groups and identify its priority topics and/or what represents low hanging fruit. * For the preventative gaps, some concern about the suggestions to disregard economic issues. Agreement that pricing restrictions must be avoided, but need to at least be able to track down the information of the bad actor. Update to GNSO Council * Update will be sharing progress to date and ensuring awareness that the expectation is a request for an Issue Report in August. Looking Ahead: August Council Vote Request for Issue Report * No comments AOB * Next call to revert to normal time and day - Thursday, 17 July 2025 at 14:00 UTC for 60 minutes 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> Skype: steve.chan55 Mobile: +1.310.339.4410 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

Proposed Agenda DNS Abuse Small Team 17 July 14:00 UTC
by Feodora Hamza July 16, 2025

July 16, 2025

Dear DNS Abuse Small Team, Please find below the proposed agenda for our next call. Proposed Agenda DNS Abuse Small Team 17 July 14:00 UTC 1. Welcome 2. Update on Preliminary Recommendations Document 3. Discussion on Issue Report 4. Discussion on “Prioritization” 5. AOB- Next Steps Kind regards, Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Re: [Ext] Re: Meeting Notes 3 July 2025 DNS Abuse
by Steve Chan July 9, 2025

July 9, 2025

Hi Lawrence, Apologies for not getting your comment quite right. The usual caveat applies to the notes that staff provides – they should not be considered a substitute for recordings and where available, transcripts. Thank you though for clarifying your point in your email. Best, Steve From: "Lawrence O. Olawale-Roberts" <lawrence(a)microboss.org> Date: Tuesday, July 8, 2025 at 5:41 PM To: Steve Chan <steve.chan(a)icann.org>, "gnso-dnsabuse-smallteam(a)icann.org" <gnso-dnsabuse-smallteam(a)icann.org> Subject: [Ext] Re: [gnso-dnsabuse-smallteam] Meeting Notes 3 July 2025 DNS Abuse Thanks for the notes Steve. Am not satisfied with the frame of capture on my point as it impacts the Review of G6, G7, and G21. Again whilst we would like to be careful on issues around pricing, it does have a significant impact on the scale of DNS Abuse. To mitigate this, we would expect that the business put in place certain key measures before providing discounted rates with a view to eliminating opportunities for such programs to be used by bad actors. For this reason we presume further policy work in necessary. Lawrence. ----- Error! Filename not specified. Error! Filename not specified. Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence(a)microboss.org<mailto:Lawrence@microboss.org> Error! Filename not specified. Error! Filename not specified. …collaboration to enhance communication. Error! Filename not specified. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!5AG_Ttiq4…> | Error! Filename not specified.[facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJ…> Error! Filename not specified.[linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/microbosstech/_…> Error! Filename not specified.[mobile.twitter.com]<https://urldefense.com/v3/__https:/mobile.twitter.com/microbosstech__;!!PtG…> Error! Filename not specified.[instagram.com]<https://urldefense.com/v3/__https:/www.instagram.com/microbosstech/?hl=en__…> Error! Filename not specified.[youtube.com]<https://urldefense.com/v3/__https:/www.youtube.com/@microboss__;!!PtGJab4!5…> This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient, you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and his company MicroBoss. Kindly note that whilst we scan all e-mails for viruses, we cannot guarantee that any e-mail is virus-free. | Do consider the environment before printing this email. ________________________________ From: Steve Chan via gnso-dnsabuse-smallteam <gnso-dnsabuse-smallteam(a)icann.org> Sent: Thursday, July 3, 2025 5:00:50 PM To: gnso-dnsabuse-smallteam(a)icann.org <gnso-dnsabuse-smallteam(a)icann.org> Subject: [gnso-dnsabuse-smallteam] Meeting Notes 3 July 2025 DNS Abuse Dear All, Please see the notes and actions items from the DNS Abuse Small Team call on 3 July 2025. Best, Steve DNS Abuse Small Team Wiki<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/iQC…> Action Items * Pull in Farzaneh and NCSG comments into the worksheet * Add the gap to the list (informing a complainant of the outcome of the investigation) * Small team members to review gap report preliminary recommendations document by Thursday, 10 July * Distribute Doodle poll to reschedule Thurs call Welcome * None Discuss List of Gaps – New Feedback * Reviewing G1 * Here and in general, the At-Large focused on identifying topics that they believe are high priority. Confirmed that the At-Large focused on determining which issues should be investigated. * Retail registrars will have visibility, but resellers might not. * An associated domain check must be done with care. There is the possibility of profiling, infringement of privacy. * Important considerations that will be relevant to deliberations, not necessarily the time to go into details now. The framing of this topic might be too prescriptive. Agreement that it’s hard to refrain from discussing merits of the issues and trying to develop solutions. * Clear interest in including this topic for policy development. Action Item: Pull in Farzaneh and NCSG comments into the worksheet * Reviewing G10 * Data feeds need to be considered with a grain of salt. * Reviewing G17 and G27 * The RySG doesn’t see this topic as a subject for policy development, but the At-Large sees it a high priority item. The most important element/gap is informing a complainant of the outcome of the investigation. * The CSG also noted the gap. Not seeking to be prescriptive about whether this topic would warrant policy development. * Important to coordinate both the submission of complaints as well as the point raised by the At-Large. * However, if the Ry/Rrs are not compelled to provide a response, would they still do it? Policy development could ensure that this is a baseline requirement, for both the collection and resolution of complaints. * There are already requirements for Ry/Rrs to have a mechanism to accept complaints. However, there seems to be a lack of education for reporters, which may not warrant policy development. Action Item: Add the gap to the list (informing a complainant of the outcome of the investigation). * Reviewing G19 and G24 – no comments * Reviewing G31, G4, and G13 * In respect of G4, RySG had already identified as a gap. Believe it warrants additional work. * NCSG also believes that this is a high-priority. Concern about attributing the identification of the issue to only NetBeacon WP. * Reviewing G13 * Divergence about whether this topic warrants policy development. CSG believes it is important to close the loop, accepting that cases can be so different. * A path could be to increase the baseline of actions warranted, but dictating timeframes can be problematic. * Clarification that the SLAs could be for specific types of abuse, not all types. * Clarification that the 24 hr response time is for LEA * Reviewing G15 and G20 * At-Large did not seek to determine the path to resolve gaps. It may indeed be the case that this gap would not warrant policy development. * Reviewing G29 - none * Reviewing G2, G9, G12, and G25 * G9 and G12 do seem like a gap, it seems like a compliance issue. * Suggestion to combine G2 and G1 * Concerns about the obligations of resellers. * NCSG does not believe G12 is a gap. * Reviewing G6, G7, and G21 * NCSG does not think pricing should even be in consideration as a best practice * Bylaws prevent policy development about pricing. * Suggestion that the Issue Report will help clarify what is and is not appropriate for policy development. Therefore, it might actually be helpful to include. * General question about how Bylaws changes can be effectuated. * Clash with Council call. Need to consider rescheduling if we want to review line by line. * Reminder of focus – the small team’s report should highlight what should and should not be included in the Issue Report. Discuss Preliminary Recommendations Document * Consider adding a note that in respect of certain issues, a PDP might not be the only or best outcome. * In respect of the PDP itself, wariness of parallel processes. * Need to clarify language about recommendation for PDP Action Item: Small team members to review gap report preliminary recommendations document by Thursday, 10 July Action Item: Distribute Doodle poll to reschedule Thurs call Prioritization Discussion from Preliminary Recommendations Document * None 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> Skype: steve.chan55 Mobile: +1.310.339.4410 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…> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Meeting Notes 3 July 2025 DNS Abuse
by Steve Chan July 9, 2025

July 9, 2025

Dear All, Please see the notes and actions items from the DNS Abuse Small Team call on 3 July 2025. Best, Steve DNS Abuse Small Team Wiki<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/iQC…> Action Items * Pull in Farzaneh and NCSG comments into the worksheet * Add the gap to the list (informing a complainant of the outcome of the investigation) * Small team members to review gap report preliminary recommendations document by Thursday, 10 July * Distribute Doodle poll to reschedule Thurs call Welcome * None Discuss List of Gaps – New Feedback * Reviewing G1 * Here and in general, the At-Large focused on identifying topics that they believe are high priority. Confirmed that the At-Large focused on determining which issues should be investigated. * Retail registrars will have visibility, but resellers might not. * An associated domain check must be done with care. There is the possibility of profiling, infringement of privacy. * Important considerations that will be relevant to deliberations, not necessarily the time to go into details now. The framing of this topic might be too prescriptive. Agreement that it’s hard to refrain from discussing merits of the issues and trying to develop solutions. * Clear interest in including this topic for policy development. Action Item: Pull in Farzaneh and NCSG comments into the worksheet * Reviewing G10 * Data feeds need to be considered with a grain of salt. * Reviewing G17 and G27 * The RySG doesn’t see this topic as a subject for policy development, but the At-Large sees it a high priority item. The most important element/gap is informing a complainant of the outcome of the investigation. * The CSG also noted the gap. Not seeking to be prescriptive about whether this topic would warrant policy development. * Important to coordinate both the submission of complaints as well as the point raised by the At-Large. * However, if the Ry/Rrs are not compelled to provide a response, would they still do it? Policy development could ensure that this is a baseline requirement, for both the collection and resolution of complaints. * There are already requirements for Ry/Rrs to have a mechanism to accept complaints. However, there seems to be a lack of education for reporters, which may not warrant policy development. Action Item: Add the gap to the list (informing a complainant of the outcome of the investigation). * Reviewing G19 and G24 – no comments * Reviewing G31, G4, and G13 * In respect of G4, RySG had already identified as a gap. Believe it warrants additional work. * NCSG also believes that this is a high-priority. Concern about attributing the identification of the issue to only NetBeacon WP. * Reviewing G13 * Divergence about whether this topic warrants policy development. CSG believes it is important to close the loop, accepting that cases can be so different. * A path could be to increase the baseline of actions warranted, but dictating timeframes can be problematic. * Clarification that the SLAs could be for specific types of abuse, not all types. * Clarification that the 24 hr response time is for LEA * Reviewing G15 and G20 * At-Large did not seek to determine the path to resolve gaps. It may indeed be the case that this gap would not warrant policy development. * Reviewing G29 - none * Reviewing G2, G9, G12, and G25 * G9 and G12 do seem like a gap, it seems like a compliance issue. * Suggestion to combine G2 and G1 * Concerns about the obligations of resellers. * NCSG does not believe G12 is a gap. * Reviewing G6, G7, and G21 * NCSG does not think pricing should even be in consideration as a best practice * Bylaws prevent policy development about pricing. * Suggestion that the Issue Report will help clarify what is and is not appropriate for policy development. Therefore, it might actually be helpful to include. * General question about how Bylaws changes can be effectuated. * Clash with Council call. Need to consider rescheduling if we want to review line by line. * Reminder of focus – the small team’s report should highlight what should and should not be included in the Issue Report. Discuss Preliminary Recommendations Document * Consider adding a note that in respect of certain issues, a PDP might not be the only or best outcome. * In respect of the PDP itself, wariness of parallel processes. * Need to clarify language about recommendation for PDP Action Item: Small team members to review gap report preliminary recommendations document by Thursday, 10 July Action Item: Distribute Doodle poll to reschedule Thurs call Prioritization Discussion from Preliminary Recommendations Document * None 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> Skype: steve.chan55 Mobile: +1.310.339.4410 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…>

4 4

Post Call | GNSO Council DNS Abuse Small Team meeting | 09 July 2025
by Terri Agnew July 9, 2025

July 9, 2025

Dear all, Please use link below to access the attendance and the recording links on the small team wiki page for the GNSO Council DNS Abuse Small Team meeting held on Wednesday, 09 July 2025 at 12:00 UTC. DNS Abuse Small Team Wiki: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0