Termination by Registry Operator (a) Registry Operator may terminate this Agreement upon notice to ICANN if (i) ICANN fails to cure any fundamental and material breach of ICANN’s covenants set forth in Article 3, within thirty (30) calendar days after Registry Operator gives ICANN notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that ICANN is in fundamental and material breach of such covenants, and (iii) ICANN fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction.
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.
Registry Operator has (i) ceased to conduct its business in the ordinary course; or (ii) filed for bankruptcy, become insolvent or anything analogous to any of the foregoing under the laws of any jurisdiction anywhere in the world; or
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-‐xxxxxx-‐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).
Project Administration Designation Pursuant to Paragraph (B) of Rule 164-1-21 of the Administrative Code, the Recipient shall designate its Chief Executive Officer, Chief Fiscal Officer and Project Manager in Appendix B of this Agreement. Changes in these designations must be made in writing.
COVENANTS OF REGISTRY OPERATOR Registry Operator covenants and agrees with ICANN as follows:
Registry Lock Registry Operator may offer the Registry Lock service, which is a registry service that allows an authorized representative from the sponsoring Registrar, request the activation or deactivation of any of the following EPP statuses: serverUpdateProhibited, serverDeleteProhibited and⁄or serverTransferProhibited. SPECIFICATION 1 CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION
Domain and Designation The Top-Level Domain to which this Agreement applies is (the “TLD”). Upon the Effective Date and until the earlier of the expiration of the Term (as defined in Section 4.1) or the termination of this Agreement pursuant to Article 4, ICANN designates Registry Operator as the registry operator for the TLD, subject to the requirements and necessary approvals for delegation of the TLD and entry into the root-zone.
REGISTRY OPERATOR CODE OF CONDUCT 1. In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to:
Application for Membership No employee shall be subject to any penalties against his application for membership or reinstatement, except as may be provided for in the Constitution and By-Laws of the National Union and the Union. A copy of such Constitution and By-Laws, and any changes thereto, shall be transmitted to the Company.
