Examples of Consensus Policies in a sentence
In the event of a conflict between Registry Services and Consensus Policies or any Temporary Policy, the Consensus Polices or Temporary Policy shall control, but only with respect to subject matter in conflict.
Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-‐policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).
The question raised is whether the use of the capitalized “S” in the proposed 2023 .NET RA might restrict Verisign’s obligation to comply with Consensus Policies under Section 3.1(b)(iv)(1) to those policies that fall within the defined terms of Security and Stability, while the lowercase “s” used in the Base RA could, it was argued, theoretically allow for a broader mandate for ICANN to enforce Consensus Policies related to broader conceptions for security and stability.
Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).
The concern focuses on the use of capitalized “S” in Section 3.1(b)(iv)(1) of the proposed 2023 .NET RA versus a lowercase “s” used in Specification 1, Section 1.2.1 of the Base RA when referring to “security” and “stability”.8 These provisions set forth the allowed topics for ICANN Consensus Policies.
Perceived difference between the proposed 2023 .NET RA and the Base RA in relation to obligations to comply with Consensus Policies The several comments expressed concern on the use of the defined terms “Security” and “Stability” that have been in the .NET RA since 2005.
Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder).
The provision in question has been in place since the 2005 .NET RA and used in registry agreements, including .COM and .NAME, as well as .BIZ, .INFO, and .ORG before the latter three TLDs transitioned to the Base RA in 2019, without any policy development work or Consensus Policies being limited as hypothesized in the comments.
In both agreements, the provisions noted above focus on compliance with Consensus Policies, specifically for issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, security and/or stability of the Internet or DNS.
CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION Consensus Policies.