Common use of Registry Operator Operations Clause in Contracts

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 the registrant for any domain names in the registry TLD, such registrations must be through an ICANN accredited registrar, and will be considered transactions for purposes of calculating the Registry-Level Transaction Fee to be paid to ICANN by Registry Operator pursuant to Section 7.2. (ii) Use of ICANN-Accredited Registrars. Registry Operator shall ensure that all Approved Services are provided through one or more ICANN-Accredited Registrars.

Registry Operator Operations. (i) Registration RestrictionsPolicyRestrictions. (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. (CBC) Registry Operator shall reserve, and not register any TLD strings (i) appearing on the list of reserved TLD strings attached as Appendix 6Specification 5 6 hereto (“Specification 5”) or (ii) located at ▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇▇/TLD/tlds-alpha-by-domain.txt 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 the registrant for any domain names in the registry TLD, such registrations must be through an ICANN accredited registrar, and will be considered transactions for purposes of calculating the Registry-Level Transaction Fee to be paid to ICANN by Registry Operator pursuant to Section 7.2. . (ii) Use Functional and Performance Specifications. Functional and Performance Specifications for operation of ICANN-Accredited Registrarsthe 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 ensure 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 reasonable advance written notice, provided that all Approved 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 (i) 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 and (ii) provided through one by Registry Operator for the TLD as of the Effective Date and identified in Appendix S, Part VII; (b) other products or more ICANN-Accredited Registrarsservices 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; (d) material changes to any Registry Service within the scope of (a), (b) or (c) above. (iv) Process for Consideration of Proposed Registry Operator Services. Following written notification by Registry Operator to ICANN that Registry Operator may make a change in a Registry Operator Service within the scope of the preceding paragraph, ICANN will follow the procedure detailed at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/registries/rsep/rsep.html.