Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59
NON-NETWORK PROVIDER is a provider that has not entered into a contract with us or any other Blue Cross and Blue Shield plan. For pediatric dental care services, non-network provider is a dentist that has not entered into a contract with us or does not participate in the Dental Coast to Coast Network. For pediatric vision hardware services, a non-network provider is a provider that has not entered into a contract with EyeMed, our vision care service manager.
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
Directory Listings 15.1.1 CBT, as publisher of its White Pages, will include Primary Listings of CLEC’s resale directory customers in its White Pages, and shall cause its publisher to include primary listings of CLEC’s directory customers in its Publisher’s Yellow Pages Directories under the following terms and conditions:
15.1.1.1 CBT will publish the Primary Listing of CLEC Directory Customers located within the geographic scope of its White Pages directory and will recover costs for both resale and facility based Customers in accordance with the Act.
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.
Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.
13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management
Stock Plan Administration Service Provider The Company transfers the Optionee's Personal Information to Fidelity Stock Plan Services LLC, an independent service provider based in the United States, which assists the Company with the implementation, administration and management of the Plan (the “Stock Plan Administrator”). In the future, the Company may select a different Stock Plan Administrator and share the Optionee's Personal Information with another company that serves in a similar manner. The Stock Plan Administrator will open an account for the Optionee to receive and trade Shares acquired under the Plan. The Optionee will be asked to agree on separate terms and data processing practices with the Stock Plan Administrator, which is a condition to the Optionee’s ability to participate in the Plan.
Provider Network The Panel of health service Providers with which the Contractor contracts for the provision of covered services to Members and Out-of-network Providers administering services to Members.
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.
