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.
Unbundled Copper Loop – Non-Designed (UCL-ND 2.4.3.1 The UCL–ND is provisioned as a dedicated 2-wire metallic transmission facility from BellSouth’s Main Distribution Frame to a customer’s premises (including the NID). The UCL-ND will be a “dry copper” facility in that it will not have any intervening equipment such as load coils, repeaters, or digital access main lines (“DAMLs”), and may have up to 6,000 feet of bridged tap between the end user’s premises and the serving wire center. The UCL-ND typically will be 1300 Ohms resistance and in most cases will not exceed 18,000 feet in length, although the UCL-ND will not have a specific length limitation. For loops less than 18,000 feet and with less than 1300 Ohms resistance, the loop will provide a voice grade transmission channel suitable for loop start signaling and the transport of analog voice grade signals. The UCL-ND will not be designed and will not be provisioned with either a DLR or a test point.
2.4.3.2 The UCL-ND facilities may be mechanically assigned using BellSouth’s assignment systems. Therefore, the Loop Make Up process is not required to order and provision the UCL-ND. However, Lightyear can request Loop Make Up for which additional charges would apply.
2.4.3.3 At an additional charge, BellSouth also will make available Loop Testing so that Lightyear may request further testing on the UCL-ND. Rates for Loop Testing are as set forth in Exhibit B of this Attachment.
2.4.3.4 UCL-ND loops are not intended to support any particular service and may be utilized by Lightyear to provide a wide-range of telecommunications services so long as those services do not adversely affect BellSouth’s network. The UCL-ND will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the loop to the customer’s inside wire.
2.4.3.5 Order Coordination (OC) will be provided as a chargeable option and may be utilized when the UCL-ND provisioning is associated with the reuse of BellSouth facilities. Order Coordination -Time Specific (OC-TS) does not apply to this product.
2.4.3.6 Lightyear may use BellSouth’s Unbundled Loop Modification (ULM) offering to remove bridge tap and/or load coils from any loop within the BellSouth network. Therefore, some loops that would not qualify as UCL-ND could be transformed into loops that do qualify, using the ULM process.
Unbundled Copper Sub-Loop (UCSL) is a copper facility of any length provided from the cross-box in the field up to and including the end-user’s point of demarcation. If available, this facility will not have any intervening equipment such as load coils between the end-user and the cross-box.
Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters).
2.4.2.2 A UCL-D will be 18,000 feet or less in length and is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 Ohms of resistance.
2.4.2.3 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Telepak Networks.
2.4.2.4 These Loops are not intended to support any particular services and may be utilized by Telepak Networks to provide a wide-range of telecommunications services as long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the Loop to the customer’s inside wire.
2.4.2.5 Upon the Effective Date of this Agreement, Unbundled Copper Loop – Long (UCL-L) elements will no longer be offered by BellSouth and no new orders for UCL-L will be accepted. Any existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement will be grandfathered at the rates set forth in the Parties’ interconnection agreement that was in effect immediately prior to the Effective Date of this Agreement. Existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement may remain connected, maintained and repaired according to BellSouth’s TR73600 and may remain connected until such time as they are disconnected by Telepak Networks or BellSouth provides ninety
Unbundled Copper Loops (UCL) 2.4.1 BellSouth shall make available Unbundled Copper Loops (UCLs). The UCL is a copper twisted pair Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters) and is not intended to support any particular telecommunications service. The UCL will be offered in two types – Designed and Non-Designed.
COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.
Dark Fiber Transport Dark Fiber Transport is defined as Dedicated Transport that consists of unactivated optical interoffice transmission facilities without attached signal regeneration, multiplexing, aggregation or other electronics. Except as set forth in Section 6.9.1 below, BellSouth shall not be required to provide access to Dark Fiber Transport Entrance Facilities pursuant to this Agreement.
Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks.
2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI.
2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks.
2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.
2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5).
2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275.
2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three
NYISO and Connecting Transmission Owner Obligations Connecting Transmission Owner and NYISO shall cause the New York State Transmission System and the Connecting Transmission Owner’s Attachment Facilities to be operated, maintained and controlled in a safe and reliable manner in accordance with this Agreement and the NYISO Tariffs. Connecting Transmission Owner and NYISO may provide operating instructions to Developer consistent with this Agreement, NYISO procedures and Connecting Transmission Owner’s operating protocols and procedures as they may change from time to time. Connecting Transmission Owner and NYISO will consider changes to their respective operating protocols and procedures proposed by Developer.
Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason:
(1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met:
(a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed.
(b) The Data will be Encrypted while within the Contractor network.
(c) The Data will remain Encrypted during transmission to the Cloud.
(d) The Data will remain Encrypted at all times while residing within the Cloud storage solution.
(e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS.
(f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks.
(g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network.
(2) Data will not be stored on an Enterprise Cloud storage solution unless either:
(a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or,
(b) The Cloud storage solution used is FedRAMP certified.
(3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.
