Common use of SERVICE REQUIRMENTS Clause in Contracts

SERVICE REQUIRMENTS. 4.1 The Contracting QP shall place one (1) Order for each QP-EVPL Service Port. For example, if the Contracting QP wishes to take up two (2) QP-EVPL Service Ports, the Contracting QP shall submit two (2) separate Orders. 4.2 The Contracting QP acknowledges and agrees that: (a) for a QP-EVPL Service Port at the Core Layer, such QP-EVPL Service Port must be connected to a PB-EVC and/or an IP Multicast Connection; and (b) for a QP-EVPL Service Port at the Aggregation Layer, such QP-EVPL Service Port must be connected to an AG-EVC and/or an IP Multicast Connection. 4.3 When placing an Order for a QP-EVPL Service Port, the Contracting QP shall be required to: (a) Choose one (1) Service Port type which is either a 1 Gigabit Ethernet (“1GE Service Port”) or a 10 Gigabit Ethernet (“10GE Service Port”). The Symmetrical Peak Information Rate for a 1GE Service Port shall be 1Gbps and for a 10GE Service Port shall be 10Gbps. (b) Choose any of the following Network Layers: (i) Option1: Layer 2 VLAN (IEEE 802.1q and IEEE Q-in-Q) (ii) Option 2: Layer 3 IPv4 (iv) Option 4: Layer 3 IP Multicast (IGMP V2/V3) provided that the availability of Option 2 and Option 3 above are subject to the Contracting QP having taken up and completed the L3 Virtual Routing Domain Setup Service, which is an Ancillary Mandated Service provided by Nucleus Connect. (c) Choose either of the following failover mechanism and protocols (only for QP- EVPL Service Ports within the same Nucleus Connect’s CO): (i) Option 1: IEEE 802.3ad (ii) Option 2: eBGP The Contracting QP’s responsibility is to ensure that the abovementioned failover mechanism and protocols are correctly configured and dimensioned on its equipment. 4.4 The Contracting QP must adhere to Nucleus Connect’s QoS tagging scheme when sending or receiving data traffic through the QP-EVPL Service Port. Such QoS tagging scheme requires the use of priority bit value 5 for Class A, priority bit value 4 for Class B, priority bit value 2 for Class C and priority bit value 1 for Class D. (a) Where the QP-EVPL Service Port is located at a NC CO: (i) The Contracting QP must procure Patching Services from Nucleus Connect in order to connect the Contracting QP Equipment to the QP-EVPL Service Port. (ii) If the Contracting QP Equipment is not co-located at the same NC CO as the QP-EVPL Service Port, the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP-EVPL Service Port. (iii) The Contracting QP must also procure Co-location Services from Nucleus Connect to house the Contracting QP Equipment which is used to provide the transmission link. (iv) The inter End-User traffic shall be routed through the Contracting QP Equipment that is connected to the QP-EVPL Service Port. (b) Where the QP-EVPL Service Port is located at an NetLink Trust CO: (i) The Contracting QP must procure patching services from NetLink Trust in order to connect the Contracting QP Equipment to the QP- EVPL Service Port. (ii) If the Contracting QP Equipment is not co-located at the same NetLink Trust CO as the QP-EVPL Service Port, the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP- EVPL Service Port. (iii) The Contracting QP shall be responsible to house its equipment at NetLink Trust’s COs. (iv) In order for the Contracting QP to deliver its traffic to any other QP- EVPL Service Port located at a NC CO or at another NetLink Trust CO, the routing shall be by Layer 3 IP V4 or IP V6 protocol. The QP- EVPL Service Port at NC CO shall have PB-EVC connections to the relevant NetLink Trust CO. All IP traffic shall still be routed through the Contracting QP Equipment that is connected to the QP-EVPL 5.‌ CHARGES Service Port located at NC CO and/or NetLink Trust CO. The charges set out in this paragraph 5 are the rates payable by the Contracting QP on a per QP-EVPL Service Port basis.

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 QPResidential Per -End-EVPL Service PortUser Connection. For example, if the Contracting QP Contractor wishes to take up two (2) QPResidential Per- End-EVPL Service PortsUser Connections, the Contracting QP shall submit two (2) separate Orders. 4.2 The Contracting QP acknowledges and agrees that: (a) for a QP-EVPL Service Port at the Core Layer, such QP-EVPL Service Port must be connected to a PB-EVC and/or an IP Multicast Connection; and (b) for a QP-EVPL Service Port at the Aggregation Layer, such QP-EVPL Service Port must be connected to an AG-EVC and/or an IP Multicast Connection. 4.3 When placing an Order for a QPResidential Per-EVPL Service PortE nd-User Connection, the Contracting QP shall be required to: (a) Choose one (1) the Gigabit Ethernet Service Port type which is either a 1 Gigabit Ethernet (“1GE Service Port”) or a 10 Gigabit Ethernet (“10GE GE Service Port”). Each Residential Per-End-User-Connection will have a bundle of the following: (i) Symmetrical Downlink PIR 1Gbps/Uplink PIR 1Gbps, for Class D CoS; (ii) Downlink CIR of 25Mbps, for Class D CoS, and (iii) Downlink CIR of at least 20MBps, for Class B CoS. The Symmetrical Peak Information Rate for a 1GE Downlink Class B CIR will be stacked on top of the symmetrical Class D PIR. In the same Order, the Contracting QP may choose up to two additional Service Port shall Ports to be 1Gbps and for a 10GE aggregated to the same Residential Per -End-User Connection provided that all the Service Port shall be 10GbpsPorts are of the same type. (b) Choose any of the following Network Layers: (i) Option1: Layer 2 VLAN (IEEE 802.1q and IEEE Q-in-Q). Where there is more than one Service Port sharing the same Residential Per -End- User Connection, each Service Port shall have unique VLAN(s); (ii) Option 2: Layer 3 IPv4 IPv4; (iviii) Option 43: Layer 3 IP Multicast (IGMP V2/V3) IPv6, provided that the availability of Option 2 and Option 3 above are subject to the Contracting QP having taken up and completed the L3 Virtual Routing Domain Setup Service, which is an Ancillary Mandated Service Servic e provided by Nucleus Connect. (c) Choose either The table below sets out the performance parameters of each Class of Service: Class B Near Real Time 1ms 8ms 0.2% 4.3 If the following failover mechanism Contracting QP injects traffic into any Residential Per -End-User Connection which exceeds the CIR purchased for such Residential Per -End-User Connection pursuant to paragraph 4.2( a), the Contracting QP acknowledges and protocols (only for QP- EVPL Service Ports within agrees that notwithstanding that Nucleus Connect will endeavour to deliver such excess traffic, such delivery is not guaranteed. For the same Nucleus Connect’s CO): (i) Option 1: IEEE 802.3ad (ii) Option 2: eBGP The avoidance of doubt, the Contracting QP’s responsibility is QP shall not be able to ensure that inject traffic into any Residential Per-End-User Connection which exceeds the abovementioned failover mechanism and protocols are correctly configured and dimensioned on its equipmentPIR as set out in paragraph 4.2(a). 4.4 The Contracting QP must adhere to Nucleus Connect’s QoS tagging scheme when sending or receiving data traffic through any Residential Per-End-User Connection from the QP-EVPL relevant Service PortPort(s). Such QoS tagging scheme requires the use of priority bit value 5 for Class A, priority bit value 4 for Class B, priority bit value 2 for Class C and priority bit value 1 for Class D. (a) Where the QP-EVPL Service Port is located at a NC CO: (i) The Contracting QP must procure Patching Services from Nucleus Connect in order to connect the Contracting QP Equipment to the QP-EVPL Service Port. (ii) 4.5 If the Contracting QP Equipment is not corequires Nucleus Connect to perform QoS tagging on behalf of the Contracting QP, such tagging shall be on a one C-located at VLAN and one CoS per Service Port basis. 4.6 In relation to any Residential Per-End-User Connection taken up by the same NC CO as the Contracting QP-EVPL Service Port, if the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP-EVPL Service Port.wishes to: (iiia) The Contracting QP must also procure Co-location Services from Nucleus Connect to house the Contracting QP Equipment which is used to provide the transmission link. (iv) The inter End-User traffic shall be routed through the Contracting QP Equipment that is connected to the QP-EVPL Service Port.Intentionally Deleted) (b) Where add or reduce the QPnumber of Service Ports aggregated to such Residential Per-EVPL End-User Connection, provided that the number of Service Port is located Ports sharing such Residential Per-End-User Connection shall not exceed three (3) at an NetLink Trust CO: (i) The Contracting QP must procure patching services from NetLink Trust in order to connect all times, each such event shall constitute a Modification for which the Contracting QP Equipment to the QP- EVPL Service Port. (ii) If the Contracting QP Equipment is not co-located at the same NetLink Trust CO as the QP-EVPL Service Port, the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP- EVPL Service Port. (iii) The Contracting QP shall be responsible required to house its equipment at NetLink Trust’s COssubmit an Order pursuant to and in accordance with the General Service Terms and Conditions. (iv) In order for the Contracting QP to deliver its traffic to any other QP- EVPL Service Port located at a NC CO or at another NetLink Trust CO, the routing shall be by Layer 3 IP V4 or IP V6 protocol. The QP- EVPL Service Port at NC CO shall have PB-EVC connections to the relevant NetLink Trust CO. All IP traffic shall still be routed through the Contracting QP Equipment that is connected to the QP-EVPL 5.‌ CHARGES Service Port located at NC CO and/or NetLink Trust CO. The charges set out in this paragraph 5 are the rates payable by the Contracting QP on a per QP-EVPL Service Port basis.

Appears in 1 contract

Samples: Interconnection Offer (Ico) Agreement

SERVICE REQUIRMENTS. 4.1 The Contracting QP shall place one (1) Order for each QPResidential Per -End-EVPL Service PortUser Connection. For example, if the Contracting QP Contractor wishes to take up two (2) QPResidential Per- End-EVPL Service PortsUser Connections, the Contracting QP shall submit two (2) separate Orders. 4.2 The Contracting QP acknowledges and agrees that: (a) for a QP-EVPL Service Port at the Core Layer, such QP-EVPL Service Port must be connected to a PB-EVC and/or an IP Multicast Connection; and (b) for a QP-EVPL Service Port at the Aggregation Layer, such QP-EVPL Service Port must be connected to an AG-EVC and/or an IP Multicast Connection. 4.3 When placing an Order for a QPResidential Per-EVPL Service PortE nd-User Connection, the Contracting QP shall be required to: (a) Choose one (1) the Gigabit Ethernet Service Port type which is either a 1 Gigabit Ethernet (“1GE Service Port”) or a 10 Gigabit Ethernet (“10GE GE Service Port”). Each Residential Per-End-User-Connection will have a bundle of the following: (i) Symmetrical Downlink PIR 1Gbps/Uplink PIR 1Gbps, for Class D CoS; (ii) Downlink CIR of 25Mbps, for Class D CoS, and (iii) Downlink CIR of at least 20MBps, for Class B CoS. The Symmetrical Peak Information Rate for a 1GE Downlink Class B CIR will be stacked on top of the symmetrical Class D PIR. In the same Order, the Contracting QP may choose up to two additional Service Port shall Ports to be 1Gbps and for a 10GE aggregated to the same Residential Per -End-User Connection provided that all the Service Port shall be 10GbpsPorts are of the same type. (b) Choose any of the following Network Layers: (i) Option1: Layer 2 VLAN (IEEE 802.1q and IEEE Q-in-Q). Where there is more than one Service Port sharing the same Residential Per -End- User Connection, each Service Port shall have unique VLAN(s); (ii) Option 2: Layer 3 IPv4 IPv4; (iviii) Option 43: Layer 3 IP Multicast (IGMP V2/V3) IPv6, provided that the availability of Option 2 and Option 3 above are subject to the Contracting QP having taken up and completed the L3 Virtual Routing Domain Setup Service, which is an Ancillary Mandated Service Servic e provided by Nucleus Connect. (c) Choose either The table below sets out the performance parameters of each Class of Service: Class D Best Effort Best Effort 30ms Best Effort 4.3 If the following failover mechanism Contracting QP injects traffic into any Residential Per -End-User Connection which exceeds the CIR purchased for such Residential Per -End-User Connection pursuant to paragraph 4.2( a), the Contracting QP acknowledges and protocols (only for QP- EVPL Service Ports within agrees that notwithstanding that Nucleus Connect will endeavour to deliver such excess traffic, such delivery is not guaranteed. For the same Nucleus Connect’s CO): (i) Option 1: IEEE 802.3ad (ii) Option 2: eBGP The avoidance of doubt, the Contracting QP’s responsibility is QP shall not be able to ensure that inject traffic into any Residential Per-End-User Connection which exceeds the abovementioned failover mechanism and protocols are correctly configured and dimensioned on its equipmentPIR as set out in paragraph 4.2(a). 4.4 The Contracting QP must adhere to Nucleus Connect’s QoS tagging scheme when sending or receiving data traffic through any Residential Per-End-User Connection from the QP-EVPL relevant Service PortPort(s). Such QoS tagging scheme requires the use of priority bit value 5 for Class A, priority bit value 4 for Class B, priority bit value 2 for Class C and priority bit value 1 for Class D. (a) Where the QP-EVPL Service Port is located at a NC CO: (i) The Contracting QP must procure Patching Services from Nucleus Connect in order to connect the Contracting QP Equipment to the QP-EVPL Service Port. (ii) 4.5 If the Contracting QP Equipment is not corequires Nucleus Connect to perform QoS tagging on behalf of the Contracting QP, such tagging shall be on a one C-located at VLAN and one CoS per Service Port basis. 4.6 In relation to any Residential Per-End-User Connection taken up by the same NC CO as the Contracting QP-EVPL Service Port, if the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP-EVPL Service Port.wishes to: (iiia) The Contracting QP must also procure Co-location Services from Nucleus Connect to house the Contracting QP Equipment which is used to provide the transmission link. (iv) The inter End-User traffic shall be routed through the Contracting QP Equipment that is connected to the QP-EVPL Service Port.Intentionally Deleted) (b) Where add or reduce the QPnumber of Service Ports aggregated to such Residential Per-EVPL End-User Connection, provided that the number of Service Port is located Ports sharing such Residential Per-End-User Connection shall not exceed three (3) at an NetLink Trust CO: (i) The Contracting QP must procure patching services from NetLink Trust in order to connect all times, each such event shall constitute a Modification for which the Contracting QP Equipment to the QP- EVPL Service Port. (ii) If the Contracting QP Equipment is not co-located at the same NetLink Trust CO as the QP-EVPL Service Port, the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP- EVPL Service Port. (iii) The Contracting QP shall be responsible required to house its equipment at NetLink Trust’s COssubmit an Order pursuant to and in accordance with the General Service Terms and Conditions. (iv) In order for the Contracting QP to deliver its traffic to any other QP- EVPL Service Port located at a NC CO or at another NetLink Trust CO, the routing shall be by Layer 3 IP V4 or IP V6 protocol. The QP- EVPL Service Port at NC CO shall have PB-EVC connections to the relevant NetLink Trust CO. All IP traffic shall still be routed through the Contracting QP Equipment that is connected to the QP-EVPL 5.‌ CHARGES Service Port located at NC CO and/or NetLink Trust CO. The charges set out in this paragraph 5 are the rates payable by the Contracting QP on a per QP-EVPL Service Port basis.

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 QP-EVPL Service Port. For example, if the Contracting QP wishes to take up two (2) QP-EVPL Service Ports, the Contracting QP shall submit two (2) separate Orders. 4.2 The Contracting QP acknowledges and agrees that: (a) for a QP-EVPL Service Port at the Core Layer, such QP-EVPL Service Port must be connected to a PB-EVC and/or an IP Multicast Connection; and (b) for a QP-EVPL Service Port at the Aggregation Layer, such QP-EVPL Service Port must be connected to an AG-EVC and/or an IP Multicast Connection. 4.3 When placing an Order for a QP-EVPL Service Port, the Contracting QP shall be required to: (a) Choose one (1) Service Port type which is either a 1 Gigabit Ethernet (“1GE Service Port”) or a 10 Gigabit Ethernet (“10GE Service Port”). The Symmetrical Peak Information Rate for a 1GE Service Port shall be 1Gbps and for a 10GE Service Port shall be 10Gbps. (b) Choose any of the following Network Layers: (i) Option1: Layer 2 VLAN (IEEE 802.1q and IEEE Q-in-Q) (ii) Option 2: Layer 3 IPv4 Xxxxx 0 XXx0 (iv) Option 4: Layer 3 IP Multicast (IGMP V2/V3) provided that the availability of Option 2 and Option 3 above are subject to the Contracting QP having taken up and completed the L3 Virtual Routing Domain Setup Service, which is an Ancillary Mandated Service provided by Nucleus Connect. (c) Choose either of the following failover mechanism and protocols (only for QP- EVPL Service Ports within the same Nucleus Connect’s CO): (i) Option 1: IEEE 802.3ad (ii) Option 2: eBGP The Contracting QP’s responsibility is to ensure that the abovementioned failover mechanism and protocols are correctly configured and dimensioned on its equipment. 4.4 The Contracting QP must adhere to Nucleus Connect’s QoS tagging scheme when sending or receiving data traffic through the QP-EVPL Service Port. Such QoS tagging scheme requires the use of priority bit value 5 for Class A, priority bit value 4 for Class B, priority bit value 2 for Class C and priority bit value 1 for Class D. (a) Where the QP-EVPL Service Port is located at a NC CO: (i) The Contracting QP must procure Patching Services from Nucleus Connect in order to connect the Contracting QP Equipment to the QP-EVPL Service Port. (ii) If the Contracting QP Equipment is not co-located at the same NC CO as the QP-EVPL Service Port, the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP-EVPL Service Port. (iii) The Contracting QP must also procure Co-location Services from Nucleus Connect to house the Contracting QP Equipment which is used to provide the transmission link. (iv) The inter End-User traffic shall be routed through the Contracting QP Equipment that is connected to the QP-EVPL Service Port. (b) Where the QP-EVPL Service Port is located at an NetLink Trust CO: (i) The Contracting QP must procure patching services from NetLink Trust in order to connect the Contracting QP Equipment to the QP- EVPL Service Port. (ii) If the Contracting QP Equipment is not co-located at the same NetLink Trust CO as the QP-EVPL Service Port, the Contracting QP must ensure that its equipment/transmission link used to connect to the QP-EVPL Service Port is able to interface properly with the QP- EVPL Service Port. (iii) The Contracting QP shall be responsible to house its equipment at NetLink Trust’s COs. (iv) In order for the Contracting QP to deliver its traffic to any other QP- EVPL Service Port located at a NC CO or at another NetLink Trust CO, the routing shall be by Layer 3 IP V4 or IP V6 protocol. The QP- EVPL Service Port at NC CO shall have PB-EVC connections to the relevant NetLink Trust CO. All IP traffic shall still be routed through the Contracting QP Equipment that is connected to the QP-EVPL 5.‌ 5. CHARGES Service Port located at NC CO and/or NetLink Trust CO. The charges set out in this paragraph 5 are the rates payable by the Contracting QP on a per QP-EVPL Service Port basis.

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!