Inclusion of MRC End Users in Directory Assistance Database. BellSouth will include and maintain MRC End User listings in BellSouth’s Directory Assistance databases. MRC shall provide such Directory Assistance listings to BellSouth at no charge.
Inclusion of MRC End Users in Directory Assistance Database Sample Clauses
Related to Inclusion of MRC End Users in Directory Assistance Database
Routing for Operator Services and Directory Assistance Traffic For a Verizon Telecommunications Service dial tone line purchased by CBB for resale pursuant to the Resale Attachment, upon request by CBB, Verizon will establish an arrangement that will permit CBB to route the CBB Customer’s calls for operator and directory assistance services to a provider of operator and directory assistance services selected by CBB. Verizon will provide this routing arrangement in accordance with, but only to the extent required by, Applicable Law. Verizon will provide this routing arrangement pursuant to an appropriate written request submitted by CBB and a mutually agreed-upon schedule. This routing arrangement will be implemented at CBB's expense, with charges determined on an individual case basis. In addition to charges for initially establishing the routing arrangement, CBB will be responsible for ongoing monthly and/or usage charges for the routing arrangement. CBB shall arrange, at its own expense, the trunking and other facilities required to transport traffic to CBB’s selected provider of operator and directory assistance services.
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
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.
The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.
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.
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.
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.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
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.
Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.
