![](https://secure.gravatar.com/avatar/4ff17692a1337d612e64e8012dbb23fd.jpg?s=120&d=mm&r=g)
Embrace of the SAC115 definition for DNS Abuse is telling...and interestingly, subclauses that imposes what appears to me a greater duty of care on Registries with wider latitude to act: [RAA 3.18.2]........"When Registrar has actionable evidence that a Registered Name sponsored by Registrar is being used for DNS Abuse, Registrar *must promptly take the **appropriate mitigation action(s) *that are reasonably necessary to stop, or otherwise disrupt, the Registered Name from being used for DNS Abuse. Action(s) may vary depending on the circumstances, taking into account the cause and severity of the harm from the DNS Abuse and the possibility of associated collateral damage." [RA Spec 6.4.2(ii)]......" Such action(s) *shall, at a minimum*, include........(ii) the taking of *direct action*, by the Registry Operator, where the Registry Operator deems appropriate. Action(s) may vary depending on the circumstances of each case, taking into account the severity of the harm from the DNS Abuse and the possibility of associated collateral damage." ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* ============================= On Mon, 25 Dec 2023 at 06:58, Olivier MJ Crépin-Leblond via CPWG < cpwg@icann.org> wrote:
Happy Holidays everyone,
These have finally been agreed: https://www.icann.org/resources/pages/global-amendment-2024-en/
Interesting process.
Olivier _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.