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.
Access to Data Operator shall make Data in the possession of the Operator available to the LEA within five (5) business days of a request by the LEA.
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.
Delay of Registration; Furnishing Information (a) No Holder shall have any right to obtain or seek an injunction restraining or otherwise delaying any such registration as the result of any controversy that might arise with respect to the interpretation or implementation of this Section 2.
(b) It shall be a condition precedent to the obligations of the Company to take any action pursuant to Section 2.2, 2.3 or 2.4 that the selling Holders shall furnish to the Company such information regarding themselves, the Registrable Securities held by them and the intended method of disposition of such securities as shall be required to effect the registration of their Registrable Securities.
(c) The Company shall have no obligation with respect to any registration requested pursuant to Section 2.2 or Section 2.4 if the number of shares or the anticipated aggregate offering price of the Registrable Securities to be included in the registration does not equal or exceed the number of shares or the anticipated aggregate offering price required to originally trigger the Company’s obligation to initiate such registration as specified in Section 2.2 or Section 2.4, whichever is applicable.
Access to Records The Contractor and its subcontractors, if any, shall maintain all books, documents, papers, accounting records, and other evidence pertaining to all costs incurred under this Contract. They shall make such materials available at their respective offices at all reasonable times during this Contract, and for three (3) years from the date of final payment under this Contract, for inspection by the State or its authorized designees. Copies shall be furnished at no cost to the State if requested.
Access to Records; Copies The Assuming Bank agrees to permit the Receiver and the Corporation access to all Records of which the Assuming Bank has custody, and to use, inspect, make extracts from or request copies of any such Records in the manner and to the extent requested, and to duplicate, in the discretion of the Receiver or the Corporation, any Record in the form of microfilm or microfiche pertaining to Deposit account relationships; provided, that in the event that the Failed Bank maintained one or more duplicate copies of such microfilm or microfiche Records, the Assuming Bank hereby assigns, transfers, and conveys to the Corporation one such duplicate copy of each such Record without cost to the Corporation, and agrees to deliver to the Corporation all Records assigned and transferred to the Corporation under this Article VI as soon as practicable on or after the date of this Agreement. The party requesting a copy of any Record shall bear the cost (based on standard accepted industry charges to the extent applicable, as determined by the Receiver) for providing such duplicate Records. A copy of each Record requested shall be provided as soon as practicable by the party having custody thereof.
ACCESS TO RECORDS AND REPORTS The Contractor must maintain an acceptable cost accounting system. The Contractor agrees to provide the Sponsor, the Federal Aviation Administration, and the Comptroller General of the United States or any of their duly authorized representatives access to any books, documents, papers, and records of the contractor which are directly pertinent to the specific contract for the purpose of making audit, examination, excerpts and transcriptions. The Contractor agrees to maintain all books, records and reports required under this contract for a period of not less than three years after final payment is made and all pending matters are closed.
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.
Access to NID 2.7.3.1 NewPhone may access the customer’s premises wiring by any of the following means and NewPhone shall not disturb the existing form of electrical protection and shall maintain the physical integrity of the NID:
2.7.3.1.1 BellSouth shall allow NewPhone to connect its Loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premises;
2.7.3.1.2 Where an adequate length of the customer’s premises wiring is present and environmental conditions permit, either Party may remove the customer premises wiring from the other Party’s NID and connect such wiring to that Party’s own NID;
2.7.3.1.3 Either Party may enter the subscriber access chamber or dual chamber NID enclosures for the purpose of extending a cross-connect or spliced jumper wire from the customer premises wiring through a suitable “punch-out” hole of such NID enclosures; or
2.7.3.1.4 NewPhone may request BellSouth to make other rearrangements to the customer premises wiring terminations or terminal enclosure on a time and materials cost basis.
2.7.3.2 In no case shall either Party remove or disconnect the other Party’s loop facilities from either Party’s NIDs, enclosures, or protectors unless the applicable Commission has expressly permitted the same and the disconnecting Party provides prior notice to the other Party. In such cases, it shall be the responsibility of the Party disconnecting loop facilities to leave undisturbed the existing form of electrical protection and to maintain the physical integrity of the NID. It will be NewPhone’s responsibility to ensure there is no safety hazard, and NewPhone will hold BellSouth harmless for any liability associated with the removal of the BellSouth Loop from the BellSouth NID. Furthermore, it shall be the responsibility of the disconnecting Party, once the other Party’s loop has been disconnected from the NID, to reconnect the disconnected loop to a nationally recognized testing laboratory listed station protector, which has been grounded as per Article 800 of the National Electrical Code. If no spare station protector exists in the NID, the disconnected loop must be appropriately cleared, capped and stored.
2.7.3.3 NewPhone shall not remove or disconnect ground wires from BellSouth’s NIDs, enclosures, or protectors.
2.7.3.4 NewPhone shall not remove or disconnect NID modules, protectors, or terminals from BellSouth’s NID enclosures.
2.7.3.5 Due to the wide variety of NID enclosures and outside plant environments, BellSouth will work with NewPhone to develop specific procedures to establish the most effective means of implementing this section if the procedures set forth herein do not apply to the NID in question.
