We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Consensus Policies Sample Clauses

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 xxxxx://xxx.xxxxx.xxx/consensus-policies, 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.
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.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/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 will fully comply with and implement all Consensus Policies, as the same may be applicable to Sponsored TLDs, 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.
Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Sponsor will comply with and shall cause Registry Operator to implement all applicable 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.
Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof,a) Compliance with Consensus Policies and Temporary Policies. Registry Operator will fullyshall comply with and implement all Consensus Policies, as the same may be applicable to Sponsored TLDs, 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 ICANN’s Bylaws and as set forth below.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”).
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.
Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Sponsor xxxxx) Compliance with Consensus Policies and Temporary Policies. Registry Operator shall comply with and shall cause Registry Operator to implement all applicable 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 ICANN’s Bylaws and as set forth below.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”).
Consensus Policies. (i) At all times during the term of this Agreement and subject to the terms hereof, Sponsor will fully comply with and implement all Consensus Policies, to the extent such policies are applicable to sponsored TLDs, 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.

Related to Consensus Policies

  • Compliance with Consensus Policies and Temporary Policies 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”).

  • SPAM POLICY You are strictly prohibited from using the Website or any of the Company's Services for illegal spam activities, including gathering email addresses and personal information from others or sending any mass commercial emails.

  • Investment Policies The Borrower shall at all times be in compliance in all material respects with its Investment Policies (after giving effect to any Permitted Policy Amendments).

  • Employment Policies The employment relationship between the parties shall also be governed by the general employment policies and practices of the Company, including those relating to protection of confidential information and assignment of inventions, except that when the terms of this Agreement differ from or are in conflict with the Company’s general employment policies or practices, this Agreement shall control.

  • Umbrella Policies Contractor may satisfy basic coverage limits through any combination of basic coverage and umbrella insurance.

  • Policies and Temporary Policies 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”). Data Escrow. Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).

  • Management; Community Policies Owner may retain employees and management agents from time to time to manage the Property, and Owner’s agent may retain other employees or contractors. Resident, on behalf of himself or herself and his or her Guests, agrees to comply fully with all directions from Owner and its employees and agents, and the rules and regulations (including all amendments and additions thereto, except those that substantially modify the Resident’s bargain and to which Resident timely objects) as contained in this Agreement and the Community Policies of the Property. The Community Policies are available at xxxxx://xxxxxxxxxxxxxx.xxx/policies.pdf or on request from the management office and are considered part of this Agreement.

  • Violence Policies and Procedures The Employer agrees to have in place explicit policies and procedures to deal with violence. The policy will address the prevention of violence, the management of violent situations, provision of legal counsel and support to employees who have faced violence. The policies and procedures shall be part of the employee's health and safety policy and written copies shall be provided to each employee. Prior to implementing any changes to these policies, the employer agrees to consult with the Association.

  • Claims Made Policies If any of the required policies provide coverage on a claims-made basis: 11.5.1 The Retroactive Date must be shown and must be before the date of the contract or the beginning of contract work. 11.5.2 Insurance must be maintained and evidence of insurance must be provided for at least five (5) years after completion of the contract of work. 11.5.3 If coverage is canceled or non-renewed, and not replaced with another claims-made policy form with a Retroactive Date prior to the contract effective date, the Contractor must purchase “extended reporting” coverage for a minimum of five (5) years after completion of contract work.

  • Policies and Procedures i) The policies and procedures of the designated employer apply to the employee while working at both sites. ii) Only the designated employer shall have exclusive authority over the employee in regard to discipline, reporting to the College of Nurses of Ontario and/or investigations of family/resident complaints. iii) The designated employer will ensure that the employee is covered by WSIB at all times, regardless of worksite, while in the employ of either home. iv) The designated employer will ensure that the employee is covered by liability insurance at all times, regardless of worksite, while in the employ of either home. v) The designated employer shall have exclusive authority over the employee’s personnel files and health records. These files will be maintained on the site of the designated employer.