ISP-Bound Traffic Minutes Growth Cap Sample Clauses

ISP-Bound Traffic Minutes Growth Cap. 14.4.1 On a calendar year basis, as set forth below, CLEC and ILEC agree to cap overall compensable ISP-Bound Traffic minutes of use (“Growth Cap”). The Parties agree that the Growth Cap shall be an amount equal to: 1st Quarter 2001 compensable ISP-Bound minutes of use, multiplied by 4, multiplied by 1.21, plus all minutes of use terminated by ILEC on behalf of CLEC pursuant to the Parties’ COBRA Agreement.2 2 In the event a carrier adopts this ICA and Amendment pursuant to Section 252(i), the growth cap for the adopting carrier shall be: 1st Quarter 2001 compensable ISP-Bound minutes of use, multiplied by 4, multiplied by 1.21; provided, however, that if such carrier also had a COBRA Agreement with SBC which has been terminated, the adopting carrier’s growth cap shall also include the addition of the minutes of use terminated by SBC on behalf of the adopting carrier pursuant to the Parties’ COBRA Agreement.
Sample 1
AutoNDA by SimpleDocs
ISP-Bound Traffic Minutes Growth Cap. 2.3.1 On a calendar year basis, as set forth below, LEC and ILEC agree to cap overall compensable Missouri ISP-Bound Traffic minutes of use in the future based upon the 1st Quarter 2001 ISP-Bound Traffic minutes for which LEC was entitled to compensation under its Missouri Interconnection Agreement(s) in existence for the 1st Quarter of 2001, on the following schedule. Calendar Year 2001 1st Quarter 2001 compensable ISP-Bound minutes, times 4, times 1.10 Calendar Year 2002 Year 2001 compensable ISP-Bound minutes, times 1.10 Calendar Year 2003 Year 2002 compensable ISP-Bound minutes Calendar Year 2004 and on Year 2002 compensable ISP-Bound minutes Notwithstanding anything contrary herein, in Calendar Year 2004, LEC and ILEC agree that ISP-Bound Traffic exchanged between LEC and ILEC during the entire period from January 1, 2004 until December 31, 2004 shall be counted towards determining whether LEC has exceeded the growth caps for Calendar Year 2004.
Sample 1

Related to ISP-Bound Traffic Minutes Growth Cap

  • ISP-Bound Traffic 7.3.6.1 The Parties agree that ISP-bound traffic is Interstate traffic and governed by the FCC’s Order on Remand and Report and Order (Intercarrier Compensation for ISP-bound Traffic) CC Docket 01-131 (FCC ISP Order), effective June 14, 2001. However, the Parties agree to exchange ISP-bound traffic utilizing the xxxx and keep compensation mechanism. Xxxx and keep will apply to both end office call termination and tandem switched transport of ISP-bound traffic.

  • Erosion Prevention and Control Purchaser’s Operations shall be conducted reasonably to minimize soil erosion. Equipment shall not be operated when ground conditions are such that excessive damage will result. Purchaser shall adjust the kinds and intensity of erosion control work done to ground and weather condi- tions and the need for controlling runoff. Erosion control work shall be kept current immediately preceding ex- pected seasonal periods of precipitation or runoff. If Purchaser fails to do seasonal erosion control work prior to any seasonal period of precipitation or runoff, Forest Service may temporarily assume responsibility for the work and any unencumbered deposits hereunder may be used by Forest Service to do the work. If needed for such work, Purchaser shall make additional deposits on request by Forest Service. Any money deposited or used for this purpose shall be treated as cooperative deposits under B4.218.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • -wire Unbundled Digital/DS0 Loop These are designed 4-wire Loops that may be configured as 64kbps, 56kbps, 19kbps, and other sub-rate speeds associated with digital data services and will come standard with a test point, OC, and a DLR.

  • Web-based-WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the HTTP response for only one HTTP request. If Registry Operator implements a multiple-step process to get to the information, only the last step shall be measured. If the RTT is 5-times or more the corresponding SLR, the RTT will be considered undefined.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Requirements Pertaining Only to Federal Grants and Subrecipient Agreements If this Agreement is a grant that is funded in whole or in part by Federal funds:

  • DNS update time Refers to the time measured from the reception of an EPP confirmation to a transform command on a domain name, until the name servers of the parent domain name answer “DNS queries” with data consistent with the change made. This only applies for changes to DNS information.

  • Sector Sub-Sector Industry Classification Level of Government Type of Obligation Description of Measure Source of Measure All sectors : : - : Central : National Treatment Senior Management and Board of Directors : National Treatment and the Senior Management and Board of Directors obligations shall not apply to any measure relating to small and medium sized domestic market enterprise2. Foreign equity is restricted to a maximum of 40% for domestic market enterprises with paid-in equity capital of less than the equivalent of USD 200,000 Note: Members of the Board of Directors or governing body of corporation or associations shall be allowed in proportion to their allowable participation or share in the capital of such enterprises. : -1987 Constitution of the Republic of the Philippines. - Foreign Investments Act of 1991 (R.A. No. 7042, as amended by R.A. No. 8179). -Presidential and Administrative Issuances. ∞ 2 The concept of a small and medium sized domestic market enterprise is an enterprise with paid in equity capital of less than the equivalent of USD 200,000.00.

Time is Money Join Law Insider Premium to draft better contracts faster.