RSVP is a network control protocol that enables Internet applications to
signal LSPs for MPLS-TE,
and LSPs for O-UNI. The
RSVP implementation is compliant with the IETF RFC 2205,
RFC 3209, and
When configuring an O-UNI LSP, the
RSVP session is bidirectional. The exchange of data between a pair of machines
actually constitutes a single RSVP session. The RSVP session is established
using an Out-Of-Band (OOB) IP Control Channel (IPCC) with the neighbor. The
RSVP messages are transported over an interface other than the data interface.
RSVP supports extensions according
to OIF2000.125.7 requirements, including:
RSVP is automatically enabled on interfaces on which MPLS-TE is
configured. For MPLS-TE LSPs with nonzero bandwidth, the RSVP bandwidth has to
be configured on the interfaces. There is no need to configure RSVP, if all
MPLS-TE LSPs have zero bandwidth
For O-UNI, there is no need for any RSVP
RSVP Refresh Reduction, defined in RFC 2961, includes support for
reliable messages and summary refresh messages. Reliable messages are
retransmitted rapidly if the message is lost. Because each summary refresh
message contains information to refresh multiple states, this greatly reduces
the amount of messaging needed to refresh states. For refresh reduction to be
used between two routers, it must be enabled on both routers. Refresh Reduction
is enabled by default.
Message rate limiting for RSVP allows you to set a maximum threshold on
the rate at which RSVP messages are sent on an interface. Message rate limiting
is disabled by default.
The process that implements RSVP is restartable. A software upgrade,
process placement or process failure of RSVP or any of its collaborators, has
been designed to ensure Nonstop Forwarding (NSF) of the data plane.
RSVP supports graceful restart, which is compliant with RFC 3473. It
follows the procedures that apply when the node reestablishes communication
with the neighbor’s control plane within a configured restart time.
It is important to note that RSVP is not a routing protocol. RSVP works
in conjunction with routing protocols and installs the equivalent of dynamic
access lists along the routes that routing protocols calculate. Because of
this, implementing RSVP in an existing network does not require migration to a
new routing protocol.