Dear DNS Abuse Small Team,
Hope you have all arrived safely in Prague (or if you are joining us online, hope the hours are kind to you). A reminder to take advantage of the Prague meeting to discuss the homework with your SG/Cs:
Gap matrix: https://docs.google.com/spreadsheets/d/18PdZnH3OQ65NT9g0lGE6Y2toFaCrtxyf/edit?gid=1836517289#gid=1836517289
As mentioned on our last call, the ST will not have any meeting time during the Prague meeting (other than our already scheduled Council meeting), but there are sessions on the schedule that will discuss DNS abuse that we as the ST should keep our eyes and ears open and follow to the best that our schedules allow. Please note this list is taken from the slide deck from our June 5 call – if we have missed any session please do add to this list.
Monday 9 June
13:45 South Hall 2 (GNSO)
Tuesday 10 June
09:00 Forum Hall (GAC)
09:00 South Hall C (At Large)
10:45 Forum Hall (GAC)
Wednesday 11 June
10:45 South Hall 2 (GNSO)
13:45 South Hall 3 A/B (ccNSO)
Thursday 12 June
10:45 South Hall 3 C (At Large)
At-large Plenary Session 2- Progressing DNS Abuse Mitigation Efforts Within ICANN https://icann83.sched.com/event/246Xv/at-large-plenary-2-progressing-dns-abuse-mitigation-efforts-within-icann
Thanks all!
Best,
Jen
From: jen@dot.asia <jen@dot.asia>
Sent: Wednesday, June 4, 2025 4:21 AM
To: 'gnso-dnsabuse-smallteam@icann.org' <gnso-dnsabuse-smallteam@icann.org>
Subject: Draft Categorization of DNS Abuse Mitigation Gaps
Dear DNS Abuse Small Team,
Following our recent discussions over the past three meetings, please find here a draft categorization/clustering of the identified gaps in DNS abuse mitigation. The categorization is derived from the list of gaps shared during our last meeting. This draft reflects the key themes and inputs gathered from our group’s review of the ICANN Org reports, the INFERMAL study, the NetBeacon White Paper, and other relevant materials mentioned in the assignment form.
The aim of this categorization is to support a more structured and accessible discussion, particularly as we prepare for further engagement during ICANN83. It is intended to serve as a working tool to help cluster the gaps into overarching themes and which gaps may be best addressed through the ICANN Policy Development Process (PDP) and further investigated in an Issue Report, as well as which might be outside ICANN`s remit.
Importantly, this version remains preliminary. Our collective input is essential to refine and expand on this list. Please include comments, corrections and additional suggestions.
Items to consider when discussing and socializing this list within your respective SG/Cs, SO/ACs:
· Whether the categorization/clustering aligns with your understanding of each gap
· Any gaps you feel are missing or misclassified
· Opportunities to clarify where further analysis is needed
The goal of this exercise, aside from focusing our discussions, is to assist in identifying gaps and investigating further through an ICANN Issue Report as appropriate. As mentioned on the last call, the Request for Issue Report template expects a name of a Councilor but does not preclude the request coming from the Small Team, which is comprised of Councilors, if that our preference.
Finally, please do come prepared to discuss your SG/C/SO/AC’s input during our next scheduled call (June 20), thank you in advance for your review and contributions.
Best,
Jen