Class 2
Class 2
CLASS 2
QOS MECHANISMS
NETWORK
CONGESTION
Network Congestion
• Definition: Congestion is a state of a network component where it
experiences more input traffic than it is able to handle with the
available (shared) resources.
• Network nodes handle congestion differently, depending on the OSI
layer it is associated with.
Network Congestion
Congestion in Layer 3
Classic ports:
• 80 HTTP - Nature: web
• 443 SSL - Nature: playback/browsing (streaming)
• 22 SSH - Nature: interactive
• 5060 VoIP - Nature: voice calls
Is there a problem with this approach?
Classification
Header Inspection
4 3 3 2 2 1 1
Rank of precedence 4 3 2 2 1 1
0 000 Routine 3
1 001 Priority
2 010 Immediate
3 011 Flash
4 100 Flash Override 4 3 2 2 1 1
5 101 Critic/Critical
6 110 Internetwork Control
7 111 Network Control
Marking
IPv4 – IP Precedence: First design, RFC791 (1981)
Each type of service is implemented as the same “behavior” throughout every router in the data flow.
Marking
IPv4 – Differentiated Services (DiffServ)
10%
DSCP name: EF
DSCP binary: (101 110)B
DSCP decimal: (46)D
How can we guarantee that the user does not get more
throughput than it is actually paying for?
Policing
Definition: Policing is a QoS mechanism used to limit throughput of a
given traffic flow by performing one of the following actions to arriving
packets:
• Allow packet to pass
• Drop the packet
• Re-mark the packet with different priority
Policing
• In Policing, packets may be categorized in terms of conformity to the
traffic contract, i.e.,
• Conforming: OK rate
• Exceeding: using the excess burst capacity (more about it later)
• Violating: higher rate than allowed
• Categories are optional and must be configured
• Example of actions are:
• Conforming – pass
• Exceeding – lower priority [optional]
• Violating – drop
Policing
Single-Rate, Two-Color Policer (Single Bucket)