Use of the Arin Registry Database Sample Clauses

Use of the Arin Registry Database 
AutoNDA by SimpleDocs

Related to Use of the Arin Registry Database

  • Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-­‐to-­‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Use of Technology Participants are subject to all existing laws (federal and state) and University regulations and policies on use of technology, including not only those laws and regulations that are specific to computers and networks, but also those that may apply generally to personal conduct such as:  UC Electronic Communications Policy: xxxx://xxxxxx.xxxx.xxx/doc/7000470/ElectronicCommunications  UCLA E-mail Policy and Guidelines: xxxx://xxx.xxxxxxxxxxxxx.xxxx.xxx/app/Default.aspx?&id=455  IT Services Acceptable Use Policy: xxxx://xxx.xxx.xxxx.xxx/policies/aupdetail.html  The UC Policy on Copyright Ownership: xxxx://xxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxx.xxx/resources/copyright-ownership.html  Bruin OnLine Service Level Agreement: xxxx://xxx.xxx.xxxx.xxx/policies/BOL_SLA.pdf Any violation may result in technology related privileges being restricted or revoked and may also result in The University undertaking disciplinary or civil action. If the violation constitutes a criminal offense, appropriate legal action may be taken.

  • Domain Name Registration If Customer submits a Service Order(s) for domain name registration services, the following terms shall also apply:

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Service Registration Certain of our Services require you to register to use them. In such case, you agree that a l information you provide is truthful, current and complete. If there is any change to your registration information, you agree to provide us with updated information immediately. To the extent any of the Services are password protected, you agree to keep such password confidential and not to share it with any third party. You also agree that you wil not access any Services for which a password is required by using any third party’s password. If you discover any use of your password other than by you, you agree to immediately notify us. If you become aware of unauthorized account access, you similarly agree to immediately notify us. At the end of any use of a password protected Service, you agree to exit and logout out of your user session. Under no circumstances sha l we be responsible for any loss or damage that may result if you fail to comply with these requirements.

  • NERC Registration If and to the extent any of the NTO’s facilities are NERC jurisdictional facilities, the ISO will register for certain NERC functions applicable to those NTO facilities. Such functions may include, without limitation, those functions designated by NERC to be “Reliability Coordinator” and “Balancing Authority” and “Transmission Planner” and “Planning Coordinator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

  • ELECTRONIC REGISTRATION In the event that the electronic registration system (hereinafter referred to as the “Teraview Electronic Registration System” or “TERS”) is operative in the applicable Land Titles Office in which the Property is registered, then at the option of the Vendor’s solicitor, the following provisions shall prevail, namely:

  • Publicity; Use of Names and Logos Vendor may use Citizens’ name and logo in its marketing materials, website and social media to indicate that it is a participating or contracted vendor for Citizens. However, Vendor may not in any way state, imply or infer that it holds a “preferred,” “approved,” “awarded,” “selected” or otherwise special status with Citizens in any such materials. This prohibition includes, but is not limited to, the use of endorsements or quotes from Citizens officials, Citizens vendor scores, or any other Citizens-related materials that may directly or indirectly imply that Vendor enjoys a special or preferred status with Citizens. Citizens reserves the right to determine that its name and/or logo have been misused and to request that Vendor cease using its name and/or logo in any way it deems inappropriate. Failure to comply will result in corrective action, up to and including contract termination. Vendor may only use the approved Citizens logo, which may be obtained by sending a request via email to: xxxxxxxx@xxxxxxxxxxx.xxx.

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