Identification of ISP Sample Clauses

Identification of ISP. Bound Traffic – CenturyLink will presume traffic delivered to CLEC that exceeds a 3:1 ratio of terminating (CenturyLink to CLEC) to originating (CLEC to CenturyLink) traffic is ISP-Bound traffic. Either Party may rebut this presumption by demonstrating the factual ratio to the Commission. Traffic exchanged that is not ISP-Bound traffic will be considered to be Section 251(b)(5) traffic. The provisions in this Section apply regardless how the ISP-Bound traffic is determined.
View SourceView Similar (13)
Identification of ISP. Bound Traffic -- Qwest will presume traffic delivered to CLEC that exceeds a 3:1 ratio of terminating (Qwest to CLEC) to originating (CLEC to Qwest) traffic is ISP-bound traffic. Either Party may rebut this presumption by demonstrating the factual ratio to the Commission. Traffic exchanged that is not ISP- bound traffic will be considered to be Section 251(b)(5)
View SourceView Similar (3)
Identification of ISP. Bound traffic -- The Parties will presume traffic delivered to a Party that exceeds a 3:1 ratio of terminating to originating traffic is ISP-bound traffic. Either Party may rebut this presumption by demonstrating the factual ratio to the state Commission.
View SourceView Similar (2)
Identification of ISP. Bound traffic -- Qwest will presume traffic delivered to CLEC that exceeds a 3:1 ratio of terminating (Qwest to CLEC) to originating (CLEC to Qwest) traffic is ISP-bound traffic. Either Party may rebut this presumption by demonstrating to the state Commission that the traffic above this ratio is in fact EAS/Local (§251(b)(5)) Traffic delivered to non-ISP customers, which is subject instead to the compensation mechanisms, set forth in Section 7.3.4.3 above. The same identification procedures and presumption shall apply for CLEC traffic delivered to Qwest in terminating traffic as well.
View SourceView Similar (2)

Related to Identification of ISP

  • Identification When performing work on District property, Contractor shall be in appropriate work attire (or uniform, if applicable) at all times. If Contractor does not have a specific uniform, then Contractor shall provide identification tags and/or any other mechanism the District in its sole discretion determines is required to easily identify Contractor. Contractor and its employees shall (i) display on their clothes the above-mentioned identifying information and (ii) carry photo identification and present it to any District personnel upon request. If Contractor cannot produce such identification or if the identification is unacceptable to District, District may provide at its sole discretion, District-produced identification tags to Contractor, costs to be borne by Contractor.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.