The quality of service and guide is a really good guide to use for both study as well as for real world
applications.
It has, as an example, recommendations for classification and marketing.
So as an example, voice traffic should use an IP precedence of five a per hop behaviour or FB, which
is similar in concept to DHCP of F and DHCP of 46 a per hop behaviour essentially is a class.
So what class of traffic will the traffic be put into and how will it be treated on a per hop behaviour?
In other words, by each node in a network, how will your routers and switches treat the traffic?
The physical marking would be 46, so that's the DHCP.
And at layer two, your costs in your editor, the one Q header would be set to five and the MPLS experimental
bits will be set to five as well.
Call signalling.
So a protocol such as CIP or HDD three may use an IP precedence of three per hop behaviour would be
either a F 31 or KES three and the DHCP would be either 26 or 24.
That's because there are differences in the way that phones mark traffic depending on how old they are.
Bulk data, as an example, would have an IP precedence of one per hop behavior of AF 11, DCP of ten
and a cost or experimental value of one.
There are different ways to create classes depending on how close you are to the edge of the network.
If you're at the edge of the network, in other words.
You write here where your pieces and phones are connecting to the network.
You may use multiple classes such as the quality of service baseline model, but in a lot of cases as
you get closer and closer to the core.
So in a core MPLS network as an example, they'll end up only having four or five classes.
They will aggregate traffic classes into fewer classes as you get closer to the core of the network.