Академический Документы
Профессиональный Документы
Культура Документы
Motivation
Internet currently provides only single class of best-effort service.
No admission control and no assurances about delivery
Future real-time applications may be inelastic. Should we modify these applications to be more adaptive or should we modify the Internet to support inelastic behavior?
Lecture 22: 11/20/2001 2
Application Types
Elastic applications.
Wide range of acceptable rates, although faster is better E.g., data transfers such as FTP
Overview
Principles for QoS Integrated Services (Intserv) Differentiated Services (Diffserv) Resource ReSerVation Protocol (RSVP)
PRINCIPLE 1: Marking of packets is needed for router to distinguish between different classes; and new router policy to treat packets accordingly.
10
Summary
11
ATM QoS and Integrated services were developed based on these results.
Focus on per-flow, hard QoS. Effort was driven by perceived application needs.
In the last 5 years, the focus has shifted towards Differentiated services.
Focus is on QoS for flow aggregates, e.g., all the flows belonging to one customer.
Lecture 22: 11/20/2001 12
Overview
Motivation for QoS Integrated Services (Intserv) Differentiated Services (Diffserv) Resource ReSerVation Protocol (RSVP)
13
IETF Intserv
Focus on per-flow QoS.
Support specific applications such as video streaming. Based on mathematical guarantees.
Many concerns:
Complexity Scalability Business model Charging
14
Service interface
How does the application describe what it wants?
Packet scheduling
How does the network meet promises?
15
Service Models
Network can support traffic streams with different quality of service.
Best effort Predictive or differentiated services Strong guarantees on the level of service (real-time)
The set of services that is supported on a specific network can be viewed as a service model.
Model that can be used to select a service
E.g., cost versus performance tradeoffs
16
Service Models
Guaranteed service
Targets hard real-time applications. User specifies traffic characteristics and a service requirement. Requires admission control at each of the routers. Can mathematically guarantee bandwidth, delay, and jitter.
Controlled load.
Targets applications that can adapt to network conditions within a certain performance window. User specifies traffic characteristics and bandwidth. Requires admission control at each of the routers. Guarantee not as strong as with the guaranteed service. e.g., measurement-based admission control.
Best effort
Lecture 22: 11/20/2001 17
Service Interface
Session must first declare its QoS requirement and characterize the traffic it will send through the network R-spec: defines the QoS being requested by receiver (e.g., rate r) T-spec: defines the traffic characteristics of sender (e.g., leaky bucket with rate r and buffer size b). A signaling protocol is needed to carry the R-spec and Tspec to the routers where reservation is required; RSVP is a leading candidate for such signaling protocol.
18
Packet scheduling
Guaranteed service
Use token bucket filter to characterize traffic
Described by rate r and bucket depth b
Use WFQ at the routers Parekhs bound for worst case queuing delay = b/r
19
Call Admission
Call Admission: routers will admit calls based on their R-spec and T-spec and base on the current resource allocated at the routers to other calls.
20
Overview
Motivation for QoS Integrated Services (Intserv) Differentiated Services (Diffserv) Resource ReSerVation Protocol (RSVP)
21
Differentiated Services
Intended to address the following difficulties with Intserv and RSVP; Scalability: maintaining states by routers in high speed networks is difficult due to the very large number of flows Flexible Service Models: Intserv has only two classes, want to provide more qualitative service classes; want to provide relative service distinction (Platinum, Gold, Silver, ) Simpler signaling: (than RSVP) many applications and users may only want to specify a more qualitative notion of service
22
Diffserv - Motivation
Do fine-grained enforcement only at the edge of the network.
Typically slower links at edges E.g., mail sorting in post office
The core of the network uses only the type field for QoS management.
Small number of types with well defined forwarding behavior Can be handled fast
Example: expedited service versus best effort Evolution rather than revolution
Lecture 22: 11/20/2001 23
Diffserv - Discussion
Diffserv defines an architecture and a set of forwarding behaviors.
It is up to the service providers to define and implement end-to-end services on top of this architecture. Offers a more flexible service model; different providers can offer different service.
24
26
Core Functions
Forwarding: according to Per-Hop-Behavior or PHB specified for the particular packet class; such PHB is strictly based on class marking (no other header fields can be used to influence PHB). BIG ADVANTAGE: No state info to be maintained by routers!
27
Forwarding (PHB)
PHB result in a different observable (measurable) forwarding performance behavior. PHB does not specify what mechanisms to use to ensure required PHB performance behavior. Examples:
Class A gets x% of outgoing link bandwidth over time intervals of a specified length. Class A packets leave first before packets from class B.
28
Forwarding (PHB)
Expedited Forwarding (EF):
Guarantees a certain minimum rate for the EF traffic. Implies isolation: guarantee for the EF traffic should not be influenced by the other traffic classes. Admitted based on peak rate. Non-conformant traffic is dropped or shaped. Possible service: providing a virtual wire.
29
Forwarding (PHB)
Assured Forwarding (AF):
AF defines 4 classes with some bandwidth and buffers allocated to them. The intent is that it will be used to implement services that differ relative to each other (e.g., gold, silver,). Within each class, there are three drop priorities, which affect which packets will get dropped first if there is congestion. Lots of studies on how these classes and drop priorities interact with TCP flow control. Non-conformant traffic is remarked.
Lecture 22: 11/20/2001 30
Admission control makes sure that all links in the network core have sufficient EF bandwidth.
Simple case: sum of all virtual link bandwidth is less than the capacity of the slowest link.
Traffic enforcement for EF traffic limits how much EF traffic enters the network.
Lecture 22: 11/20/2001 31
Definition of end-to-end services for paths that cross networks with different forwarding behaviors
Some packets will be handled differently in different routers. Some routers are not DiffServ capable.
32
Overview
Motivation for QoS Integrated Services (Intserv) Differentiated Services (Diffserv) Resource ReSerVation Protocol (RSVP)
33
Service interface
How does the application describe what it wants?
Packet scheduling
How does the network meet promises?
34
Role of RSVP
Rides on top of unicast/multicast routing protocols. Must be present at sender(s), receiver(s), and routers. Carries resource requests all the way through the network. At each hop consults admission control and sets up reservation. Informs requester if failure.
35
36
RSVP Goals
Used on connectionless networks.
Should not replicate routing functionality. Should co-exist with route changes.
Limit control overhead. Modular design should be generic signaling protocol. Result:
Receiver-oriented Soft-state
37
Receiver-Initiated Reservation
Receiver initiates reservation by sending a reservation over the sink tree.
Assumes multicast tree has been set up previously.
Also uses receiver-initiated mechanism.
Hooks up with the reserved part of the tree. How far the request has to travel to the source depends on the level of service requested. Uses existing routing protocol, but routers have to store the sink tree (reverse path from forwarding path).
Properties:
Scales well: can have parallel independent connect and disconnect actions single shared resource required. Supports receiver heterogeneity: reservation specifies receiver requirements and capabilities.
Lecture 22: 11/20/2001 38
Soft State
Routers keep state about reservation. Periodic messages refresh state. Non-refreshed state times out automatically. Alternative: Hard state
No periodic refresh messages. State is guaranteed to be there. State is kept till explicit removal. Why could there be a problem?
40
41
PATH Messages
PATH messages carry senders T-spec.
Token bucket parameters
Routers note the direction PATH messages arrived and set up reverse path to sender. Receivers send RESV messages that follow reverse path and setup reservations. If reservation cannot be made, user gets an error.
42
RESV Messages
RESV messages carry receivers R-spec. Forwarded via reverse path of PATH. Queuing delay and bandwidth requirements. Source traffic characteristics (from PATH). Filter specification
Which transmissions can use the reserved resources? Reservation style.
44
RSVP reservations
Reservations from multiple receivers for a single sender are merged together at branching points. Reservations for multiple senders may be added up:
Video conference
45
Reservation Styles
Three styles
Wildcard/No filter does not specify a particular sender for group. Fixed filter sender explicitly specified for a reservation.
Video conference
46
Example
A S1 B S2, S3
R1
R2 R3
D 3b
R2 R3
48
S1:4b S2:5b
R1
D S1:3b S3:b
R2 R3
49
D (S1,S2,S3):3b
R2 R3
50
Changing Reservation
Receiver-oriented approach and soft state make it easy to modify reservation. Modification sent with periodic refresh.
51
Routing Changes
Routing protocol makes routing changes. In absence of route or membership changes, periodic PATH and RESV messages refresh established reservation state. When change, new PATH messages follow new path, new RESV messages set reservation. Non-refreshed state times out automatically.
52
State in Switches
Have to keep sink tree information.
No such thing as inverse multicast routing.
RSVP - Review
Concentration on multicast may have been wrong idea.
Unicast considered as special case of multicast.
Receiver initiation handle negotiation at application level. Receiver heterogeneity how can low-capability receiver benefit from video sent at high bandwidth?
Layered encoding
Soft state
Hard state works in telephony network
Lecture 22: 11/20/2001 54