June 2025 - gnso-dnsabuse-smallteam

Preliminary DNS Abuse Small Team Draft Report to Council and Updated Matrix
by Feodora Hamza June 27, 2025

June 27, 2025

Dear Small Team Members, As discussed during the recent call, please find attached the preliminary draft of the DNS Abuse Small Team Report to Council. This draft reflects the updated and cleaned table, which has been revised based on your input into the matrix. Please also find below the updated google sheet/matrix, which we have aimed to make more user-friendly and where we have incorporated contributions from the RrSG, while addressing the comments received thus far. * Draft Report: https://docs.google.com/document/d/18AMsedMhKEox1196No0yS6ktqFbcTs2l/edit * Updated Matrix: https://docs.google.com/spreadsheets/d/18PdZnH3OQ65NT9g0lGE6Y2toFaCrtxyf/ed… We kindly ask you to review the draft and share any comments, edits or suggestions prior to the next DNS Abuse Small Team meeting scheduled for 3 July 14:00 UTC. The draft will be updated further once the feedback on the “list of gaps” from other SGs and Cs has been received. Thank you all for your contribution on this. We look forward to your further feedback. Kind regards, Feodora on behalf of Support Staff

1 0

Meeting Notes 26 June 2025 DNS Abuse
by John Emery June 26, 2025

June 26, 2025

Dear All, Please the attached notes below for the meeting of the DNS Abuse Small Team on 26 June 2025: DNS Abuse Small Team 26 June 2025 Meeting Notes DNS Abuse Small Team Wiki<https://icann-community.atlassian.net/wiki/x/iQCiCg> Slides<https://icann-community.atlassian.net/wiki/download/attachments/178389129/u…> ACTION ITEMS AI: Staff to clarify in questions for clarification by replying to comments within the document 1. Welcome 2. Discuss list of gaps – new feedback * Shared this document<https://docs.google.com/spreadsheets/d/18PdZnH3OQ65NT9g0lGE6Y2toFaCrtxyf/ed…> and went over new positions from each SG/C (early input as the official deadline is next week) * RySG G17 and G27 seem similar. How can it be easier to submit reports to take action on them? They should be worked on as a single initiative * RySG G1 and G10 these perhaps should not be tied together as preventive measures. It could be difficult on the CP side because the level of evidence is not at the same rigor as an actionable complaint * Aim is to narrow the total number of gaps, should be a clear indication that this could be a future area of work. * RySG G30 and G1 could be couched together. * Agreement with G30 and G1 brought together, flag where we think things can be combined * G2 and G31 are not the same, but some kind of friction in API to new customers, it would also be sensible to consider other kinds of contractual friction. Because of theme categorization, what is the underlying subject matter and intent, some could be grouped back together. * NCSG input shared via this document<https://docs.google.com/document/d/1W9_fBXRjgDNGXiWf61JOHn3YAPE2qMgqtSGIdrg…> * NCSG reminded about the Human Rights impact assessment * This exercise will be moving toward a call for Issue Report * IPC a couple of comments unsure where the context comes from for example G24 AI: Staff to clarify in questions for clarification by replying to comments within the document * NCSG comments imply that some of these gaps are not gaps, but measures that CPs don’t take because it has consequences for them. Discussing these gaps we have to consider why these measures have not been implemented * Mitigation measures cannot always be transparent and will be learned by abusers and make it harder to mitigate abuse 3. Discuss reply from ICANN Org * Discussed the following document<https://icann-community.atlassian.net/wiki/download/attachments/178389129/I…> from ICANN org Compliance * Perhaps the path forward is to factor their replies into the gap analysis review. There were some gaps already identified to see if they address or do not address the gaps identified * Q 1: The discussion of the investigations and remediation plans completed is an indication that compliance had not been able to do that before. * There was a general discussion about wanting a bit more detail from question 3, but it was unsurprising. * Amendments have been helpful, conduct investigations, and enforce mitigation, if there should be more rigorous enforcement it has to be listed out via contracts or ICANN consensus policies. * A lot of compliance webinars are building education materials for RySG and RrSG, it remains a work in progress. Gap for compliance to start to work on that and give a timeline on when that can happen * Gaps in RAA language on “reasonable and prompt” did the contractual amendments fix that? G29, G20, G15, or can say that these gaps have been partially addressed * Looking at gaps list G29 from the 2022 DNS abuse report it has been partially addressed from the answers from compliance. * The other enforcement challenges are in between the lines that the data compliance has been identified after the contract amendments have been implemented. Based on the NetBeacon analysis it is now worthwhile to see if it still persists based on the answers from compliance * The list of gaps on enforcement challenges have not been named directly by the report as a gap, this has been the work of the small team. Looking between the lines and the data, you can always go further than what we currently have. Is this a real issue or does not fit into what the community would like to do for the Issue Report 4. Present preliminary recommendation document * Request an issue report by August, staff drafted a small report as outlined in the slides <https://icann-community.atlassian.net/wiki/download/attachments/178389129/u…> and in this document<https://docs.google.com/document/d/18AMsedMhKEox1196No0yS6ktqFbcTs2l/edit?u…> * This included a key findings of the gap analysis in a more readable format * Discussion of the prioritization column, for all of them or only for some listed? As some may be more valuable than others. These will not be taken as a whole row. * Staff: Intention is to have Council vote on request for Issue Report in the August meeting. July AOB is allocated to present to Council the current state of the Small Team * Specific question in the issue report is done in consultation with ICANN legal Thank you, 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 | 26 June 2025
by Julie Bisland June 26, 2025

