ZyXEL Communications CellPipe 7130 RG User Manual page 234

Chapter 16 Quality of Service (QoS)
IEEE 802.1Q Tag
The IEEE 802.1Q standard defines an explicit VLAN tag in the MAC header to
identify the VLAN membership of a frame across bridges. A VLAN tag includes the
12-bit VLAN ID and 3-bit user priority. The VLAN ID associates a frame with a
specific VLAN and provides the information that devices need to process the frame
across the network.
IEEE 802.1p specifies the user priority field and defines up to eight separate traffic
types. The following table describes the traffic types defined in the IEEE 802.1d
standard (which incorporates the 802.1p).
Table 76 IEEE 802.1p Priority Level and Traffic Type
PRIORITY
LEVEL
Level 7
Level 6
Level 5
Level 4
Level 3
Level 2
Level 1
Level 0
DiffServ
QoS is used to prioritize source-to-destination traffic flows. All packets in the flow
are given the same priority. You can use CoS (class of service) to give different
priorities to different packet types.
DiffServ (Differentiated Services) is a class of service (CoS) model that marks
packets so that they receive specific per-hop treatment at DiffServ-compliant
network devices along the route based on the application types and traffic flow.
Packets are marked with DiffServ Code Points (DSCPs) indicating the level of
service desired. This allows the intermediary DiffServ-compliant network devices
to handle the packets differently depending on the code points without the need to
negotiate paths or remember state information for every flow. In addition,
applications do not have to request a particular service or give advanced notice of
where the traffic is going.
234
TRAFFIC TYPE
Typically used for network control traffic such as router configuration
messages.
Typically used for voice traffic that is especially sensitive to jitter (jitter is the
variations in delay).
Typically used for video that consumes high bandwidth and is sensitive to
jitter.
Typically used for controlled load, latency-sensitive traffic such as SNA
(Systems Network Architecture) transactions.
Typically used for "excellent effort" or better than best effort and would
include important business traffic that can tolerate some delay.
This is for "spare bandwidth".
This is typically used for non-critical "background" traffic such as bulk
transfers that are allowed but that should not affect other applications and
users.
Typically used for best-effort traffic.
CellPipe 7130 RG User's Guide