Co-operation by Registrar Sample Clauses

Co-operation by Registrar. The Registrar must ensure that its Personnel reasonably co-operates during, or for the purpose of this clause 16, including by: (a) providing appropriate access and secure office facilities in the relevant premises; (b) providing copies of any documents, records or data in accordance with clause 16.4 (which must be given to auDA within 5 Business Days of being requested to do so); (c) making appropriate Personnel promptly available to answer questions; and (d) if necessary, installing and running audit software on the Registrar's and its Personnel’s information technology systems.
AutoNDA by SimpleDocs

Related to Co-operation by Registrar

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

  • Registrar The term “

  • Rules by Trustee, Paying Agent, Registrar The Trustee, Paying Agent or Registrar may make reasonable rules for its functions.

  • Rules by Trustee, Paying Agent and Registrar The Trustee may make reasonable rules for action by or a meeting of Holders. The Registrar and the Paying Agent may make reasonable rules for their functions.

  • Paying Agent and Registrar Initially, U.S. Bank National Association, the Trustee under the Indenture, will act as Paying Agent and Registrar. The Company may change any Paying Agent or Registrar without notice to any Holder. The Company or any of its Subsidiaries may act in any such capacity.

  • Paying Agent and Security Registrar The Trustee will act as Paying Agent, Security Registrar and Conversion Agent. The Company may change any Paying Agent, Security Registrar, co-registrar or Conversion Agent without prior notice. The Company or any of its Affiliates may act in any such capacity.

  • Registrar, Paying Agent and Authenticating Agent; Paying Agent to Hold Money in Trust (a) The Company may appoint one or more Registrars and one or more Paying Agents, and the Trustee may appoint an Authenticating Agent, in which case each reference in this Indenture to the Trustee in respect of the obligations of the Trustee to be performed by that Agent will be deemed to be references to the Agent. The Company may act as Registrar or (except for purposes of Article 8)

  • initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.

  • Cooperation by Holders The Partnership shall have no obligation to include Registrable Securities of a Holder in a Registration Statement or in an Underwritten Offering pursuant to Section 2.03(a) if such Holder has failed to timely furnish such information that the Partnership determines, after consultation with its counsel, is reasonably required in order for any registration statement or prospectus supplement, as applicable, to comply with the Securities Act.

  • Company to Furnish Trustee Names and Addresses of Securityholders The Company will furnish or cause to be furnished to the Trustee (a) within 15 days after each regular record date (as defined in Section 2.03) a list, in such form as the Trustee may reasonably require, of the names and addresses of the holders of each series of Securities as of such regular record date, provided that the Company shall not be obligated to furnish or cause to furnish such list at any time that the list shall not differ in any respect from the most recent list furnished to the Trustee by the Company and (b) at such other times as the Trustee may request in writing within 30 days after the receipt by the Company of any such request, a list of similar form and content as of a date not more than 15 days prior to the time such list is furnished; provided, however, that, in either case, no such list need be furnished for any series for which the Trustee shall be the Security Registrar.

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