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.
Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.
Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers. 2.8.3.2 This element will be provided in MDUs and/or Multi-Tenants Units (MTUs) where either Party owns wiring all the way to the End User’s premises. Neither Party will provide this element in locations where the property owner provides its own wiring to the End User’s premises, where a third party owns the wiring to the End User’s premises.
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
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, 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.