Registry Operator has Sample Clauses

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
Sample 1Sample 2Sample 3See All (2k)
AutoNDA by SimpleDocs
Registry Operator has. (i) ceased to conduct its business in the ordinary course; or
Sample 1Sample 2Sample 3See All (8)
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 9.1.7 A written notice by Sponsor or ICANN that release of the Deposits is mandated by non-payment of any fees due to Escrow Agent, pursuant to Section 15 of this Agreement; or 9.1.8 A written notice by ICANN or Sponsor that a court, arbitral, legislative, or government agency of competent jurisdiction has issued an order, rule, statute, regulation, or other requirement (a copy of which ICANN or Sponsor has provided to Registry Operator) that mandates the release of the Deposits to ICANN and/or Sponsor; and 9.2 Copies of notices with proof of delivery submitted to Escrow Agent that ICANN, Registry Operator, or Sponsor (whichever gave the notice under Section 9.1) has previously notified the other party(ies) in writing; and 9.3 Written instructions from ICANN, Sponsor, or a replacement escrow agent (see Section 9.1.3) that the Deposits be released and delivered to whichever of them provided such written instructions; and 9.4 A written undertaking by the party(ies) receiving the Deposits (ICANN, Sponsor, or a replacement escrow agent) that the Deposits will be used only as permitted under the terms of the Registry Agreement or the TLD Sponsorship Agreement, as applicable. Upon release of any Deposits to ICANN, Sponsor, or a replacement escrow agent, Escrow Agent shall at the same time deliver to Registry Operator a photostatic copy of the notice it received from Sponsor and/or ICANN under Sections 9.1.1 to 9.1.8, as applicable.
Sample 1

Related to Registry Operator has

  • COVENANTS OF REGISTRY OPERATOR Registry Operator covenants and agrees with ICANN as follows:

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry 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 DNS 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 Specification 1; (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.

  • REGISTRY OPERATOR CODE OF CONDUCT 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:

  • 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. (b) Registry Operator may terminate this Agreement for any reason upon one hundred eighty (180) calendar day advance notice to ICANN.

  • ICANN shall also issue an advisory statement containing a detailed explanation of its reasons for adopting the Temporary Policy and why the Board believes such Temporary Policy should receive the consensus support of Internet stakeholders.

  • TRANSFER AND SUB-CONTRACTING 31.1 This Framework Agreement is personal to the Supplier and the Supplier shall not assign, novate or otherwise dispose of or create any trust in relation to any or all rights and obligations under this Framework Agreement or any part thereof without the Approval. 31.2 Notwithstanding the provisions of Clause 31.1 above, the Supplier shall be entitled to Sub-Contract its obligations to supply the Services to those Sub-Contractors listed in Framework Agreement Schedule 2 (Sub-Contractors). The Supplier shall ensure that terms are included in any Sub-Contract permitted under this Framework Agreement which: 31.2.1 require the Supplier to pay any undisputed sum due to the relevant Sub-Contractor within a specified period that does not exceed thirty (30) calendar days from the date the Supplier receives the Sub-Contractor's invoice; and 31.2.2 prohibit the Sub-Contractor from further sub-contracting any element of the service provided to the Supplier without Approval. 31.3 The Supplier shall not substitute or remove a Sub-Contractor or appoint an additional sub-contractor without Approval, such Approval not be unreasonably withheld or delayed. Such consent shall not constitute approval or endorsement of such substitute or additional sub-contractor and the Supplier shall remain responsible for the provision of the Ordered Services at all times. 31.4 The Authority may require the Supplier to terminate a Sub-Contract where it considers that: 31.4.1 the Sub-Contractor may prejudice the provision of the Services or may be acting contrary to the interests of the Authority; 31.4.2 the Sub-Contractor is considered to be unreliable and/or has not provided reasonable services to its other customers; and/or 31.4.3 the Sub-Contractor employs unfit persons; 31.5 In the event that the Authority exercises its right pursuant to Clause 31.4 above, the Supplier shall remain responsible for maintaining the provision of the Services. 31.6 Despite any permitted Sub-Contract pursuant to this Clause 31, the Supplier at all times shall remain responsible for all acts and omissions of its Sub-Contractors and the acts and omissions of those employed or engaged by the Sub-Contractors as if they were its own. An obligation on the Supplier to do, or refrain from doing, any act or thing shall include an obligation upon the Supplier to procure that its employees, staff, agents and the Sub-Contractors', employees, staff and agents also do, or refrain from doing, such act or thing. 31.7 The Authority shall be entitled to: 31.7.1 assign, novate or otherwise dispose of its rights and obligations under this Framework Agreement or any part thereof to any Other Contracting Body; or 31.7.2 novate, transfer or otherwise dispose of its rights and obligations under this Framework Agreement to any other body (including any private sector body) which substantially performs any of the functions that previously had been performed by the Authority. 31.8 The Supplier shall enter into such agreement and/or deed as the Authority shall reasonably require so as to give effect to any assignment, novation, transfer or disposal made pursuant to Clause 31.7 above.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!