Registry Operator will Sample Clauses

Registry Operator will perform monitoring from internally located systems as a means to verify that the conditions of the SLA are being met.
Sample 1
AutoNDA by SimpleDocs

Related to Registry Operator will

  • 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

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

  • 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).

  • Consider Operator as School Official The Parties agree that Operator is a “school official” under FERPA and has a legitimate educational interest in personally identifiable information from education records. For purposes of the Service Agreement and this DPA, Operator: (1) provides a service or function for which the LEA would otherwise use employees; (2) is under the direct control of the LEA with respect to the use and maintenance of education records; and

  • Economic Uniformity At the election of the General Partner with respect to any taxable period ending upon, or after, the termination of the Subordination Period, all or a portion of the remaining items of Partnership gross income or gain for such taxable period, after taking into account allocations pursuant to Section 6.1(d)(iii), shall be allocated 100% to each Partner holding Subordinated Units that are Outstanding as of the termination of such Subordination Period (“Final Subordinated Units”) in the proportion of the number of Final Subordinated Units held by such Partner to the total number of Final Subordinated Units then Outstanding, until each such Partner has been allocated an amount of gross income or gain that increases the Capital Account maintained with respect to such Final Subordinated Units to an amount equal to the product of (A) the number of Final Subordinated Units held by such Partner and (B) the Per Unit Capital Amount for a Common Unit. The purpose of this allocation is to establish uniformity between the Capital Accounts underlying Final Subordinated Units and the Capital Accounts underlying Common Units held by Persons other than the General Partner and its Affiliates immediately prior to the conversion of such Final Subordinated Units into Common Units. This allocation method for establishing such economic uniformity will be available to the General Partner only if the method for allocating the Capital Account maintained with respect to the Subordinated Units between the transferred and retained Subordinated Units pursuant to Section 5.5(c)(ii) does not otherwise provide such economic uniformity to the Final Subordinated Units.

  • 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. 1. 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. 2. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) 3. 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. a. 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. b. 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. c. 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. d. Registry Operator of a “Generic String” TLD may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others.

  • Transfer and Seniority Outside the Bargaining Unit (a) It is understood that an employee shall not be transferred by the Hospital to a position outside the bargaining unit without his consent except in the case of temporary assignments not exceeding six (6) months. Such employees on temporary assignments shall remain members of the bargaining unit. (b) An employee who is transferred to a position outside the bargaining unit shall not, subject to (c) below, accumulate seniority. In the event the employee is returned by the Hospital to a position in the bargaining unit within twenty-four (24) months of the transfer he or she shall be credited with the seniority held at the time of transfer and resume accumulation from the date of his or her return to the bargaining unit. An employee not returned to the bargaining unit within 24 months shall forfeit bargaining unit seniority. (c) In the event an employee transferred out of the bargaining unit under (b) above is returned to the bargaining unit within a period of six (6) calendar months, he shall accumulate seniority during the period of time outside the bargaining unit."

  • The FTPS Unit Servicing Agent shall transmit to each FTPS Unit holder of record any notice or other communication received from the Trustee and shall be solely responsible for soliciting and transmitting to the Trustee any notice required from FTPS Unit holders.

  • 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:

  • 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!