Handling of Registry Data Sample Clauses

Handling of Registry Data. (c) (i) Data Escrow. Registry Operator shall establish at its expense a data escrow or mirror site policy for the Registry Data compiled by Registry Operator. Registry Data, as used in this Agreement, shall mean the following: (1) data for domains sponsored by all registrars, consisting of domain name, server name for each nameserver, registrar id, updated date, creation date, expiration date, status information, and DNSSEC related key material (if Registry Operator implements DNSSEC); (2) data for nameservers sponsored by all registrars consisting of server name, each IP address, registrar id, updated date, creation date, expiration date, and status information; (3) data for registrars sponsoring registered domains and nameservers, consisting of registrar id, registrar address, registrar telephone number, registrar e-mail address, whois server, referral URL, updated date and the name, telephone number, and e-mail address of all the registrar’s administrative, billing, and technical contacts; (4) domain name registrant data collected by the Registry Operator from registrars as part of or following registration of a domain name; and (5) the DNSSEC-related material necessary to sign the .biz zone (e.g., public and private portions of .biz zone key-signing keys and zone-signing keys)(if Registry Operator implements DNSSEC). The escrow agent or mirror-site manager, and the obligations thereof, shall be mutually agreed upon by ICANN and Registry Operator on commercially reasonable standards that are technically and practically sufficient to allow a successor registry operator to assume management of the TLD. To this end, Registry Operator shall periodically deposit into escrow all Registry Data on a schedule (not more frequently than weekly for a complete set of Registry Data, and daily for incremental updates) and in an electronic format mutually approved from time to time by Registry Operator and ICANN, such approval not to be unreasonably withheld by either party. In addition, Registry Operator will deposit into escrow that data collected from registrars as part of offering Registry Services introduced after the Effective Date of this Agreement. The schedule, content, format, and procedure for escrow deposits shall be as reasonably established by ICANN from time to time, and as set forth in Appendix 1 hereto. Changes to the schedule, content, format, and procedure may be made only with the mutual written consent of ICANN and Registry Operator (which neither ...
AutoNDA by SimpleDocs
Handling of Registry Data. (i Data Escrow. Sponsor shall establish at its expense a data escrow or mirror site policy for the Registry Data compiled by Sponsor. Registry Data, as used in this Agreement, shall mean the following: (1) data for domains sponsored by all registrars, consisting of domain name, server name for each nameserver, registrar id, updated date, creation date, expiration date, status information, and DNSSEC DS data (if Sponsor's Registry Operator implements DNSSEC); (2) data for nameservers sponsored by all registrars consisting of server name, each IP address, registrar id, updated date, creation date, expiration date, and status information; (3) data for registrars sponsoring registered domains and nameservers, consisting of registrar id, registrar address, registrar telephone number, registrar e-mail address, whois server, referral URL, updated date and the name, telephone number, and e-mail address of all the registrar's administrative, billing, and technical contacts; and (4) domain name registrant data collected by the Sponsor from registrars as part of or following registration of a domain name. The escrow agent or mirror-site manager, and the obligations thereof, shall be mutually agreed upon by ICANN and Sponsor and such escrow shall be maintained at Sponsor's expense on commercially reasonable standards that are technically and practically sufficient to allow a successor registry operator to assume management of the TLD. To this end, Sponsor shall periodically deposit into escrow all Registry Data on a schedule (not more frequently than weekly for a complete set of Registry Data, and daily for incremental updates) and in an electronic format mutually approved from time to time by Sponsor and ICANN, such approval not to be unreasonably withheld by either party. In addition, Sponsor will deposit into escrow that data collected from registrars as part of offering Sponsor Services introduced after the Effective Date of this Agreement. The schedule, content, format, and procedure for escrow deposits shall be as reasonably established by ICANN from time to time, and as set forth in Appendix 1 hereto. Changes to the schedule, content, format, and procedure may be made only with the mutual written consent of ICANN and Sponsor (which neither party shall unreasonably withhold) or through the establishment of a Consensus Policy as outlined in Section 3.1(b) above. The escrow shall be held under an agreement, substantially in the form of Appendix 2, as the same may ...
Handling of Registry Data 

Related to Handling of Registry Data

  • Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

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

  • Costs of updating of registration statement If provided for in the Prospectus for a Trust, the Trustee shall pay, or reimburse to the Depositor, the expenses related to the updating of the Trust's registration statement, to the extent of legal fees, typesetting fees, electronic filing expenses and regulatory filing fees. Such expenses shall be paid from the Income Account, or to the extent funds are not available in such Account, from the Capital Account, against an invoice or invoices therefor presented to the Trustee by the Depositor. By presenting such invoice or invoices, the Depositor shall be deemed to certify, upon which certification the Trustee is authorized conclusively to rely, that the amounts claimed therein are properly payable pursuant to this paragraph. The Depositor shall provide the Trustee, from time to time as requested, an estimate of the amount of such expenses, which the Trustee shall use for the purpose of estimating the accrual of Trust expenses. The amount paid by the Trust pursuant to this paragraph in each year shall be separately identified in the annual statement provided to Unit holders. The Depositor shall assure that the Prospectus for the Trust contains such disclosure as shall be necessary to permit payment by the Trust of the expenses contemplated by this paragraph under applicable laws and regulations. The provisions of this paragraph shall not limit the authority of the Trustee to pay, or reimburse to the Depositor or others, such other or additional expenses as may be determined to be payable from the Trust as provided in this Section 6.02.

  • Marking of Data Pursuant to Paragraph A above, any Data delivered under this Agreement shall be marked with the following legend: Use, duplication, or disclosure is subject to the restrictions as stated in Agreement HR0011-XX-9-XXXX between the Government and the Performer.

  • Marking of Records At its expense, the Seller will xxxx its master data processing records evidencing Pool Receivables and related Contracts with a legend evidencing that Receivable Interests related to such Pool Receivables and related Contracts have been sold in accordance with the Agreement.

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

  • Contents of Registration Statement (i) The Registration Statement, when it became effective, did not contain and, as amended or supplemented, if applicable, will not contain any untrue statement of a material fact or omit to state a material fact required to be stated therein or necessary to make the statements therein not misleading, (ii) the Registration Statement and the Prospectus comply and, as amended or supplemented, if applicable, will comply in all material respects with the Securities Act and the applicable rules and regulations of the Commission thereunder and (iii) the Prospectus does not contain and, as amended or supplemented, if applicable, will not contain any untrue statement of a material fact or omit to state a material fact necessary to make the statements therein, in the light of the circumstances under which they were made, not misleading, except that the representations and warranties set forth in this paragraph do not apply to statements or omissions in the Registration Statement or the Prospectus based upon information relating to any Underwriter furnished to the Company in writing by such Underwriter through you expressly for use therein.

  • Maintenance of Registration For a period of at least five (5) years from the Effective Date, or until such earlier time upon which the Company is required to be liquidated, the Company will use its best efforts to maintain the registration of the Units, Common Stock and Warrants under the provisions of the Exchange Act, except after giving effect to a going private transaction after the completion of an Initial Business Combination. The Company will not deregister the Units, Common Stock or Warrants under the Exchange Act (except in connection with a going private transaction after the completion of an Initial Business Combination) without the prior consent of the Representative.

  • Expenses of Registration All expenses incurred in connection with registrations, filings or qualifications pursuant to Sections 2 and 3, including, without limitation, all registration, listing and qualifications fees, printers, legal and accounting fees shall be paid by the Company.

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