Editing Resource Reservation Protocol (section)

{{Short description|Computer network protocol}}
{{Use American English|date=September 2020}}

The '''Resource Reservation Protocol''' ('''RSVP''') is a [[transport layer]]<ref>{{cite book|url=https://books.google.com/books?id=pIIu7IbUwIcC&pg=PA583 |title=Juniper Networks Field Guide and Reference|page=583|first1=Aviva|last1=Garrett|first2=Gary|last2=Drenan|first3=Cris|last3=Morris|year=2002|publisher=Addison-Wesley Professional |isbn=9780321122445}}</ref> [[Communications protocol|protocol]] designed to reserve resources across a [[Computer networking|network]] using the [[integrated services]] model. RSVP operates over an [[IPv4]] or [[IPv6]] and provides receiver-initiated setup of resource reservations for [[IP multicast|multicast]] or [[unicast]] data flows. It does not transport application data but is similar to a control protocol, like [[Internet Control Message Protocol]] (ICMP) or [[Internet Group Management Protocol]] (IGMP). RSVP is described in {{IETF RFC|2205}}.

RSVP can be used by [[host (network)|hosts]] and [[router (computing)|routers]] to request or deliver specific levels of [[quality of service]] (QoS) for application [[Stream (computing)|data streams]]. RSVP defines how applications place reservations and how they can relinquish the reserved resources once no longer required. RSVP operations will generally result in resources being reserved in each node along a path. RSVP is not a [[routing protocol]] but was designed to interoperate with current and future routing protocols.

In 2003, development effort was shifted from RSVP to [[RSVP-TE]] for [[teletraffic engineering]]. [[Next Steps in Signaling]] (NSIS) was a proposed replacement for RSVP.

{{IPstack}}