Provider Directory a. The Contractor shall make available in electronic form and, upon request, in paper form, the following information about its network providers:
Directory To participate in the MnDOT TGB program, a business must be certified at the time of contract execution. Certified Targeted Group Businesses are listed in the Directory of Certified Targeted Group, Economically Disadvantaged and VET Vendors. MnDOT makes no representation as to any TGB’s technical or financial ability to perform the work. Prime contractors are solely responsible for performing due diligence in hiring TGB firms. A TGB’s failure to perform the work will not be considered justification for a compensation increase or time extension.
Volunteer Peer Assistants 1. Up to eight (8)
Posting of Seniority Lists See the Local Provisions Appendix L5.
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.
International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
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
Chief Executive Office; Collateral Locations The chief executive office of Borrower and Borrower's Records concerning Accounts are located only at the address set forth below and its only other places of business and the only other locations of Collateral, if any, are the addresses set forth in the Information Certificate, subject to the right of Borrower to establish new locations in accordance with Section 9.2 below. The Information Certificate correctly identifies any of such locations which are not owned by Borrower and sets forth the owners and/or operators thereof and to the best of Borrower's knowledge, the holders of any mortgages on such locations.
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.
International or National Shopping Goods estimated to cost less than $30,000 equivalent per contract may be procured under contracts awarded on the basis of international or national shopping procedures in accordance with the provisions of paragraphs 3.5 and 3.6 of the Guidelines.