Resource Reservation Protocol Extensions for Path-Triggered RSVP Receiver Proxy
RFC 5946, “Resource Reservation Protocol Extensions for Path-Triggered RSVP Receiver Proxy”, is a Proposed Standard document published in October 2010 by F. Le Faucheur, J. Manner, A. Narayanan, A. Guillou, H. Malik. It updates RFC 2205. The canonical text is published by the RFC Editor.
Abstract
Resource Reservation Protocol (RSVP) signaling can be used to make end-to-end resource reservations in an IP network in order to guarantee the Quality of Service (QoS) required by certain flows. With conventional RSVP, both the data sender and receiver of a given flow take part in RSVP signaling. Yet, there are many use cases where resource reservation is required, but the receiver, the sender, or both, is not RSVP-capable. Where the receiver is not RSVP- capable, an RSVP router may behave as an RSVP Receiver Proxy, thereby performing RSVP signaling on behalf of the receiver. This allows resource reservations to be established on the segment of the end-to- end path from the sender to the RSVP Receiver Proxy. However, as discussed in the companion document "RSVP Proxy Approaches", RSVP extensions are needed to facilitate operations with an RSVP Receiver Proxy whose signaling is triggered by receipt of RSVP Path messages from the sender. This document specifies these extensions. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5946 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5945 Resource Reservation Protocol Proxy Approaches
- RFC 5947 Requirements for Multiple Address of Record Reachability Information in the Session Initiation Protocol
- RFC 5944 IP Mobility Support for IPv4, Revised
- RFC 5948 Transmission of IPv4 Packets over the IP Convergence Sublayer of IEEE 802.16
- RFC 5943 A Dedicated Routing Policy Specification Language Interface Identifier for Operational Testing
- RFC 5949 Fast Handovers for Proxy Mobile IPv6
- RFC 5942 IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes
- RFC 5950 Network Management Framework for MPLS-based Transport Networks