Editing Resource Reservation Protocol (section)

==History and related standards==
The basic concepts of RSVP were originally proposed in 1993.<ref name="RSVP93">Zhang, L., Deering, S., Estrin, D., Shenker, S., and D. Zappala, "RSVP: A New Resource ReSerVation Protocol", IEEE Network, September 1993</ref>

RSVP is described in a series of RFC documents from the IETF:

* {{IETF RFC|2205|link=no}}: The version 1 functional specification was described in RFC 2205 (Sept. 1997) by [[Internet Engineering Task Force|IETF]]. Version 1 describes the interface to admission (traffic) control that is based "only" on resource availability. Later [[#RFC2750|RFC2750]] extended the admission control support.
* {{IETF RFC|2210|link=no}} defines the use of RSVP with controlled-load RFC 2211 and guaranteed RFC 2212 QoS control services. More details in [[Integrated Services]]. Also defines the usage and data format of the data objects (that carry resource reservation information) defined by RSVP in RFC 2205.
* {{IETF RFC|2211|link=no}} specifies the network element behavior required to deliver Controlled-Load services.
* {{IETF RFC|2212|link=no}} specifies the network element behavior required to deliver guaranteed QoS services.
* {{IETF RFC|2750|link=no}} describes a proposed extension for supporting generic [[policy|policy based]] admission control in RSVP. The extension included a specification of policy objects and a description on handling policy events. (January 2000).
* {{IETF RFC|3209|link=no}}, "RSVP-TE: Extensions to RSVP for LSP Tunnels" (December 2001).
* {{IETF RFC|3473|link=no}}, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions" (January 2003).
* {{IETF RFC|3936|link=no}}, "Procedures for Modifying the '''R'''esource re'''S'''er'''V'''ation '''P'''rotocol (RSVP)" (October 2004), describes current best practices and specifies procedures for modifying RSVP.
* {{IETF RFC|4495|link=no}}, "A Resource Reservation Protocol (RSVP) Extension for the Reduction of Bandwidth of a Reservation Flow" (May 2006), extends RSVP to enable the bandwidth of an existing reservation to be reduced instead of tearing down the reservation.
* {{IETF RFC|4558|link=no}}, "Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement" (June 2006).