MPLS

Introduction of RSVP
• Resource ReSerVation Protocol.
• Allows applications running in hosts to reserve
resources in the Internet for their data flows.
• Used by the routers to forward bandwidth
reservation requests.
• RSVP software must be present in the receivers,
sender, and routers.
 Introduction of RSVP (cont.)
• Two principle characteristics of RSVP
– It provides reservations for bandwidth in multicast
trees(unicast is handled as a special case).
– It is receiver-oriented.
• RSVP reserves resources for only one direction data
streams.
• RSVP is not a routing protocol
– It does not determine the links in which the reservations are
to be made.
– An RSVP daemon consults the local routing databases to
obtain routes.
 Introduction of RSVP (cont.)
• RSVP depends on an underlying routing
protocol(unicast or multicast) to determine the
routes for the flows
• RSVP is sometimes referred to as a signaling
protocol that allows hosts to establish and tear-
down reservations for data flows
W
RSVP in Hosts and Routers

HOST ROUTER

RSVP RSVP
Application messages Routing
RSVP Protocol RSVP messages
process process process
Policy Policy
Control Control
Data

Admission
Admission Control
Control Packet
Packet Scheduler
Classifier Scheduler Classifier Data
Data
Packet Data
Scheduler
RSVP: multicast- and receiver-oriented.
 Heterogeneous receivers
• Sender does not have to know the receiving rates
of all receivers.
• It only needs to know the maximum rate of all its
receivers.
• The sender encodes the video or audio into
multiple layers and sends all the layers up to the
maximum rate into multicast tree.
• The receivers pick out the layers that are
appropriate for their receiving rates.
 Heterogeneous receivers (cont.)
• In order to not excessively waste bandwidth in
the network’s links, the heterogeneous receivers
must communicate to the network the rates they
can handle.
• RSVP gives foremost attention to the issue of
reserving resources for heterogeneous receivers.
RSVP Operation Example

Path message Session

(Ipa,PID,Port)
Resv message
IGMP(1)
IGMP message
Receiver B
Data Resv (3)
Packet
Session
(Ipa,PID,Port) (4)

path (2) IGMP (1)

Sender

Resv(3) Receiver A
Merge Session
point (Ipa,PID,Port)
A Few Simple Examples

An RSVP example
 An RSVP video conference example

• Each router receives a reservation message from

each of its downstream links in the multicast tree
and sends only one reservation message into its
upstream link.
 Call Admission
• Whenever a router receives a new reservation
message, it must first determine if its
downstream links on the multicast tree can
accommodate the reservation.
• This admission test is performed whenever a
router receives a reservation message.
• RSVP does not define the admission test, but it
assumes that the routers perform such a test and
that RSVP can interact with the test.
 Path Messages
• Path messages are another important RSVP message type.
• Originate at the senders and flow downstream towards the
receivers.
• The principle purpose of the path messages is to let the routers
know on which links they should forward the reservation
messages.
• The path messages also contain a sender Tspec, which defines
the traffic characteristics of the data stream that the sender will
generate.
• Tspec can be used to prevent over reservation.
 Resv messages
• After a receiver has received a Path message, it sends a Resv
message.
• The Resv message travels toward the sender (upstream) and
makes a resource reservation on the routers that support
RSVP.
• If a router does not support RSVP on the path, it routes the
packet based on the best-effort delivery methods.
 Reservation merging
• In RSVP, the resources are not reserved for each receiver in a flow; the
reservation is merged. In Figure, Rc3 requests a 2-Mbps bandwidth while Rc2
requests a 1-Mbps bandwidth.
• Router R3, which needs to make a bandwidth reservation, merges the two
requests. The reservation is made for 2 Mbps, the larger of the two, because a 2-
Mbps input reservation can handle both requests.
• The same situation is true for R2. Rc2 and Rc3, both belonging to one single flow,
request different amounts of bandwidth.
• In a multimedia environment, different receivers may handle different grades of
quality.
• For example, Rc2 may be able to receive video only at 1 Mbps (lower quality),
while Rc3 may be able to receive video at 2 Mbps (higher quality).
 Soft State
• The reservation in the routers and hosts are maintained
with soft states.
• Each reservation for bandwidth stored in a router has an
associated timer.
• If a receiver desires to maintain a reservation, it must
periodically refresh the reservation by sending reservation
messages.
• A receiver can also change its reservation by adjusting its
reservation in its stream of refresh messages.
• The senders must also refresh the path state by periodically
sending path messages.
 Transport of Reservation Messages
• RSVP messages are sent hop-by-hop directly over
IP, thus the RSVP message is placed in the
information field of the IP datagram.
• If an RSVP path or reservation message is lost, a
replacement refresh message should arrive soon.
 Disadvantage of RSVP
• Need more memory to record per flow state
information of each node in network.
• RSVP is lack of scalability.