Градбените блокови на QoS

Дизајн на компјутерски мрежи

МОДЕЛИ ЗА ИМПЛЕМЕНТАЦИЈА
НА QOS
 Three Models for Quality of Service
• Best-Effort: No QoS is applied to packets.
• IntServ (Integrated service): Applications signal to
the network that they require special QoS.
• DiffServ (Differentiated service): The network
recognizes classes that require special QoS.
 Best-Effort Model
• Internet initially based on a best-effort packet
delivery service
• The default mode for all traffic
• No differentiation between types of traffic
• Like using standard mail
– It will get there when it gets there
• + Benefits:
– Highly scalable
– No special mechanisms required
• – Drawbacks:
– No service guarantees
– No service differentiation
 IntServ Model - hard QoS
• Some applications have special bandwidth or
delay requirements or both
• IntServ introduced to guarantee a predictable
behavior of the network for these applications
• Guaranteed delivery: no other traffic can use
reserved bandwidth
• Like having your own private courier plane
– It will be there by 10:30 a.m.
 IntServ Model (Cont.)
• Provides multiple service
levels
– Connection-oriented approach
from telephony network
• Requests specific kind of
service from the network
before sending data
• Uses RSVP to reserve network
resources
• Uses intelligent queuing
mechanisms
• End to end
 IntServ Model (Cont.)

• RSVP QoS services

– Guaranteed-rate service
– Controlled-load service
• RSVP provides policy to QoS mechanisms
 IntServ Model (Cont.)
• + Benefits:
– Explicit resource admission control (end to end)
– Per-request policy admission control (may reject new
RSVP sessions if limit is reached)
– RSVP informs network devices of flow parameters (IP
address and port numbers)
• – Drawbacks:
– Continuous signaling because of stateful architecture
– Flow-based approach not scalable to large
implementations such as the public Internet (can be
made more scalable when combined with elements
of the DiffServ model)
 DiffServ Model - soft QoS
• Network traffic identified by class
• “almost guaranteed”
• Network QoS policy enforces differentiated
treatment of traffic classes
• You choose level of service for each traffic class
• Like using a package delivery service
– Do you want overnight delivery?
– Do you want two-day air delivery?
– Do you want three- to seven day
ground delivery?
 DiffServ Model (Cont.)
• + Benefits:
– Highly scalable
– Many levels of quality possible
• – Drawbacks:
– No absolute service guarantee
– Complex mechanisms
 Summary
• There are three different models for providing QoS:
Best- Effort, IntServ, and DiffServ.
• While the Best-Effort model is highly scalable, it has
no provision for differentiating among types of
network traffic and, as a result, does not provide
QoS.
• The Integrated Services model offers absolute QoS
guarantees by explicitly reserving bandwidth, but is
not scalable.
• The Differentiated Services model provides the
ability to classify network traffic and offer many
levels of QoS while being highly scalable.
МОДЕЛ НА ИНТЕГРИРАНИ
СЕРВИСИ
 IntServ Model
• IntServ provides end-to-end
QoS service for applications.
• RSVP mechanism is used to
provision end-to-end QoS
treatment.
• CAC (call admission control) is
used through the network to
ensure resource availability.
• The network participates by
either reserving or not
reserving network resources
 IntServ Model (Cont.)
• RSVP supports the following messages:
– PATH
– RESV
– Error and Confirmation
– Teardown (remove path and reservation state)
 IntServ Model (Cont.)
• There are three types of QoS services offered by
RSVP:
– Best Effort
– Guaranteed rate (delay)
– Controlled load (least possible interruption from
other traffic flows)
RSVP Components
RSVP Interface Queuing
IntServ and DiffServ Integration
 Summary
• RSVP provides end-to-end QoS.
• RSVP signaling uses the control plane and is used
for Call Admission Control. Reservation data flow
uses the data plane in which WFQ and WRED is
used.
• RSVP integrates with DiffServ networks, in which
RSVP is used for flow admission control.
• If a reservation does not meet specific QoS
requests, the flow is sent Best-Effort.
МОДЕЛ НА ДИФЕРЕНЦИРАНИ
СЕРВИСИ
 Differentiated Services Model
• The Differentiated Services model describes
services associated with traffic classes.
• Complex traffic classification and conditioning is
performed at the network edge, resulting in a
per-packet DSCP (differentiated service code
point).
• No per-flow state in the core.
• The core only performs simple “per-hop
behaviors” on traffic aggregates.
• The goal is scalability.
 DSCP Encoding

