API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5946
[ACTIVE]

Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy

Metadata

Publisher
IETF
Doc Type
Standard
Pages
35
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]
Publication Date
2010-10-01
Status Note
Proposed Standard
DOI
10.17487/RFC5946
Link
https://doi.org/10.17487/RFC5946
Author(s)
François Le Faucheur
Jukka Manner
Ashok Narayanan
Allan Guillou
Hemant Malik
Latest version of IETF RFC 5946

Document Versions — IETF RFC 5946

  • ▶ IETF RFC 5946 (2010-10-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Behringer, M. and F. Le Faucheur, "Applicability of Keying Methods for RSVP Security", Work in Progress, June 2010. EXTERNAL
  • Le Faucheur, F., "IP Router Alert Considerations and Usage", Work in Progress, October 2009. EXTERNAL
  • IETF RFC 3181 [Active*]
  • RFC4230 — RFC4230 EXTERNAL
  • RFC5945 — RFC5945 EXTERNAL
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5946.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5946, Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy. Available at https://doi.org/10.17487/RFC5946
Snippet:
IETF RFC 5946, Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy. Available at https://doi.org/10.17487/RFC5946

HTML (ISO 690 compliant)

Preview:
IETF RFC 5946, Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy. Available at https://doi.org/10.17487/RFC5946
Snippet:
<span class="citation"><cite>IETF RFC 5946</cite>, Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy. Available at <a href="https://doi.org/10.17487/RFC5946" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5946</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5946, Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy
doi: 10.17487/RFC5946
url: https://doi.org/10.17487/RFC5946
Snippet:
<li>
<cite id="bib-rfc5946">IETF RFC 5946</cite>, Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy
<span class="doi">10.17487/RFC5946</span>
</li>

Referenced By