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.
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”).
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.
CLEC to CLEC Conversions for Unbundled Loops 2.1.10.1 The CLEC to CLEC conversion process for unbundled Loops may be used by Lightyear when converting an existing unbundled Loop from another CLEC for the same end user. The Loop type being converted must be included in Lightyear’s Interconnection Agreement before requesting a conversion. 2.1.10.2 To utilize the CLEC to CLEC conversion process, the Loop being converted must be the same Loop type with no requested changes to the Loop, must serve the same end user location from the same serving wire center, and must not require an outside dispatch to provision. 2.1.10.3 The Loops converted to Lightyear pursuant to the CLEC to CLEC conversion process shall be provisioned in the same manner and with the same functionality and options as described in this Attachment for the specific Loop type. Order Coordination (OC) Order Coordination – Time Specific (OC-TS) Test Points DLR Charge for Dispatch and Testing if No Trouble Found SL-1 (Non- Designed) Chargeable Option Chargeable Option Not available Chargeable Option – ordered as Engineering Information Document Charged for Dispatch inside and outside Central Office UCL-ND (Non- Designed) Chargeable Option Not Available Not Available Chargeable Option – ordered as Engineering Information Document Charged for Dispatch inside and outside Central Office Unbundled Voice Loops - SL-2 (including 2- and 4-wire UVL) (Designed) Included Chargeable Option Included Included Charged for Dispatch outside Central Office Unbundled Digital Loop (Designed) Included Chargeable Option (except on Universal Digital Channel) Included (where appropriate) Included Charged for Dispatch outside Central Office Unbundled Copper Loop (Designed) Chargeable in accordance with Section 2 Not available Included Included Charged for Dispatch outside Central Office For UVL-SL1 and UCLs, Lightyear must order and will be billed for both OC and OC-TS if requesting OC-TS.
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.
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.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Registration of ADS Transfer Fee by any Holder of ADS(s) being transferred or by any person to whom ADSs are transferred, a fee not in excess of U.S. $5.00 per 100 ADSs (or fraction thereof) transferred (e.g., upon a registration of the transfer of registered ownership of ADSs, upon a transfer of ADSs into DTC and vice versa, or for any other reason); and
