Schematic Design See Section 2, Part 1, Article 2.1.4, Paragraph 2.1.4.2.
Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.
zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.
TECHNICAL GUIDANCE LETTERS In the sole discretion of the System Agency, and in conformance with federal and state law, the System Agency may issue instructions, clarifications, or interpretations as may be required during work performance in the form of a Technical Guidance Letter (TGL). A TGL must be in writing, and may be delivered by regular mail, electronic mail, or facsimile transmission. Any TGL issued by the System Agency will be incorporated into the Contract by reference for all purposes when it is issued.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
Construction Change Directives 1.1.1, 3.4.2, 3.11, 3.12.8, 4.2.8, 7.1.1, 7.1.2, 7.1.3, 7.3, 9.3.1.1 Construction Schedules, Contractor’s 3.10, 3.11, 3.12.1, 3.12.2, 6.1.3, 15.1.6.2
Switching and Tagging Rules Each Party shall provide the other Parties a copy of its switching and tagging rules that are applicable to the other Parties’ activities. Such switching and tagging rules shall be developed on a non-discriminatory basis. The Parties shall comply with applicable switching and tagging rules, as amended from time to time, in obtaining clearances for work or for switching operations on equipment.
Protocol The attached Protocol shall be an integral part of this Agreement.