Common use of Consensus Policies Clause in Contracts

Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Registry Operator will fully comply with and implement all Consensus 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 ICANN’s Bylaws and as set forth below. 3.1 (b)(ii) "Consensus Policies" are those specifications or policies established (1) pursuant to the procedure set forth in ICANN's Bylaws and due process, and (2) covering those topics listed in Section 3.1(b)(iv) below. The Consensus Policy development process and procedure set forth in ICANN's Bylaws may be revised from time to time in accordance with ICANN’s Bylaws, and any Consensus Policy that is adopted through such a revised process and covering those topics listed in Section 3.1(b)(iv) below shall be considered a Consensus Policy for purposes of this Agreement. 3.1 (b)(iii) For all purposes under this Agreement, the policies identified at xxxx://xxx.xxxxx.xxx/en/general/consensus-policies.htm shall be treated in the same manner and have the same effect as "Consensus Policies."

Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Registry Operator will fully comply with and implement all Consensus Policies found at xxxx://xxx.xxxxx.xxx/general/consensus-policies.htmxxxx://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 ICANN’s Bylaws and as set forth below. 3.1 (b)(ii) "Consensus Policies" are those specifications or policies established (1) pursuant to the procedure set forth in ICANN's Bylaws and due process, and (2) covering those topics listed in Section 3.1(b)(iv) below. The Consensus Policy development process and procedure set forth in ICANN's Bylaws may be revised from time to time in accordance with ICANN’s Bylaws, and any Consensus Policy that is adopted through such a revised process and covering those topics listed in Section 3.1(b)(iv) below shall be considered a Consensus Policy for purposes of this Agreement. 3.1 (b)(iii) For all purposes under this Agreement, the policies identified at xxxx://xxx.xxxxx.xxx/en/general/consensus-policies.htm xxxx://xxx.xxxxx.xxx/en/general/consensus-­‐policies.htm shall be treated in the same manner and have the same effect as "Consensus Policies." 3.1 (b)(iv) Consensus Policies and the procedures by which they are developed shall be designed to produce, to the extent possible, a consensus of Internet stakeholders, including the operators of gTLDs. Consensus Policies shall relate to one or more of the following: (1) issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, Security and/or Stability of the Internet or DNS; (2) functional and performance specifications for the provision of Registry Services (as defined in Section 3.1(d)(iii) below); (3) Security and Stability of the registry database for the TLD; (4) registry policies reasonably necessary to implement Consensus Policies relating to registry operations or registrars; or (5) resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names). Such categories of issues referred to in the preceding sentence shall include, without limitation: 3.1 (b)(iv)(A) principles for allocation of registered names in the TLD (e.g., first-­‐come, first-­‐served, timely renewal, holding period after expiration); 3.1 (b)(iv)(B) prohibitions on warehousing of or speculation in domain names by registries or registrars;

Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Registry Operator will fully comply with and implement all Consensus Policies found at xxxx://xxx.xxxxx.xxx/general/consensus-policies.htmxxxx://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 ICANN’s Bylaws and as set forth below. 3.1 (b)(ii) "Consensus Policies" are those specifications or policies established (1) pursuant to the procedure set forth in ICANN's Bylaws and due process, and (2) covering those topics listed in Section 3.1(b)(iv) below. The Consensus Policy development process and procedure set forth in ICANN's Bylaws may be revised from time to time in accordance with ICANN’s Bylaws, and any Consensus Policy that is adopted through such a revised process and covering those topics listed in Section 3.1(b)(iv) below shall be considered a Consensus Policy for purposes of this Agreement. 3.1 (b)(iii) For all purposes under this Agreement, the policies identified at xxxx://xxx.xxxxx.xxx/en/general/consensus-policies.htm xxxx://xxx.xxxxx.xxx/en/general/consensus-­‐policies.htm shall be treated in the same manner and have the same effect as "Consensus Policies."

Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Registry Operator will fully comply with and implement all Consensus 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 ICANN’s Bylaws and as set forth below. 3.1 (b)(ii) "Consensus Policies" are those specifications or policies established (1) pursuant to the procedure set forth in ICANN's Bylaws and due process, and (2) covering those topics listed in Section 3.1(b)(iv) below. The Consensus Policy development process and procedure set forth in ICANN's Bylaws may be revised from time to time in accordance with ICANN’s Bylaws, and any Consensus Policy that is adopted through such a revised process and covering those topics listed in Section 3.1(b)(iv) below shall be considered a Consensus Policy for purposes of this Agreement. 3.1 (b)(iii) For all purposes under this Agreement, the policies identified at xxxx://xxx.xxxxx.xxx/en/general/consensus-policies.htm xxxx://xxx.xxxxx.xxx/general/consensus- policies.htm shall be treated in the same manner and have the same effect as "Consensus Policies." 3.1 (b)(iv) Consensus Policies and the procedures by which they are developed shall be designed to produce, to the extent possible, a consensus of Internet stakeholders, including the operators of gTLDs. Consensus Policies shall relate to one or more of the following: (1) issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, Security and/or Stability of the Internet or DNS; (2) functional and performance specifications for the provision of Registry Services (as defined in Section 3.1(d)(iii) below); (3) Security and Stability of the registry database for the TLD; (4) registry policies reasonably necessary to implement Consensus Policies relating to registry operations or registrars; or (5) resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names). Such categories of issues referred to in the preceding sentence shall include, without limitation: 3.1 (b)(iv)(A) principles for allocation of registered names in the TLD (e.g., first-come, first-served, timely renewal, holding period after expiration); 3.1 (b)(iv)(B) prohibitions on warehousing of or speculation in domain names by registries or registrars;

Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Registry Operator will fully comply with and implement all Consensus 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 ICANN’s Bylaws and as set forth below. 3.1 (b)(ii) "Consensus Policies" are those specifications or policies established (1) pursuant to the procedure set forth in ICANN's Bylaws and due process, and (2) covering those topics listed in Section 3.1(b)(iv) below. The Consensus Policy development process and procedure set forth in ICANN's Bylaws may be revised from time to time in accordance with ICANN’s Bylaws, and any Consensus Policy that is adopted through such a revised process and covering those topics listed in Section 3.1(b)(iv) below shall be considered a Consensus Policy for purposes of this Agreement. 3.1 (b)(iii) For all purposes under this Agreement, the policies identified at xxxx://xxx.xxxxx.xxx/en/general/consensus-policies.htm shall be treated in the same manner and have the same effect as "Consensus Policies." 3.1 (b)(iv) Consensus Policies and the procedures by which they are developed shall be designed to produce, to the extent possible, a consensus of Internet stakeholders, including the operators of gTLDs. Consensus Policies shall relate to one or more of the following: (1) issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, Security and/or Stability of the Internet or DNS; (2) functional and performance specifications for the provision of Registry Services (as defined in Section 3.1(d)(iii) below); (3) Security and Stability of the registry database for the TLD; (4) registry policies reasonably necessary to implement Consensus Policies relating to registry operations or registrars; or (5) resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names). Such categories of issues referred to in the preceding sentence shall include, without limitation: 3.1 (b)(iv)(A) principles for allocation of registered names in the TLD (e.g., first-come, first-served, timely renewal, holding period after expiration); 3.1 (b)(iv)(B) prohibitions on warehousing of or speculation in domain names by registries or registrars;