− | So far, ICANN has been steadfast in its focus on technical DNS abuse and avoidance of policymaking around content abuse. As recently as ICANN 71, the organization was criticized by [[____]] and [[ ___]] for not doing enough to steward contracted parties and non-contracted parties toward involvement in reducing abuse. | + | So far, ICANN has been steadfast in its focus on technical DNS abuse and avoidance of policymaking around content abuse. ICANN's determination of the org's definition for DNS Abuse is based on the work product of GAC and the base gTLD Registry Agreement. Thus, ICANN considers DNS security threats to be limited to attacks involving phishing, malware, botnet command and control, pharming, and spam as a vector.<ref>[https://www.icann.org/en/blogs/details/update-on-icanns-dns-security-threat-mitigation-program-19-7-2021-en Update on DNS Security Threats, ICANN Org]</ref> As recently as [[ICANN 71]], the ICANN board was criticized by members of the [[ALAC]], the [[BC]], and other [[Internet Goverance]] bodies for not doing enough to steward contracted parties and non-contracted parties toward involvement in reducing abuse. |
− | However, ICANN and SSAC, in particular, can point to [[SAC115]]. | + | However, ICANN and SSAC, in particular, have begun pointing to [[SAC115]] and [[DAAR]] as evidence of their work on addressing DNS abuse. |
| Currently, this newcomer is entirely focused on creating an interoperable framework. | | Currently, this newcomer is entirely focused on creating an interoperable framework. |