Obligations of Registry Operator to TLD Community Sample Clauses

Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.

AutoNDA by SimpleDocs

Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto. COVENANTS OF ICANN ICANN covenants and agrees with Registry Operator as follows: Open and Transparent. Consistent with ICANN’s expressed mission and core values, ICANN shall operate in an open and transparent manner. Equitable Treatment. ICANN shall not apply standards, policies, procedures or practices arbitrarily, unjustifiably, or inequitably and shall not single out Registry Operator for disparate treatment unless justified by substantial and reasonable cause. TLD Nameservers. ICANN will use commercially reasonable efforts to ensure that any changes to the TLD nameserver designations submitted to ICANN by Registry Operator (in a format and with required technical elements specified by ICANN at xxxx://xxx.xxxx.xxx/domains/root/ will be implemented by ICANN within seven (7) calendar days or as promptly as feasible following technical verifications.

Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD (and as subsequently amended) for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the Sponsored TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD as set forth in Specification 12 attached hereto. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator shall implement and comply with the registration policies set forth on Specification 12 attached hereto.

Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto. [END NEW TEXT] The parties further hereby agree to amend the Agreement by adding the following new text as a new Specification 12: [START NEW TEXT] SPECIFICATION 12

Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD,

Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submittedSpecification 12 hereof with respect to the TLD (and as subsequently amended) for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the Sponsoredsponsored, community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD as set forth in Specification 12 attached hereto. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the sponsored TLD community registration policies set forth on Specification 12 attached hereto.

Related to Obligations of Registry Operator to TLD Community

COVENANTS OF REGISTRY OPERATOR Registry Operator covenants and agrees with ICANN as follows:
NATIONAL JOINT COUNCIL AGREEMENTS 20.1 Subject to the National Joint Council By-Laws, agreements concluded by the National Joint Council of the Public Service on items which may be included in a collective agreement, and which the parties to this agreement have endorsed after December 6, 1978, will form part of this collective agreement, subject to the Public Service Labour Relations Act (PSLRA) and any legislation by Parliament that has been or may be, as the case may be, established pursuant to any Act prescribed in Schedule III of the PSLRA.
Certification for Federal-Aid Contracts Lobbying Activities A. The CONSULTANT certifies, by signing and submitting this Contract, to the best of its knowledge and belief after diligent inquiry, and other than as disclosed in writing to the LPA prior to or contemporaneously with the execution and delivery of this Contract by the CONSULTANT, the CONSULTANT has complied with Section 1352, Title 31, U.S. Code, and specifically, that:
Commercial Driver’s License If the job responsibilities of the classification of work to which an employee is regularly appointed or is assigned on an out-of-class basis involve the driving of vehicles requiring the driver to have a state Commercial Driver’s License (CDL), fees charged by the state for acquiring the license and all required endorsements shall be reimbursed by the City upon the employee having successfully attained the CDL or CDL renewal. The physical exam required to obtain or renew the license may be done on City time. The City will pay as a maximum amount, the rates charged by City identified clinics for the physical exam. Employees shall be notified of clinics offering the exam at this reimbursement rate. If an employee is covered by a City medical plan that includes coverage for physical exams, the employee shall have the exam form completed through the plan's providers (Group Health or Aetna) or shall seek reimbursement through the medical plan. Employees required to have a Hazardous Material endorsement (HME) are required per Federal regulations to submit to a background records check and fingerprinting. Employees may make application for such HME on City time and shall be reimbursed for the fees associated with the background records check and fingerprinting if such endorsement is required by the job. The City shall make a reasonable effort to make City trucks or equipment available for skill tests. In addition, for those employees qualifying as described above, fees charged for department-approved classes offered for employees to assist them in passing this exam shall be reimbursed on a one-time-only basis. Employees in other job titles or positions not involving the driving of vehicles requiring the CDL, who wish to take exam preparation or driver training courses, may request approval of the courses and reimbursement of fees in the normal manner in which educational expenses are applied for and approved by departments; provided, however, license fees for those individuals will not be reimbursed, nor shall the City be obligated to make City trucks or equipment available for skill tests for these individuals. Nothing contained herein shall guarantee that written exams, skill tests, or training classes established for the purposes described herein shall be conducted during regular work hours or through adjusted work schedules, nor shall such written exams, skill tests, or training classes be paid for on an overtime basis.
COUNCIL’S OBLIGATIONS Except as otherwise expressly provided, the obligations of the Council under the Contract are obligations of the Council in its capacity as a contracting counterparty and nothing in the Contract shall operate as an obligation on, or in any other way xxxxxx or constrain the Council in any other capacity, nor shall the exercise by the Council of its duties and powers in any other capacity lead to any liability under the Contract (howsoever arising) on the part of the Council to the Contractor.
STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.