Now you could also match on other values.
So notice you could match on IP precedence.
And specify values such as zero one, two, three, four, five, six or seven.
These values also have names.
So as an example, if I specify three here and then type do show run.
Notice that shows up as three.
But I could also specify flesh.
That's also a valid way to match.
That's very similar to using Port 23 or the word telnet in an access list.
So you can either use the word or the number.
To specify the traffic that you're going to match on.
Notice we also have a cost value that we can match on, so we could specify a cost value of five.
There are many other options available here.
So match.
And let's say application.
And here we can match on specific applications such as RTP or FX 3 to 3.
We can use network based application recognition.
To match on higher level protocols rather than just matching on layer two or layer three, we could
match on higher layers of the OCI model.
We can also match MPLS values.
So we can match experimental values in the range 0 to 7.
So as an example, we could match experimental value five.
Now, once you've matched on traffic, you need to do something with it.
So you either need to prioritize it or rate it, limit it or queue it or delay it or drop it as an example.
And that's what some of the other mechanisms do on routers and switches.
Once you've classified or matched on traffic, what are you going to do with that traffic?
As an example, if you've got a first class boarding ticket, you may go to the left door.
But if you've got an economy class ticket, you go to the right door and you get a different quality
of service and a different experience based on the ticket that you hold.