RFC 5945: Resource Reservation Protocol (RSVP) Proxy Approaches
In plain English — editorial summary, not part of the RFC
The Resource Reservation Protocol (RSVP) can be used to make end-to- end resource reservations in an IP network in order to guarantee the quality of service required by certain flows. RSVP assumes that both the data sender and receiver of a given flow take part in RSVP signaling. Yet, there are use cases where resource reservation is required, but the receiver, the sender, or both, is not RSVP-capable. This document presents RSVP proxy behaviors allowing RSVP routers to initiate or terminate RSVP signaling on behalf of a receiver or a sender that is not RSVP-capable. This allows resource reservations to be established on a critical subset of the end-to-end path. This document reviews conceptual approaches for deploying RSVP proxies and discusses how RSVP reservations can be synchronized with application requirements, despite the sender, receiver, or both not participating in RSVP. This document also points out where extensions to RSVP (or to other protocols) may be needed for deployment of a given RSVP proxy approach. However, such extensions are outside the scope of this document. Finally, practical use cases for RSVP proxy are described. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5945
- Published
- October 2010
- Authors
- F. Le Faucheur; J. Manner; D. Wing; A. Guillou
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 50
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5946Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver ProxyCurrent
October 2010
- RFC 5961Improving TCP's Robustness to Blind In-Window AttacksUpdated
August 2010
- RFC 5927ICMP Attacks against TCPCurrent
July 2010
- RFC 5926Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)Current
June 2010
- RFC 5925The TCP Authentication OptionCurrent
June 2010
- RFC 6016Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNsCurrent
October 2010
- RFC 5865A Differentiated Services Code Point (DSCP) for Capacity-Admitted TrafficCurrent
May 2010
- RFC 6040Tunnelling of Explicit Congestion NotificationUpdated
November 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?