Consensus Policy definition

Consensus Policy has the meaning set forth in the Consensus Policies and Temporary Policies Specification attached hereto.

Split View

AI-Powered Contracts

Draft, Review & Redline at the Speed of AI

Get StartedSchedule a Demo

Consensus Policy is one adopted by ICANN as follows:

Consensus Policy has the meaning set forth in the Consensus Policies and Temporary Policies Specification (or any amended or replacement Policy), the current version of which is currently available at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/resources/pages/approved-with-specs-2013-09-17-en#consensus- temporary.

Examples of Consensus Policy in a sentence

• Registry Operator shall be afforded a reasonable period of time following notice of the establishment of a Consensus Policy or Temporary Policy in which to comply with such policy or specification, taking into account any urgency involved.

• In establishing any Temporary Policy, the Board shall state the period of time for which the Temporary Policy is adopted and shall immediately implement the Consensus Policy development process set forth in ICANN’s Bylaws.

• If the one (1) year period expires or, if during such one (1) year period, the Temporary Policy does not become a Consensus Policy and is not reaffirmed by the Board, Registry Operator shall no longer be required to comply with or implement such Temporary Policy.

• Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014.

• If the period of time for which the Temporary Policy is adopted exceeds ninety (90) calendar days, the Board shall reaffirm its temporary adoption every ninety (90) calendar days for a total period not to exceed one (1) year, in order to maintain such Temporary Policy in effect until such time as it becomes a Consensus Policy.

• In the event Registry Operator determines that there is Potential Conflict between a proposed Applicable Law and any ICANN Requirement, Registry Operator shall provide detailed Notice of such Potential Conflict to ICANN as early as possible and, in the case of a Potential Conflict with a proposed Consensus Policy, no later than the end of any public comment period on such proposed Consensus Policy.

• 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.

• Changes to the schedule, content, format, and procedure may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall unreasonably withhold) or through the establishment of a Consensus Policy as outlined in Section 3.1(b) above.

• 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.

More Definitions of Consensus Policy

Consensus Policy refers to policies specified in Specification 1 of the Registry Agreement. Transfer policy: refers to the Inter-Registrar Transfer Policy specified in ICANN's Consensus Policy. For details, see ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/resources/registrars/transfers/policy. Personal Data: refers to any data about an identified or identifiable natural person. Registered Domain Name: refers to a domain name under the .网址 TLD, whether it consists of two or more (e.g., ▇▇▇▇▇▇.网址 or ▇▇▇▇▇▇.▇▇▇▇▇▇▇.网址) levels. In terms of the registered domain name, KNET and its designated agency shall be responsible for maintaining the data in the registration database, arranging for such maintenance, or deriving revenue therefrom. The name in the registration database may become a registered domain name even though it does not appear in a TLD zone file (e.g., a registered but inactive name). Registered Name Holders or Registrants: refers to natural persons or organizations that hold registered names. They own or control the corresponding domain name by signing a domain name registration agreement with KNET's authorized registrar or its subordinate agency. Registered name holders are usually called registrants. Registrar: refers to an entity that contracts with a registry, and is responsible for collecting information and materials about the registered name holders and submitting registration information for entry in the registration system. Registry Agreement: refers to the Registry Agreement and supplementary contract signed by KNET and ICANN for the TLD operation of .网址 and the subsequent revisions or renewal thereof. Registration Database: refers to a database comprised of data relating to the DNS domain names within one or more .网址 TLD, mainly used to generate DNS resource records that are published by authority or in response to all or part of domain-name availability lookup requests or WHOIS queries. Registry TLD: refers to the .网址 TLD.

Consensus Policy refers to policies specified in Specification 1 of the Registry Agreement. Transfer policy: refers to the Inter-Registrar Transfer Policy specified in ICANN's Consensus Policy. For details, see ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/resources/registrars/transfers/policy. Personal Data: refers to any data about an identified or identifiable natural person.