COVENANTS OF REGISTRY OPERATOR Sample Clauses

COVENANTS OF REGISTRY OPERATOR. Registry Operator covenants and agrees with ICANN as follows:
The Best Tool for Contract Research

Polish your contracts and save time by searching through millions of contracts from Am Law 100 firms and Fortune 100 companies

30+ Reviews on G2 Crowd
"Excellent source of contracts and clauses"
Michael-G.png
Michael G
Special Counsel
COVENANTS OF REGISTRY OPERATOR. Registry Operator covenants and agrees with ICANN as follows:3.1 (a) Preserve Security and Stability. 3.1 (a)(i) ICANN Temporary Specifications or Policies. Registry Operator shall comply with and implement all specifications or policies established by the ICANN Board of Directors on a temporary basis, if adopted by the ICANN Board of Directors by a vote of at least two-thirds of its members, so long as the ICANN Board of Directors reasonably determines that immediate temporary establishment of a specification or policy on the subject is necessary to maintain the Stability or Security (as defined in Section 3.1(d)(iv)(G)) of Registry Services or the DNS ("Temporary Specification or Policies"). Such proposed specification or policy shall be as narrowly tailored as feasible to achieve those objectives. In establishing any specification or policy under this provision, the ICANN Board of Directors shall state the period of time for which the specification or policy is temporarily adopted and shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws. ICANN shall also issue an advisory statement containing a detailed explanation of its reasons for adopting the temporary specification or policy and why the Board believes the specification or policy should receive the consensus support of Internet stakeholders. If the period of time for which the specification or policy is adopted exceeds 90 days, the ICANN Board shall reaffirm its temporary adoption every 90 days for a total period not to exceed one year, in order to maintain such policy in effect until such time as it shall become a Consensus Policy as described in Section 3.1(b) below. If during such one year period, the temporary policy or specification does not become a Consensus Policy meeting the standard set forth in Section 3.1(b) below, Registry Operator shall no longer be required to comply with or implement such temporary policy or specification. 3.1 (b) Consensus Policies. 3.1 (b)(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 http://www.icann.org/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 http://www.icann.org/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 registrationof 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; 3.1 (b)(iv)(C) reservation of registered names in the TLD that may not be registered initially or that may not be renewed due to reasons reasonably related to (a) avoidance of confusion among or misleading of users, (b) intellectual property, or (c) the technical management of the DNS or the Internet (e.g., establishment of reservations of names from registration); 3.1 (b)(iv)(D) maintenance of and access to accurate and up-to-date information concerning domain name registrations; 3.1 (b)(iv)(E) procedures to avoid disruptions of domain name registration due to suspension or termination of operations by a registry operator or a registrar, including procedures for allocation of responsibility for serving registered domain names in a TLD affected by such a suspension or termination; and 3.1 (b)(iv)(F) resolution of disputes regarding whether particular parties may register or maintain registration of particular domain names. 3.1 (b)(v) In addition to the other limitations on Consensus Policies, they shall not: 3.1 (b)(v)(A) prescribe or limit the price of Registry Services; 3.1 (b)(v)(B) modify the standards for the consideration of proposed Registry Services, including the definitions of Security and Stability (set forth below) and the standards applied by ICANN; 3.1 (b)(v)(C) modify the terms or conditions for the renewal or termination of this Agreement; 3.1 (b)(v)(D) modify ICANN’s obligations to Registry Operator under Section 3.2 (a), (b), and (c); 3.1 (b)(v)(E) modify the limitations on Consensus Policies or Temporary Specifications or Policies; 3.1 (b)(v)(F) modify the definition of Registry Services; 3.1 (b)(v)(G) modify the terms of Sections 7.2 below; or 3.1 (b)(v)(H) alter services that have been implemented pursuant to Section 3.1(d) of this Agreement (unless justified by compelling and just cause based on Security and Stability. 3.1 (b)(vi) Registry Operator shall be afforded a reasonable period of time following notice of the establishment of a Consensus Policy or Temporary Specifications or Policies in which to comply with such policy or specification, taking into account any urgency involved. In the event of a conflictbetween Registry Services (as defined in Section 3.1(d)(iii) below), on the one hand, and Consensus Policies developed in accordance with this Section 3.1(b) or any Temporary Specifications or Policies established pursuant to Section 3.1(a)(i) above, on the other hand, the Consensus Polices or Temporary Specifications or Policies shall control, notwithstanding any other provisions contained within this Agreement. 3.1 (c) Handling of Registry Data.
COVENANTS OF REGISTRY OPERATOR. Registry Operator covenants and agreeswith ICANN as follows: