Verizon Private IP Enhanced Traffic Management offers six IP classes of service [also known as Quality of service (QoS)] under the Enhanced Traffic Management service model:
Voice/Real Time Data (EF):
Traffic must conform to the subscribed EF CAR (Committed Access Rate) at the ingress of the Private IP network for real-time traffic sent into the Private IP network. Real-Time traffic exceeding this subscribed committed access rate at ingress will be discarded by the Verizon Private IP router. The Verizon Private IP router will discard Real-Time traffic exceeding this subscribed committed access rate at ingress.
Verizon does not allow bursting of Real-Time traffic in order to provide a controlled jitter environment for this traffic. To be recognized as Voice or Real-Time traffic by the Private IP network, the customer must send packets with the appropriate IP Type of Service (TOS) settings, which is either Expedited Forwarding (EF) or CS5 for this class of service.
Voice/Real-Time traffic traveling from the Verizon Private IP Provider Edge (PE) router towards the Customer Edge (CE), otherwise referred to as egress traffic, must adhere to EF priority percent associated with the PE egress QoS profile that is chosen by you for the port. Verizon offers 15 egress QoS profiles capable of supporting up to 50% of the port for Real-time traffic and 15 Real-Time centric profiles capable of supporting up to 90% of the port for Real-time traffic.
Video/Priority Data (AF4)
Traffic is not regulated at the ingress of the Private IP network and will be able to burst to full port speed if bandwidth is available on your port, and based on the bursting capability defined in your outbound egress QoS policy configured on the CE router. To be recognized as Priority Data or Video traffic by the Private IP network, the customer must send packets with the appropriate IP TOS settings, which is AF41, AF42, AF43, or CS4 for this class of service. Additionally, when using DiffServ, customers may further designate traffic into Priority Data High/Low levels.
At egress, Verizon has configured Class-Based Weighted Fair Queuing (CBWFQ) to prioritize data and Weighted Random Early Discard (WRED) for congestion control in this class of service. Traffic marked as Video/Priority Data will use a reserved minimum percentage of the bandwidth remaining that is not being utilized by the Real-Time CoS traffic based on the Egress profile template chosen for the port. Traffic marked Priority Data High (AF41 and CS4) will be delivered in a higher ratio than Priority Data Low (AF42 and AF43) as the queue approaches a congested state based on WRED configuration within the PE router.
Mission Critical Data (AF3)
Traffic is not regulated at the ingress of the Private IP network and will be able to burst to full port speed if bandwidth is available on your port, and based on the bursting capability defined in your outbound egress QoS policy configured on the CE router. To be recognized as Mission Critical Data traffic by the Private IP network, the customer must send packets with the appropriate IP TOS settings, which are AF31, AF32, AF33, and CS3 for this class of service.
Additionally, when using DiffServ, you may further designate traffic into Mission-Critical High/Low levels. The Private IP network is designed to automatically recognize Differentiated Services Code Point (DSCP) Values 48 / IP Prec 6 / CSC 6 and DSCP Value 56/ IP Prec 7 / CSC 6 as part of the Mission Critical Data IP Class of Service. These DSCP values 48 and 56 represent Network Control and Internetwork Control Traffic (LMI, Routing Updates, Routing Keep Alives, etc.).
At egress, Verizon has configured CBWFQ to prioritize data WRED for congestion control in this class of service. Traffic marked as Mission Critical Data will use a reserved minimum percentage of the bandwidth remaining that is not being utilized by the Real-Time Class of Service (CoS) traffic based on the Egress profile template chosen for the port. Traffic marked Mission-Critical High (AF31 and CS3) will be delivered in a higher ratio than Mission-Critical Low (AF32 and AF33) as the queue approaches a congested state based on WRED configuration within the Provider Edge (PE) router.
Business Data (AF2)
Traffic is not regulated at the ingress of the Private IP network and will be able to burst to full port speed if bandwidth is available on your port, and based on the bursting capability defined in your outbound egress QoS policy configured on the Customer Edge (CE) router. To be recognized as Business Data, traffic by the Private IP network, you must send packets with the appropriate IP TOS settings, which are AF21, AF22, AF23, and CS2 for this Class of Service (CoS).
At egress, Verizon has configured CBWFQ to prioritize data WRED for congestion control in this class. Traffic marked as Business Data will use a reserved minimum percentage of the bandwidth remaining that is not being utilized by the Real-Time CoS traffic based on the Egress profile template chosen for the port. Traffic marked Business Data High (AF21 and CS2) will be delivered in a higher ratio than Business Data Low (AF22 and AF23) as the queue approaches a congested state based on WRED configuration within the PE router.
General Data (AF1)
Traffic is not regulated at the ingress of the Private IP network and will be able to burst to full port speed if bandwidth is available, and based on the bursting capability defined in your outbound egress Quality of Service (QoS) policy configured on the CE router. To be recognized as General Data traffic by the Private IP network, you must send packets with the appropriate IP TOS settings, which are AF11, AF12, AF13, and CS1 for this class of service.
At egress, Verizon has configured CBWFQ to prioritize data WRED for congestion control in this class. Traffic marked as General Data will use a reserved minimum percentage of the bandwidth that is not being utilized by the Real-Time Class of Service (CoS) traffic based on the Egress profile template chosen for the port. Traffic marked General Data High (AF11 and CS1) will be delivered in a higher ratio than General Data Low (AF12 and AF13) as the queue approaches a congested state based on Weighted Random Early Detection (WRED) configuration within the PE router.
Default Data (BE)
Traffic is not regulated at the ingress of the Private IP network and will be able to burst to full port speed if bandwidth is available, and based on the bursting capability defined in your outbound egress QoS policy configured on the CE router. All traffic not marked with the appropriate IP Type Of Service (TOS) Settings defined by the Voice/Real Time, Video/Priority Data, Mission Critical Data, Business Data, or General Data IP Classes of Service will be recognized by the Private IP network as the Default Data IP CoS. Traffic can also be specifically assigned as Default Data, if the customer sends packets with the appropriate IP TOS settings, which is commonly defined as DSCP 0, but can be any other Differentiated Services Code Point (DSCP) marking not defined in the other five Private IP classes of service.
At egress, Verizon has configured Class-Based Weighted Fair Queueing (CBWFQ) to prioritize data WRED for congestion control in this class. Traffic marked as Default Data will use a reserved minimum percentage of the bandwidth that is not being utilized by the Real-Time CoS traffic based on the Egress profile template chosen for the port.
The Verizon Private IP network supports 24 egress profile templates available to Private IP customers on a per port basis. The Egress Profile templates do not change the cost of the Private IP service.