Registry Operator Operations Clause Samples

Registry Operator Operations. (i) Registration RestrictionsPolicy. (A) Registry Operator shall be responsible for establishing policies, in conformity with the charter, for the naming conventions within the sponsored TLD and for requirements of registration, consistent with Section 3.1(g). (A) Registry Operator shall establish registration policies 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 ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/resources/registries/rrdrp ; with respect to disputes arising pursuant to this Section 3.1(c)(i)(A). Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto. (B) Registry Operator shall be responsible for establishing procedures for the enforcement of applicable Charter restrictions on registration within the TLD, as described in more detail in the sponsored TLD charter attached as Part I to Appendix S. (CB) Registry Operator shall reserve, and not register any TLD strings (i) appearing on the list of reserved TLD strings attached as Appendix 6Specification 5 hereto (“Specification 5”) or (ii) located at ▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇▇/TLD/tlds-alpha-by-domain.txt for initial (i.e., other than renewal) registration at the second level within the TLD. Except to the extent ICANN otherwise authorizes in writing, Registry Operator shall comply with the requirements of Specification 5. Registry Operator may any time establish or modify policies concerning Registry Operator’s ability to reserve (i.e., withhold from registration or allocate to Registry Operator, but not register to third parties, delegate, use, activate in the DNS or otherwise make available) or block additional character strings within the TLD at its discretion. Except as specified in Specification 5, if Registry Operator is t...
View SourceView Similar (2)
Registry Operator Operations. (i) Registration Restrictions. (A) Registry Operator shall be responsible for establishing policies, in conformity with the charter, for the naming conventions within the sponsored TLD and for requirements of registration, consistent with Section 3.1(g). (B) Registry Operator shall be responsible for establishing procedures for the enforcement of applicable Charter restrictions on registration within the TLD, as described in more detail in the sponsored TLD charter attached as Part I to Appendix S. (C) Registry Operator shall reserve, and not register any TLD strings (i) appearing on the list of reserved TLD strings attached as Appendix 6 hereto or (ii) located at ▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇▇/TLD/tlds- alpha-by-domain.txt for initial (i.e., other than renewal) registration at the second level within the TLD. (ii) Functional and Performance Specifications. Functional and Performance Specifications for operation of the TLD shall be as set forth in Appendix 7 hereto, and shall address without limitation minimum requirements for DNS services; operation of the shared registration system; and nameserver operations. Registry Operator shall keep technical and operational records sufficient to evidence compliance with such specifications for at least one year, which records ICANN may audit from time to time upon no less than ten days’ advance written notice, provided that such audits shall not exceed one per quarter. Any such audit shall be at ICANN's cost. (iii) Registry Operator Services. Registry Operator Services are, for purposes of this Agreement, defined as the following: (a) those services that are operations of the Registry Operator critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the Registry Operator zone servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy (as defined in Section 3.1(b) above); (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above. (iv) ...
View Source
Registry Operator Operations 
View SourceView Similar (3)

Related to Registry Operator Operations

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Operator The Optionee shall be the operator for purposes of developing and executing exploration programs.

  • Safe Operations Notwithstanding any other provision of this Agreement, an NTO may take, or cause to be taken, such action with respect to the operation of its facilities as it deems necessary to maintain Safe Operations. To ensure Safe Operations, the local operating rules of the ITO(s) shall govern the connection and disconnection of generation with NTO transmission facilities. Safe Operations include the application and enforcement of rules, procedures and protocols that are intended to ensure the safety of personnel operating or performing work or tests on transmission facilities.

  • System Operations Each party, at its own expense, shall provide and maintain the equipment, software, services and testing necessary to transmit Data Communications to, and receive Data Communications from the parties’ respective Receipt Computers.

  • Contractor’s Project Manager and Key Personnel Contractor shall appoint a Project Manager to direct the Contractor’s efforts in fulfilling Contractor’s obligations under this Contract. This Project Manager shall be subject to approval by the County and shall not be changed without the written consent of the County’s Project Manager, which consent shall not be unreasonably withheld. The Contractor’s Project Manager shall be assigned to this project for the duration of the Contract and shall diligently pursue all work and services to meet the project time lines. The County’s Project Manager shall have the right to require the removal and replacement of the Contractor’s Project Manager from providing services to the County under this Contract. The County’s Project manager shall notify the Contractor in writing of such action. The Contractor shall accomplish the removal within five (5) business days after written notice by the County’s Project Manager. The County’s Project Manager shall review and approve the appointment of the replacement for the Contractor’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Contractor’s Project Manager from providing further services under the Contract.