Release of Performance Security (i) The Authority shall return the Performance Security to the Contractor within 60 (sixty) days of the expiry of the Maintenance Period or the Defects Liability Period, whichever is later, under this Agreement. Notwithstanding the aforesaid, the Parties agree that the Authority shall not be obliged to release the Performance Security until all Defects identified during the Defects Liability Period have been rectified.
Appropriation of Performance Security Upon occurrence of a Concessionaire Default, the Authority shall, without prejudice to its other rights and remedies hereunder or in law, be entitled to invoke, encash and appropriate the relevant amounts from the Performance Security as Damages for such Concessionaire Default. Upon such invocation, encashment and appropriation from the Performance Security, the Concessionaire shall, within [30 (thirty)] days thereof, replenish, in case of partial appropriation, to its original level the Performance Security, and in case of appropriation of the entire Performance Security provide a fresh Performance Security, as the case may be, and the Concessionaire shall, within the time so granted, replenish or furnish fresh Performance Security as aforesaid failing which the Authority shall be entitled to terminate this Agreement in accordance with Article 37. Upon replenishment or furnishing of a fresh Performance Security, as the case may be, as aforesaid, the Concessionaire shall be entitled to an additional Cure Period of [90 (ninety)] days for remedying the Concessionaire Default, and in the event of the Concessionaire not curing its default within such Cure Period, the Authority shall be entitled to invoke, encash and appropriate such Performance Security as Damages, and to terminate this Agreement in accordance with Article 37.
Performance Security If our Tender is accepted, we commit to obtain a performance security in accordance with the Tendering document;
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 xxxx://xxx.xxxxx.xxx/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.
