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.
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.
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.
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.
BROKER-DEALER REGISTRATION; FINRA MEMBERSHIP The Dealer Manager is, and during the term of this Agreement will be, (i) duly registered as a broker-dealer pursuant to the provisions of the Exchange Act, (ii) a member in good standing of FINRA, and (iii) a broker or dealer duly registered as such in those states where the Dealer Manager is required to be registered in order to carry out the Offering as contemplated by this Agreement. Each of the Dealer Manager’s employees and representatives has all required licenses and registrations to act under this Agreement. There is no provision in the Dealer Manager’s FINRA membership agreement that would restrict the ability of the Dealer Manager to carry out the Offering as contemplated by this Agreement.
NERC Registration The NTO shall register or enter into agreement with a NERC registered entity for all required NERC functions applicable to the NTO, that may include, without limitation, those functions designated by NERC to be: “Transmission Owner” and “Transmission Planner” and “Transmission Operator.” 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.
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.
Copies of Registration Statement The Company will furnish the Dealer Manager with one signed copy of the Registration Statement, including its exhibits, and such additional copies of the Registration Statement, without exhibits, and the Prospectus and all amendments and supplements thereto, which are finally approved by the Commission, as the Dealer Manager may reasonably request for sale of the Shares.
Registration Compliance; No Stop Orders The Registration Statement has become effective under the Securities Act, and no stop order suspending the effectiveness of the Registration Statement or any part thereof, preventing or suspending the use of any Preliminary Prospectus, the Prospectus or any Permitted Free Writing Prospectus or any part thereof shall have been issued and no proceedings for that purpose or pursuant to Section 8A under the Securities Act shall have been initiated or threatened by the Commission, and all requests for additional information on the part of the Commission (to be included in the Registration Statement or the Prospectus or otherwise) shall have been complied with to the reasonable satisfaction of the Representative; the Rule 462(b) Registration Statement, if any, and the Prospectus shall have been filed with the Commission within the applicable time period prescribed for such filing by, and in compliance with, the Rules and Regulations and in accordance with Section 4(a) of this Agreement, and the Rule 462(b) Registration Statement, if any, shall have become effective immediately upon its filing with the Commission; and FINRA shall have raised no unresolved objection to the fairness and reasonableness of the terms of this Agreement or the transactions contemplated hereby.