• DiffServ field: The IP version 4 header ToS octet

or the IPv6 traffic class octet, when interpreted in
conformance with the definition given in RFC
2474
• DSCP: The first six bits of the DiffServ field, used
to select a PHB (forwarding and queuing method)
 Per-Hop Behaviors

DSCP selects PHB throughout the network.

• Default PHB (FIFO, tail drop)
• EF Expedited Forwarding (low delay)
• AF Assured Forwarding
• Class-Selector (IP Precedence) PHB
 Per-Hop Behaviors (Cont.)

• EF PHB
– Ensures a minimum departure rate
– Guarantees bandwidth (The class is guaranteed an amount of
bandwidth with prioritized forwarding.)
– Polices bandwidth (The class is not allowed to exceed the
guaranteed amount; excess traffic is dropped.)
• DSCP value “101110”: looks like IP Precedence 5 to non-
DiffServ compliant devices
– Bits 5 to 7: “101” = 5 (Same three bits used for IP Precedence)
– Bits 3 to 4: “11” = no drop probability high
– Bit 2: Just “0”
 Per-Hop Behaviors (Cont.)

• AF PHB:
– Guarantees certain amount of bandwidth
– Allows access to extra bandwidth, if available
• Four standard classes (af1, af2, af3, and af4)
• DSCP value range: “aaadd0”
– Where “aaa” is a binary value of the class
– Where “dd” is drop probability
 Per-Hop Behaviors (Cont.)

• Each AF class uses three DSCP values.

• Each AF class is independently forwarded with its
guaranteed bandwidth.
• Congestion avoidance is used within each class to
prevent congestion within the class.
 Per-Hop Behaviors (Cont.)
• A DiffServ node must allocate a configurable,
minimum amount of forwarding resources (buffer
space and bandwidth) per AF class.
• Excess resources may be allocated between nonidle
classes. The manner must be specified.
• Reordering of IP packets of the same flow is not
allowed if they belong to the same AF class.
• Should congestion occur between classes, the traffic
in the higher class is given priority
• If congestion occurs within a class, the packets with
the higher drop precedence are discarded first
 Backward Compatibility Using the
Class Selector

• Class-Selector “xxx000” DSCP

• Compatibility with current IP Precedence usage (RFC
1812) = maps IP Precedence to DSCP
• Differentiates probability of timely forwarding
(xyz000) >= (abc000) if xyz > abc
– If a packet has DSCP = “011000,” it has a greater
probability of timely forwarding than a packet with DSCP
= “001000.”
 Summary
• The DiffServ model describes services associated with
traffic classes.
• Complex traffic classification and conditioning is
performed at the network edge, resulting in a per-packet
DSCP.
• A per-hop behavior is an externally observable forwarding
behavior applied at a DiffServ-compliant node to a DiffServ
behavior aggregate.
• The EF PHB guarantees and polices bandwidth while
ensuring a minimum departure rate.
• The AF PHB guarantees bandwidth while providing four
classes, each having three DSCP values.
• The DSCP is backward compatible with IP Precedence and
Class-Selector Code Point.
QOS МЕХАНИЗМИ
 QoS Mechanisms
• Classification: Each class-oriented QoS mechanism has to
support some type of classification.
• Marking: Used to mark packets based on classification,
metering, or both.
• Congestion management: Each interface must have a
queuing mechanism to prioritize transmission of packets.
• Congestion avoidance: Used to drop packets early to avoid
congestion later in the network.
• Policing and shaping: Used to enforce a rate limit based on
the metering (excess traffic is either dropped, marked, or
delayed).
• Link Efficiency: Used to improve bandwidth efficiency
through compression, link fragmentation, and interleaving
 Classification

• Classification is the identifying and splitting of traffic

into different classes.
• Traffic can be classed by various means (source IP,
dest IP, IP precedence), including the DSCP.
• Modular QoS CLI allows classification to be
implemented separately from policy.
 Marking

• Marking, also known as coloring, marks each

packet as a member of a network class so that
the packet class can be quickly recognized
throughout the rest of the network.
 Congestion Management

• Congestion management uses the marking on each packet

to determine in which queue to place packets.
• Congestion management uses sophisticated queuing
technologies, such as WFQ and LLQ, to ensure that time-
sensitive packets such as voice are transmitted first.
 Congestion Avoidance

• Congestion avoidance may randomly drop packets from selected queues

