Directory Assistance 72.1 The Parties acknowledge that CenturyLink is not a Directory Assistance (DA) provider. CenturyLink provides directory listings information for its subscribers to third party DA providers to be included in the national and local databases used by such third party providers. The Parties agree that to the extent the DA provider contracted by CLEC for DA services to CLEC’s subscribers also populates the national DA database, then CLEC’s DA listings have been made available to CenturyLink’s subscribers and no further effort is needed by either Party. If for any reason, CLEC desires that CenturyLink act as a middleman conduit for the placement of CLEC’s DA listings in the DA database(s), then CenturyLink shall provide such compensable DA listings service pursuant to separate written terms and conditions between CenturyLink and CLEC which will be attached to this Agreement as an Amendment.
Directory Assistance Service 8.3.1 Directory Assistance Service provides local end user telephone number listings with the option to complete the call at the caller's direction separate and distinct from local switching.
Directory Assistance Service Updates 8.3.3.1 BellSouth shall update end user listings changes daily. These changes include: 8.3.3.1.1 New end user connections 3.3.1.2 End user disconnections
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.
Regulatory Assistance Provider will permit regulators with jurisdiction over BFA or any BFA Recipient to examine Provider’s activities relating to its performance under this Agreement and the Services. Subject to Section 17.6, Provider will cooperate and provide all information reasonably requested by the regulator in connection with any such examination and provide reasonable assistance and access to all equipment, records, and systems requested by the regulator relating to the Services.
