Changes

*A team of [[Registrar]] and [[Registry]] representatives are negotiating changes to the [[RAA]] and [[Registry Agreement]] (RA) with [[:Category:ICANN Staff|ICANN Staff]]. The revised contractual language will be published for comment by June 2023 (ICANN 77)<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref>

*A team of [[Registrar]] and [[Registry]] representatives are negotiating changes to the [[RAA]] and [[Registry Agreement]] (RA) with [[:Category:ICANN Staff|ICANN Staff]]. The revised contractual language will be published for comment by June 2023 (ICANN 77)<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref>

*the ALAC, BC, and IPC sent a joint letter seeking consultation on the DNS abuse negotiations with the Contracted Parties (precedent from 2009 and 2013). ICANN Board said Contracted Parties entered DNS abuse negotiations with a specific scope with ICANN Contractual Compliance for more enforcement tools. ICANN Board will consider conducting a listening session with the ICANN community.

*the ALAC, BC, and IPC sent a joint letter seeking consultation on the DNS abuse negotiations with the Contracted Parties (precedent from 2009 and 2013). ICANN Board said Contracted Parties entered DNS abuse negotiations with a specific scope with ICANN Contractual Compliance for more enforcement tools. ICANN Board will consider conducting a listening session with the ICANN community.

*The GAC expressed concerns over the negotiations in relation to Recommendations 14 (ICANN should include provisions in the agreements to provide incentives, including financial incentives for registries, especially open registries, to adopt proactive anti-abuse measures<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg98</ref>) and 15 (ICANN should establish thresholds of abuse at which [[Contractual Compliance]] inquiries are automatically triggered, with a higher threshold at which registrars and registries are presumed to be in default of their agreements. If the community determines that ICANN org itself is ill-suited or unable to enforce such provisions, a DNS Abuse Dispute Resolution Policy (DADRP) should be considered as an additional means to enforce policies and deter DNS Security Abuse<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg99</ref>) from the [[First Competition, Consumer Trust, and Consumer Choice Review|Competition, Consumer Trust, and Consumer Choice Review]].

*The GAC expressed concerns over the negotiations in relation to Recommendations 14 (ICANN should include provisions in the agreements to provide incentives, including financial incentives for registries, especially open registries, to adopt proactive anti-abuse measures<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg98]</ref>) and 15 (ICANN should establish thresholds of abuse at which [[Contractual Compliance]] inquiries are automatically triggered, with a higher threshold at which registrars and registries are presumed to be in default of their agreements. If the community determines that ICANN org itself is ill-suited or unable to enforce such provisions, a DNS Abuse Dispute Resolution Policy (DADRP) should be considered as an additional means to enforce policies and deter DNS Security Abuse<ref>[https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf CCT Review 1 Final Report, pg99]</ref>) from the [[First Competition, Consumer Trust, and Consumer Choice Review|Competition, Consumer Trust, and Consumer Choice Review]].

 

===DNSSEC===

===DNSSEC===

[[SSAC]] asked ICANN Board and Org to promote [[DNSSEC]] similarly to how it has approached UA. Specifically, [[Russ Mundy]] asked for an analysis of the gaps and requirements to accomplish widespread use of DNSSEC.<ref>[https://meetings.icann.org/sites/default/files/icann76-policy-outcome-report-10apr23-en.pdf ICANN76 Policy Outcomes Report, pg 19]</ref>  

[[SSAC]] asked ICANN Board and Org to promote [[DNSSEC]] similarly to how it has approached UA. Specifically, [[Russ Mundy]] asked for an analysis of the gaps and requirements to accomplish widespread use of DNSSEC.<ref>[https://meetings.icann.org/sites/default/files/icann76-policy-outcome-report-10apr23-en.pdf ICANN76 Policy Outcomes Report, pg 19]</ref>