June 26, 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, 26 June 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, 03 July 2025
by Julie Bisland June 26, 2025

June 26, 2025

Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 03 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

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

June 26, 2025

**15-MINUTE REMINDER** Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 26 June 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

FW: [Ext] GNSO DNS Abuse Small Team - DNS Abuse Gaps Doc
by Terri Agnew June 26, 2025

June 26, 2025

Hi all, Please see attached. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: "Hong-Fu(Tom) Meng" <hfmeng(a)net-chinese.com.tw> Reply-To: "Hong-Fu(Tom) Meng" <hfmeng(a)net-chinese.com.tw> Date: Thursday, June 26, 2025 at 8:13 AM To: Terri Agnew <terri.agnew(a)icann.org>, Jennifer Chung <jen(a)dot.asia> Subject: Re: [Ext] GNSO DNS Abuse Small Team - DNS Abuse Gaps Doc Hi Jen and Terri, Here is an updated version of RrSG comments for the document. Thank you. Hong-Fu(Tom) Meng -----Original message----- From:Hong-Fu(Tom) Meng<hfmeng(a)net-chinese.com.tw> To:Terri Agnew<terri.agnew(a)icann.org>,Jennifer Chung<jen(a)dot.asia> Date: Fri, 20 Jun 2025 22:45:37 Subject: Re: [Ext] GNSO DNS Abuse Small Team - DNS Abuse Gaps Doc Hi Terri and Jen, Please use this new document. I have anonymised the comments. Thank you. Kind regards, Hong-Fu(Tom) Meng Hong-Fu(Tom) Meng / Net-Chinese Co., Ltd. & NETalent Co., Ltd. Phone: +886-225311416 E-mail: hfmeng(a)net-chinese.com.tw CONFIDENTIALITY NOTICE: This electronic message and any attachments may be confidential. If you are not the intended recipient, please do not disclose the contents to anyone, and notify the sender by e-mail; delete the message and destroy all printed hard copies. Thank you for your cooperation. 孟紅福 / 網路中文資訊股份有限公司 & 網中智庫股份有限公司電話：(02)25311416 信箱：hfmeng(a)net-chinese.com.tw 地址：台北市中山北路二段46號2樓保密警語：本信件及附件內容可能為機密性資料，若您並非被指定之收信人或在任何原因未經授權的情形之下收到本信件，請勿揭曉本信件內容於任何人，並請告知原發信人，以及請從您的電腦刪除此信件和任何已列印的文件。謝謝您的合作。 -----Original message----- From:Terri Agnew<terri.agnew(a)icann.org> To:Hong-Fu(Tom) Meng<hfmeng(a)net-chinese.com.tw>,jen<jen(a)dot.asia> Date: Fri, 20 Jun 2025 22:33:37 Subject: Re: [Ext] GNSO DNS Abuse Small Team - DNS Abuse Gaps Doc Hi Hong Fu, We confirm receipt. Thanks! Terri From: "Hong-Fu(Tom) Meng" <hfmeng(a)net-chinese.com.tw> Reply-To: "Hong-Fu(Tom) Meng" <hfmeng(a)net-chinese.com.tw> Date: Friday, June 20, 2025 at 9:28 AM To: Terri Agnew <terri.agnew(a)icann.org>, jen <jen(a)dot.asia> Subject: [Ext] GNSO DNS Abuse Small Team - DNS Abuse Gaps Doc Hi Jen and Terri, Apologize for the late reply on the DNS Abuse Gaps Lists document. Here is the document as attached, and if time extension is allowed, I will go back to RrSG for more input to the document. Thank you. Kind regards, Hong-Fu(Tom) Meng Hong-Fu(Tom) Meng / Net-Chinese Co., Ltd. & NETalent Co., Ltd. Phone: +886-225311416 E-mail: hfmeng(a)net-chinese.com.tw CONFIDENTIALITY NOTICE: This electronic message and any attachments may be confidential. If you are not the intended recipient, please do not disclose the contents to anyone, and notify the sender by e-mail; delete the message and destroy all printed hard copies. Thank you for your cooperation. 孟紅福 / 網路中文資訊股份有限公司 & 網中智庫股份有限公司電話：(02)25311416 信箱：hfmeng(a)net-chinese.com.tw 地址：台北市中山北路二段46號2樓保密警語：本信件及附件內容可能為機密性資料，若您並非被指定之收信人或在任何原因未經授權的情形之下收到本信件，請勿揭曉本信件內容於任何人，並請告知原發信人，以及請從您的電腦刪除此信件和任何已列印的文件。謝謝您的合作。

