Small Team on DNS Abuse: Difference between revisions
m added Category:DNS Abuse Responses using HotCat |
|||
Line 2: | Line 2: | ||
==Findings== | ==Findings== | ||
After considering input from across the [[ICANN Community] and ICANN [[Contractual Compliance]] on current requirements and enforcement, the small team found that:<ref>[https://75.schedule.icann.org/meetings/CyuCKhBfPZmZTLhec Small Team on DNS Abuse Session, ICANN 75]</ref> | After considering input from across the [[ICANN Community] and ICANN [[Contractual Compliance]] on current requirements and enforcement, the small team found that:<ref>[https://75.schedule.icann.org/meetings/CyuCKhBfPZmZTLhec Small Team on DNS Abuse Session, ICANN 75]</ref> | ||
* DNS abuse has a life cycle, which determines which parties should mitigate the harm | * DNS abuse has a life cycle, which determines which parties should mitigate the harm. The phases involve: | ||
*# measures to help CPs identify DNS abuse earlier or even prevent a malicious registration | |||
*# ensuring harmed parties know how AND to whom a complaint should be reported | |||
*# reports that are well-formed and actionable | |||
*# well-positioned party (CPs, web-host, website owner/operator, etc) takes action | |||
*# enforcement by ICANN compliance, if contracted party is involved | |||
* concerns and solutions fall into three buckets: | * concerns and solutions fall into three buckets: | ||
*# possibly requiring policy development, | *# possibly requiring policy development, |
Revision as of 19:20, 6 October 2022
The Small Team on DNS Abuse is an output of the GNSO Council to determine what policy efforts, if any, the GNSO Council should consider undertaking to support the efforts already underway in the different parts of the ICANN community to tackle DNS abuse.[1]
Findings[edit | edit source]
After considering input from across the [[ICANN Community] and ICANN Contractual Compliance on current requirements and enforcement, the small team found that:[2]
- DNS abuse has a life cycle, which determines which parties should mitigate the harm. The phases involve:
- measures to help CPs identify DNS abuse earlier or even prevent a malicious registration
- ensuring harmed parties know how AND to whom a complaint should be reported
- reports that are well-formed and actionable
- well-positioned party (CPs, web-host, website owner/operator, etc) takes action
- enforcement by ICANN compliance, if contracted party is involved
- concerns and solutions fall into three buckets:
- possibly requiring policy development,
- to be shared with the community for consideration outside of policy development, and
- to be considered by the Contracted Parties House.
History[edit | edit source]
At ICANN 72, the GNSO Council initiated a small team on DNS abuse. It gathered information on the efforts already underway to deal with DNS abuse but focused on the narrow topic of DNS abuse issues inadequately mitigated and whether they require policy development. The small team began meeting in February 2022 and articulated DNS abuse problems within the GNSO's purview. The small team received inputs from the ALAC, GAC, SSAC, the DNS Abuse Institute, Contractual Compliance, and from within the GNSO. At ICANN 75, the small team presented its findings and suggestions.[3]