MUTUAL COVENANTS RE PERFORMANCE OF SERVICES Sample Clauses

MUTUAL COVENANTS RE PERFORMANCE OF SERVICES. 8.1 Each Party agrees as follows:

Related to MUTUAL COVENANTS RE PERFORMANCE OF SERVICES

  • Mutual Covenants Each of the Parties covenants and agrees that, except as contemplated in this Agreement, during the period from the date of this Agreement until the earlier of the Effective Time and the time that this Agreement is terminated in accordance with its terms: 5.6.1 it shall, and shall cause its subsidiaries to, use commercially reasonable efforts to satisfy (or cause the satisfaction of) the conditions precedent to its obligations hereunder as set forth in Article 6 to the extent the same is within its control and to take, or cause to be taken, all other action and to do, or cause to be done, all other things necessary, proper or advisable under all applicable Laws to consummate the Arrangement, including using its commercially reasonable efforts to (i) obtain all Regulatory Approvals required to be obtained by it, (ii) effect all necessary registrations, filings and submissions of information requested by Governmental Entities required to be effected by it in connection with the Arrangement, (iii) oppose, lift or rescind any injunction or restraining order against it or other order or action against it seeking to stop, or otherwise adversely affecting its ability to make and complete, the Arrangement, and (iv) cooperate with the other Party in connection with the performance by it and its subsidiaries of their obligations hereunder. Subject to the terms and conditions herein provided, none of the Parties shall knowingly take or cause to be taken any action which would reasonably be expected to prevent or materially delay the consummation of the transactions contemplated hereby; and 5.6.2 it shall not take any action, refrain from taking any commercially reasonable action, or permit any action to be taken or not taken, which is inconsistent with this Agreement or which would reasonably be expected to significantly impede the consummation of the Arrangement except as permitted by this Agreement.

  • Excuse for Nonperformance or Delayed Performance Except with respect to defaults of subcontractors, Contractor/Vendor shall not be in default by reason of any failure in performance of this contract in accordance with its terms (including any failure by Contractor/Vendor to make progress in the prosecution of the work hereunder which endangers such performance) if Contractor/Vendor has notified the Commission or designee within 15 days after the cause of the delay and the failure arises out of causes such as: acts of God; acts of the public enemy; acts of the State and any other governmental entity in its sovereign or contractual capacity; fires; floods; epidemics; quarantine restrictions; strikes or other labor disputes; freight embargoes; or unusually severe weather. If the failure to perform is caused by the failure of a subcontractor to perform or to make progress, and if such failure arises out of causes similar to those set forth above, Contractor/Vendor shall not be deemed to be in default, unless the services to be furnished by the subcontractor were reasonably obtainable from other sources in sufficient time to permit Contractor to meet the contract requirements. Upon request of Contractor, the Commission or designee shall ascertain the facts and extent of such failure, and, if such officer determines that any failure to perform was occasioned by any one or more of the excusable causes, and that, but for the excusable cause, Contractor’s progress and performance would have met the terms of the contract, the delivery schedule shall be revised accordingly, subject to the rights of the State under the clause entitled (in fixed-price contracts, “Termination for Convenience,” in cost-reimbursement contracts, “Termination”). (As used in this Paragraph of this clause, the term “subcontractor” means subcontractor at any tier).

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Performance of Services The Contractor is responsible for fully meeting all obligations set forth in the Contract and for providing Product in accordance with the Contract or any Authorized User Agreement.

  • Performance of Covenants The Company shall have performed or complied with in all material respects all agreements and covenants required to be performed or complied with by it under this Agreement at or prior to the Effective Time.