Dear DNS Abuse Small Team members,
Please find below the notes and Action Items from the last meeting.
The next meeting is scheduled for 20 June at 14:10 UTC.
Kind regards,
Feodora
DNS Abuse Small Team 2024-2025
·
Small Team Lead opened the meeting and introduced the
agenda.
·
ICANN Org presented a list of gaps in DNS Abuse
mitigation based on data reviewed during the last Small Team meeting.
·
The matrix consolidates DNS abuse gaps from multiple sources.
·
It is a non-exhaustive working document, inviting Small Team input.
·
Gaps noted do not reflect consensus. Small team input is needed for validation and refinement.
·
The matrix includes a column for comments. Small Team members are encouraged to:
o
Indicate agreement/disagreement with identified gaps.
o
Suggest new gaps or sources to be added to the list.
·
Small Team is encouraged to add more studies, where relevant.
·
ICANN Org explained why the reports discussed today and in the last meeting were chosen and how they are directly linked to ICANN.
·
Summary of Discussion:
§
Emphasized not mandating pricing changes in the context of policy development, as this is outside the remit of policy-making.
§
Policy recommendations should include Human Rights Impact Assessments (HRIAs).
§
Small Team’s role is to recommend gaps/issues to the Council, not make policy recommendations.
§
Mixed support for inviting study authors (e.g. INFERMAL Study, NetBeacon White Paper) given limited remit of this Small Team. Must be targeted and purpose-driven, such as clarifying unclear data points,
not to discuss potential solutions.
·
Gap List Categorization:
o
Organize issues by theme/topic rather than by source.
o
May inform how SGs/constituencies socialize content.
·
Outreach to SGs:
o
Councilors to gather and relay feedback on gaps during ICANN83.
·
Gap Evaluation:
o
Consider which gaps are relevant for potential policy development.
o
Discuss impact, feasibility, and scope within ICANN’s remit.
·
Potential Issue Report:
o
Discussion on whether a list of identified issues warrants requesting an Issue Report.
o
Clarification needed whether the Small Team can formally request one or if the Council must.
[Note: Support
staff investigated and the Request for Issue Report template expects a name of a Councilor. However, the template is only a recommended format, so it would not seem to preclude the request coming from the Small Team, which is
of course comprised of Councilors, if that is preferred.]
·
Draft Questions to be shared with ICANN Org were shared via List with the Small Team.
·
Support for question clarity and direction.
·
Questions to be send to
ICANN Org before
ICANN83.