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.
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”).
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.
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.
Voter Registration When designated by the Secretary of State, the Contractor agrees to become a voter registration agency as defined by 17 V.S.A. §2103 (41), and to comply with the requirements of state and federal law pertaining to such agencies.
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.
Filing and Effectiveness of Registration Statement; Certain Defined Terms The Company has filed with the Commission a registration statement on Form S-3 (File No. 333-216864) covering the registration of the Offered Securities under the Act, including a related preliminary prospectus or prospectuses. At any particular time, this initial registration statement, as amended, in the form then on file with the Commission, including all material then incorporated by reference therein, all information contained in the registration statement (if any) filed pursuant to Rule 462(b) and then deemed to be a part of the initial registration statement, and all 430A Information, all 430B Information and all 430C Information, if any, that in any case has not then been superseded or modified, shall be referred to as the “Initial Registration Statement”. The Company may also have filed, or may file with the Commission, a Rule 462(b) registration statement covering the registration of Offered Securities. At any particular time, this Rule 462(b) registration statement, in the form then on file with the Commission, including the contents of the Initial Registration Statement incorporated by reference therein and including all 430A Information, all 430B Information and all 430C Information, if any, that in any case has not then been superseded or modified, shall be referred to as the “Additional Registration Statement”. As of the time of execution and delivery of this agreement (this “Agreement”), the Initial Registration Statement has been declared effective under the Act and is not proposed to be amended, and no stop order suspending the effectiveness of the Initial Registration Statement has been issued by the Commission and to the knowledge of the Company no proceedings for that purpose have been instituted or threatened by the Commission. Any Additional Registration Statement has or will become effective upon filing with the Commission pursuant to Rule 462(b) and is not proposed to be amended. The Offered Securities all have been or will be duly registered under the Act pursuant to the Initial Registration Statement and, if applicable, the Additional Registration Statement. For purposes of this Agreement:
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.
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.
