Transfer or Deletion of Student Data The Provider shall review, on an annual basis, whether the Student Data it has received pursuant to the DPA continues to be needed for the purpose(s) of the Service Agreement and this DPA. If any of the Student Data is no longer needed for purposes of the Service Agreement and this DPA, the Provider will provide written notice to the LEA as to what Student Data is no longer needed. The Provider will delete or transfer Student Data in readable form to the LEA, as directed by the LEA (which may be effectuated through Exhibit D of the DPA), within 30 calendar days if the LEA requests deletion or transfer of the Student Data and shall provide written confirmation to the LEA of such deletion or transfer. Upon termination of the Service Agreement between the Provider and LEA, Provider shall conduct a final review of Student Data within 60 calendar days. If the LEA receives a request from a parent, as that term is defined in 105 ILCS 10/2(g), that Student Data being held by the Provider be deleted, the LEA shall determine whether the requested deletion would violate State and/or federal records laws. In the event such deletion would not violate State or federal records laws, the LEA shall forward the request for deletion to the Provider. The Provider shall comply with the request and delete the Student Data within a reasonable time period after receiving the request. Any provision of Student Data to the LEA from the Provider shall be transmitted in a format readable by the LEA.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐▇▇▇▇▇▇-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)
Unbundled Network Elements 35.4.1. The charges that CLEC shall pay to Sprint for Unbundled Network Elements are set forth in Table One of this Agreement. 35.5. Collocation
35.5.1. The charges that CLEC shall pay to Sprint for Collocation are set forth in Table Two of this Agreement. 35.6. Call Related Databases
6.1. The charges that CLEC shall pay to Sprint for Call Related Databases purchased pursuant to Part J are set forth in Table One of this Agreement.
Unbundled Sub-Loop Feeder 2.8.4.1 Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and cross-box (or other access point) that serves an end user location.
2.8.4.2 USLF utilized for voice traffic can be configured as 2-wire voice (USLF-2W/V) or 4-wire voice (USLF-4W/V).
2.8.4.3 USLF utilized for digital traffic can be configured as 2-wire ISDN (USLF-2W/I); 2-wire Copper (USLF-2W/C); 4-wire Copper (USLF-4W/C); 4-wire DS0 level loop (USLF-4W/D0); or 4-wire DS1 and ISDN (USLF-4W/DI).
2.8.4.4 USLF will provide access to both the equipment and the features in the BellSouth central office and BellSouth cross box necessary to provide a 2W or 4W communications pathway from the BellSouth central office to the BellSouth cross- box. This element will allow for the connection of Global Connection’s loop distribution elements onto BellSouth's feeder system.