when previously defined limits are reached.
• By dropping packets early, congestion avoidance helps prevent
bottlenecks downstream in the network.
• Congestion avoidance technologies include random early detection and
weighted random early detection
• Implemented on output interface when, for example, LAN feeds slower
WAN link
 Policing
• Policing drops or marks packets when a predefined limit is
reached.
• Example, policing by ISP to throttle high-speed inflow that
for customer that was in excess of the service agreement
 Shaping
• Shaping queues packets when a predefined limit
is reached.
 Compression
• Header compression can dramatically reduce the overhead associated with
voice transport
• Usually used for RTP packets (network transport protocol used for carrying
converged traffic-audio, video…)
• Typical voice packet, 20B payload, 20B IP header, 8B UDP header and 12B RTP
header
• Usually used on WAN links
 Link Fragmentation and Interleaving

• Without link fragmentation and interleaving, time-sensitive

voice traffic can be delayed behind long, non-time-sensitive
data packets.
• Link fragmentation breaks long data packets apart and
interleaves time-sensitive packets so that the time-sensitive
packets are not delayed.
• Usually used on WAN links, reduces waiting for the serialization
delay of the large packets
Applying QoS to Input and
Output Interfaces
 Summary
• Different mechanisms can be used to implement QoS in a network:
classification, marking, congestion management, congestion avoidance,
policing, shaping, and link efficiency.
• The first step is always to identify classes of traffic at the input interface of
every QoSaware device so that the appropriate QoS treatment can be applied
to the different traffic types.
• Marking involves marking each packet as a member of a class so that devices
throughout the rest of the network can quickly recognize the packet class.
Marking is performed as close to the network edge as possible.
• Congestion management is based on placing marked packets into different
output interface queues based on their class; these queues are given different
treatment based on their associated queuing algorithm.
• Congestion avoidance mechanisms help prevent link congestion by dropping
lower priority traffic at the output interface before it becomes a problem.
• Traffic conditioners such as policers and shapers are used to limit the maximum
rate of traffic sent or received on an interface.
• Bandwidth efficiency on WAN links can be improved through link efficiency
mechanisms such as compression and link fragmentation and interleaving.
• QoS mechanisms may be applied at the input interface, output interface, or
both, depending on the particular QoS mechanism.
QOS ВО ЖИВОТОТ НА ЕДЕН ПАКЕТ
Overview
Life of a High-Priority VoIP Packet
Life of a High-Priority VoIP Packet
(Cont.)
Life of a High-Priority VoIP Packet
(Cont.)
Life of a High-Priority VoIP Packet
(Cont.)
Life of a High-Priority VoIP Packet
(Cont.)
Life of a High-Priority VoIP Packet
(Cont.)
Life of a High-Priority VoIP Packet
(Cont.)
Life of a High-Priority VoIP Packet
(Cont.)
Life of a High-Priority VoIP Packet
(Cont.)
Life of a Low-Priority FTP Packet
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
Life of a Low-Priority FTP Packet
(Cont.)
 Summary
• High-priority and low-priority packets are treated very
differently in a network using Differentiated Services.
• The high-priority VoIP packet begins life at an IP Phone as a
CoS 5 on the LAN, which translates to DSCP 40 as the
packet hits the WAN and is given EF status in the service
provider core network.
• With a CoS 5 and a DSCP 40, the high-priority packet is
immediately transmitted by all devices as it moves through
the network.
• The low-priority FTP packet begins life as a CoS 0 packet,
which translates to DSCP 0 and Assured Forwarding 11 in
the service provider core network.
• In a busy network, the low-priority packet will wait at
every device and has a high probability of being dropped at
any of several points.
 Module Summary
• The three basic models for QoS are Best Effort, IntServ, and
DiffServ. With Best Effort, no special QoS mechanisms are
applied. With IntServ, applications signal to the network
that they require QoS. With DiffServ, the network devices
recognize the traffic classes of the packets and provide
different QoS levels.
• The Differentiated Services model is the primary model
used to implement QoS in IP networks because it is highly
scalable and offers the capability to define many different
levels of service.
• The Differentiated Services model uses a 6-bit DSCP to
mark packets so that they will be treated with different
levels of service as they traverse an IP network.
 Module Summary
• IP networks use a variety of mechanisms to
implement QoS, including classification, marking,
congestion management, congestion avoidance,
metering, traffic policing, traffic shaping, and link
efficiency.
• As packets travel through the network, each
packet is classified and marked as close to the
source as possible. The downstream devices then
apply different QoS mechanisms to the packet
based on its marking. The packets can be re-
marked along the way.