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.
LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.
Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years. b. Renewal registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms not exceeding a total of ten years. c. Upon change of sponsorship of the registration of a Registered Name from one registrar to another, according to Part A of the ICANN Policy on Transfer of Registrations between Registrars, the term of registration of the Registered Name shall be extended by one year, provided that the maximum term of the registration as of the effective date of the sponsorship change shall not exceed ten years. d. The change of sponsorship of registration of Registered Names from one registrar to another, according to Part B of the ICANN Policy on Transfer of Registrations between Registrars shall not result in the extension of the term of the registration and Registry Operator may assist in such change of sponsorship.
Registration in Nominee Name; Denominations The Collateral Agent, on behalf of the Secured Parties, shall have the right (in its sole and absolute discretion) to hold the Pledged Securities in its own name as pledgee, the name of its nominee (as pledgee or as sub-agent) or the name of the Pledgors, endorsed or assigned in blank or in favor of the Collateral Agent. Each Pledgor will promptly give to the Collateral Agent copies of any notices or other communications received by it with respect to Pledged Securities registered in the name of such Pledgor. The Collateral Agent shall at all times have the right to exchange the certificates representing Pledged Securities for certificates of smaller or larger denominations for any purpose consistent with this Agreement.
Registration and Indorsement It will ensure that all financial assets (other than cash) credited to the Collateral Account are registered in the name of the Financial Institution, indorsed to the Financial Institution or in blank or credited to another securities account maintained in the name of the Financial Institution and that no financial asset credited to the Collateral Account is registered in the name of the Grantor, payable to the order of the Grantor or specially indorsed to the Grantor unless it has been indorsed to the Financial Institution or in blank.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
COOPERATION IN PREPARATION OF REGISTRATION STATEMENT The COMPANY and STOCKHOLDERS shall furnish or cause to be furnished to VPI and the Underwriters all of the information concerning the COMPANY and the STOCKHOLDERS required for inclusion in, and will cooperate with VPI and the Underwriters in the preparation of, the Registration Statement and the prospectus included therein (including audited and unaudited financial statements, prepared in accordance with generally accepted accounting principles, in form suitable for inclusion in the Registration Statement). The COMPANY and the STOCKHOLDERS agree promptly to advise VPI if, at any time during the period in which a prospectus relating to the offering is required to be delivered under the 1933 Act, any information contained in the prospectus concerning the COMPANY or the STOCKHOLDERS becomes incorrect or incomplete in any material respect, and to provide the information needed to correct such inaccuracy. VPI will give the COMPANY and the STOCKHOLDERS an opportunity and a reasonable amount of time to review and comment on a substantially final draft of the Registration Statement prior to filing, and with respect to all amendments thereto, VPI will give the COMPANY and STOCKHOLDERS an opportunity to review and comment on those portions of such amendments that relate to the COMPANY. Insofar as the information contained in the Registration Statement relates solely to the COMPANY or the STOCKHOLDERS, as of the effective date of the Registration Statement the COMPANY represents and warrants as to such information with respect to itself, and each STOCKHOLDER represents and warrants, as to such information with respect to the COMPANY and himself or herself, that the Registration Statement will not include an 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, in light of the circumstances in which they were made, not misleading and that the STOCKHOLDERS and the COMPANY have had the opportunity to review and approve such information. If, prior to the 25th day after the date of the final prospectus of VPI utilized in connection with the IPO, the COMPANY or the STOCKHOLDERS become aware of any fact or circumstance which would change (or, if after the Closing Date, would have changed) a representation or warranty of the COMPANY or the STOCKHOLDERS in this Agreement or would affect any document delivered pursuant hereto in any material respect, the COMPANY and the STOCKHOLDERS shall immediately give notice of such fact or circumstance to VPI. However, subject to the provisions of Section 7.8, such notification shall not relieve either the COMPANY or the STOCKHOLDERS of their respective obligations under this Agreement, and, subject to the provisions of Section 7.8, at the sole option of VPI, the truth and accuracy of any and all warranties and representations of the COMPANY, or on behalf of the COMPANY and of STOCKHOLDERS at the date of this Agreement and on the Pre-Closing Date and on the Closing Date, contained in this Agreement (including the Schedules and Annexes hereto) shall be a precondition to the consummation of this transaction.
Segregation and Registration Except as otherwise provided herein, and except for securities to be delivered to any subcustodian appointed pursuant to Sections 14.2 or 14.3 hereof, the Bank as custodian will receive and hold pursuant to the provisions hereof, in a separate account or accounts and physically segregated at all times from those of other persons, any and all Portfolio Securities which may now or hereafter be delivered to it by or for the account of the Fund. All such Portfolio Securities will be held or disposed of by the Bank for, and subject at all times to, the instructions of the Fund pursuant to the terms of this Agreement. Subject to the specific provisions herein relating to Portfolio Securities that are not physically held by the Bank, the Bank will register all Portfolio Securities (unless otherwise directed by Proper Instructions or an Officers' Certificate), in the name of a registered nominee of the Bank as defined in the Internal Revenue Code and any Regulations of the Treasury Department issued thereunder, and will execute and deliver all such certificates in connection therewith as may be required by such laws or regulations or under the laws of any state. The Fund will from time to time furnish to the Bank appropriate instruments to enable it to hold or deliver in proper form for transfer, or to register in the name of its registered nominee, any Portfolio Securities which may from time to time be registered in the name of the Fund.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation
