Common use of SERVICE REQUIRMENTS Clause in Contracts

SERVICE REQUIRMENTS. 4.1 The Contracting QP shall place one (1) Order for each IP Multicast Connection. For example, if the Contracting QP wishes to take up two (2) IP Multicast Connections, the Contracting QP shall submit two (2) separate Orders. 4.2 When placing an Order for an IP Multicast Connection, the Contracting QP shall be required to: (a) Specify one (1) Service Port ID of the QP-EVPL Service Port and the NetLink Trust CO within Nucleus Connect’s Aggregation Network. (b) Specify the following Network protocol options: (i) Layer 2 VLAN (IEEE 802.1q); (ii) either IPv4 multicast address or (if and only where it is commercially available at Nucleus Connect’s determination) IPv6 multicast address; (iii) IGMP v2/v3. (c) Subscribe to one or more block(s) of 100Mbps Downlink CIR and 1Mbps Uplink CIR. The Downlink CIR shall comprise Class B Near Real Time and the Uplink CIR shall comprise Class D Best Effort, as set out below. The Contracting QP may subsequently from time to time, increase or decrease the number of block(s) of 100Mbps Downlink CIR and 1Mbps Uplink CIR, up to a maximum aggregate of Downlink CIR of 10Gbps/Uplink CIR of 100Mbps and no less than a minimum aggregate of Downlink CIR of 100Mbps/Uplink CIR of 1 Mbps. Such increase or decrease shall constitute a Modification for which the Contracting QP shall be required to submit an Order pursuant to and in accordance with the General Service Terms and Conditions. The table below sets out the performance parameters of each Class of Service: Class Of Service Jitter Latency Packet Loss 4.3 If the Contracting QP injects traffic into any IP Multicast Connection which exceeds the CIR purchased for such IP Multicast Connection pursuant to paragraph 4.2(c), the excess traffic will not be delivered. 4.4 The Contracting QP must adhere to Nucleus Connect’s QoS tagging scheme when sending or receiving data traffic through any IP Multicast Connection from the relevant Service Port(s). Such QoS tagging scheme requires the use of priority bit value 4 for Class B and priority bit value 1 for Class D. 4.5 The Contracting QP must procure and maintain, at its own cost, any equipment or software needed to receive or use and for the testing and commissioning of the IP Multicast Connection(s). 4.6 In the event that Nucleus Connect accepts an Order for IP Multicast Connection submitted by the Contracting QP in accordance with the General Service Terms and Conditions, Nucleus Connect will in relation to such accepted Order create VRF (Virtual Router Forwarding) and mVPN (multi-cast VPN).

Appears in 3 contracts

Samples: Interconnection Offer (Ico) Agreement, Interconnection Offer (Ico) Agreement, Service Schedule – Ip Multicast Connection

AutoNDA by SimpleDocs

SERVICE REQUIRMENTS. 4.1 The Contracting QP shall place one (1) Order for each IP Multicast Connection. For example, if the Contracting QP wishes to take up two (2) IP Multicast Connections, the Contracting QP shall submit two (2) separate Orders. 4.2 When placing an Order for an IP Multicast Connection, the Contracting QP shall be required to: (a) Specify one (1) Service Port ID of the QP-EVPL Service Port and the NetLink Trust OpenNet CO within Nucleus Connect’s Aggregation Network. (b) Specify the following Network protocol options: (i) Layer 2 VLAN (IEEE 802.1q); (ii) either IPv4 multicast address or (if and only where it is commercially available at Nucleus Connect’s determination) IPv6 multicast address; (iii) IGMP v2/v3. (c) Subscribe to one or more block(s) of 100Mbps Downlink CIR and 1Mbps Uplink CIR. The Downlink CIR shall comprise Class B Near Real Time and the Uplink CIR shall comprise Class D Best Effort, as set out below. The Contracting QP may subsequently from time to time, increase or decrease the number of block(s) of 100Mbps Downlink CIR and 1Mbps Uplink CIR, up to a maximum aggregate of Downlink CIR of 10Gbps/Uplink CIR of 100Mbps and no less than a minimum aggregate of Downlink CIR of 100Mbps/Uplink CIR of 1 Mbps. Such increase or decrease shall constitute a Modification for which the Contracting QP shall be required to submit an Order pursuant to and in accordance with the General Service Terms and Conditions. The table below sets out the performance parameters of each Class of Service: Class Of Service Jitter Latency Packet Loss 4.3 If the Contracting QP injects traffic into any IP Multicast Connection which exceeds the CIR purchased for such IP Multicast Connection pursuant to paragraph 4.2(c), the excess traffic will not be delivered. 4.4 The Contracting QP must adhere to Nucleus Connect’s QoS tagging scheme when sending or receiving data traffic through any IP Multicast Connection from the relevant Service Port(s). Such QoS tagging scheme requires the use of priority bit value 4 for Class B and priority bit value 1 for Class D. 4.5 The Contracting QP must procure and maintain, at its own cost, any equipment or software needed to receive or use and for the testing and commissioning of the IP Multicast Connection(s). 4.6 In the event that Nucleus Connect accepts an Order for IP Multicast Connection submitted by the Contracting QP in accordance with the General Service Terms and Conditions, Nucleus Connect will in relation to such accepted Order create VRF (Virtual Router Forwarding) and mVPN (multi-cast VPN).

Appears in 1 contract

Samples: Interconnection Offer (Ico) Agreement

AutoNDA by SimpleDocs

SERVICE REQUIRMENTS. 4.1 The Contracting QP shall place one (1) Order for each IP Multicast Connection. For example, if the Contracting QP wishes to take up two (2) IP Multicast Connections, the Contracting QP shall submit two (2) separate Orders. 4.2 When placing an Order for an IP Multicast Connection, the Contracting QP shall be required to: (a) Specify one (1) Service Port ID of the QP-EVPL Service Port and the NetLink Trust OpenNet CO within Nucleus Connect’s Aggregation Network. (b) Specify the following Network protocol options: (i) Layer 2 VLAN (IEEE 802.1q); (ii) either IPv4 multicast address or (if and only where it is commercially available at Nucleus Connect’s determination) IPv6 multicast address; (iii) IGMP v2/v3. (c) Subscribe to one or more block(s) of 100Mbps Downlink CIR and 1Mbps Uplink CIR. The Downlink CIR shall comprise Class B Near Real Time and the Uplink CIR shall comprise Class D Best Effort, as set out below. The Contracting QP may subsequently from time to time, increase or decrease the number of block(s) of 100Mbps Downlink CIR and 1Mbps Uplink CIR, up to a maximum aggregate of Downlink CIR of 10Gbps/Uplink CIR of 100Mbps and no less than a minimum aggregate of Downlink CIR of 100Mbps/Uplink CIR of 1 Mbps. Such increase or decrease shall constitute a Modification for which the Contracting QP shall be required to submit an Order pursuant to and in accordance with the General Service Terms and Conditions. The table below sets out the performance parameters of each Class of Service: Class Of Service Jitter Latency Packet Loss 4.3 The Contracting QP may only place an Order for an IP Unicast Connection if there is an active IP Multicast Connection to the same OpenNet CO. 4.4 When placing an Order for an IP Unicast Connection, the Contracting QP shall be required to: (a) Specify one (1) Service Port ID of the QP-EVPL Service Port and the OpenNet CO within Nucleus Connect’s Aggregation Network. (b) Specify the following Network protocol options: (i) Layer 2 VLAN (IEEE 802.1q and IEEE Q-in-Q); (ii) either IPv4 or IPv6; and (iii) either static routing or dynamic routing, provided that the availability of sub-paragraphs (ii) and (iii) above are subject to the Contracting QP having taken up and completed Nucleus Connect’s L3 Virtual Routing Domain Setup Service. The Contracting QP may place Order for multiple IP Unicast Connection(s) from the same OpenNet CO to same or different NC CO(s). The routing of traffic for the IP Unicast Connection(s) will be based on the above Network protocol chosen by the Contracting QP. (c) Subscribe to one or more block(s) of 250Mbps Downlink CIR and 30Mbps Uplink CIR. The Class of Service shall be Class B Near Real Time for both Downlink and Uplink CIR. The Contracting QP may subsequently from time to time, increase or decrease the number of block(s) of 250Mbps Downlink CIR and 30Mbps Uplink CIR, up to a maximum aggregate of Downlink CIR of 10Gbps. Such increase or decrease shall constitute a Modification for which the Contracting QP shall be required to submit an Order pursuant to and in accordance with the General Service Terms and Conditions. The table below sets out the performance parameters of Class B Class of Service: Class Of Service Jitter Latency Packet Loss Class B Near Real Time 0.5ms 3ms 0.1% 4.5 If the Contracting QP injects traffic into any IP Multicast Connection (or as the case may be, IP Unicast Connection) which exceeds the CIR purchased for such IP Multicast Connection pursuant to paragraph 4.2(c) or 4.4(c), the excess traffic will not be delivered. 4.4 4.6 The Contracting QP must adhere to Nucleus Connect’s QoS tagging scheme when sending or receiving data traffic through any IP Multicast Connection (or as the case may be, IP Unicast Connection) from the relevant Service Port(s). Such QoS tagging scheme requires the use of priority bit value 4 for Class B and priority bit value 1 for Class D. 4.5 4.7 The Contracting QP must procure and maintain, at its own cost, any equipment or software needed to receive or use and for the testing and commissioning of the IP Multicast Connection(s) and (if applicable) IP Unicast Connection(s). 4.6 4.8 In the event that Nucleus Connect accepts an Order for IP Multicast Connection submitted by the Contracting QP in accordance with the General Service Terms and Conditions, Nucleus Connect will in relation to such accepted Order create VRF (Virtual Router Forwarding) and mVPN (multi-cast VPN).

Appears in 1 contract

Samples: Interconnection Offer (Ico) Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!