RSVP Protocol
CategoryInternet Protocol
Resource Reservation Protocol (RSVP) 1.0 provides receiver-initiated setup of resource reservations for unicast or multicast rich content flows, with specific Quality-of-Service (QoS) properties requested from the network for all nodes along the path(s) of these flows.
Media Resource Reservation
Voice and Video Traffic Control
RSVP 1.0 provides a general facility for creating and maintaining distributed reservation state across a mesh of or unicast and multicast rich content delivery paths.
The protocol itself transfers and manipulates QoS and policy parameters as opaque data, passing it to the appropriate admission and policy control modules for interpretation. Assuming traffic control state is to be built and destroyed incrementally in routers and hosts, RSVP is designed to establish a soft state and send periodic refresh messages to maintain it along the reserved paths connecting event participants.
RSVP is simplex, i.e. such that makes reservations for unidirectional data flows, adapting dynamically to changing group memberships and routes. It provides several reservation styles to fit a variety of applications, based on a combination of the sender selection — explicit or wildcard, and the treatment of reservations for different senders within the same session — distinct for each upstream sender or shared among all selected senders. The resulting styles are mutually exclusive, i.e. not supporting mixed modes.