RFC 6511: Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths
In plain English — editorial summary, not part of the RFC
There are many deployment scenarios that require an egress Label Switching Router (LSR) to receive binding of the Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Label Switched Path (LSP) to an application and a payload identifier using some "out-of-band" (OOB) mechanism. This document defines protocol mechanisms to address this requirement. The procedures described in this document are equally applicable for point-to-point (P2P) and point-to-multipoint (P2MP) LSPs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6511
- Published
- February 2012
- Authors
- Z. Ali; G. Swallow; R. Aggarwal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6510Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes ObjectsCurrent
February 2012
- RFC 6512Using Multipoint LDP When the Backbone Has No Route to the RootCurrent
February 2012
- RFC 6513Multicast in MPLS/BGP IP VPNsUpdated
February 2012
- RFC 6514BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNsUpdated
February 2012
- RFC 6515IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNCurrent
February 2012
- RFC 6506Supporting Authentication Trailer for OSPFv3Obsoleted
February 2012
- RFC 6516IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join MessagesCurrent
February 2012
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
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?