1 0

Proposed Agenda DNS Abuse Small Team 26 June 14:00 UTC
by Feodora Hamza June 25, 2025

June 25, 2025

Dear DNS Abuse Small Team, Please find below the proposed agenda for our next call. Please also find attached the reply document from ICANN Org regarding the questions posed by the Small Team. Proposed Agenda DNS Abuse Small Team 26 June 14:00 UTC 1. Welcome 2. Discuss list of gaps – new feedback 3. Discuss reply from ICANN Org 4. Present preliminary recommendation document 5. AOB 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

REMINDER | Meeting Invitation | GNSO Council's DNS Abuse Small Team call | Thursday, 26 June 2025
by Terri Agnew June 25, 2025

June 25, 2025

Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 26 June 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

3 2

MEETING CANCELLED | DNS Abuse Small Team | 10 July 2025
by Devan Reed June 24, 2025

June 24, 2025

Dear all, Please note that the 10 July meeting has been cancelled due to it conflicting with the GNSO Council Meeting. Please make sure to remove it from your calendars. The 26 June meeting will go ahead as planned this week. Thank you! Kind regards, Devan

1 0

Canceled: GNSO Council's DNS Abuse small team
by ICANN Policy Calendar June 24, 2025

June 24, 2025

**Starting with 26 June 2025, adjusted start time from 14:10 UTC to 14:00 UTC (on series) Meeting: GNSO Council's DNS Abuse Small Team Date/Time: Every Thursday at 14:00 UTC for 1 hour, 26 June – 31 July 2025 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

1 0