RFC 6510: Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects
In plain English — editorial summary, not part of the RFC
Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) established using the Resource Reservation Protocol Traffic Engineering (RSVP-TE) extensions may be signaled with a set of LSP-specific attributes. These attributes may be carried in both Path and Resv messages. This document specifies how LSP attributes are to be carried in RSVP Path and Resv messages using the Routing Backus-Naur Form and clarifies related Resv message formats. This document updates RFC 4875 and RFC 5420. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6510
- Published
- February 2012
- Authors
- L. Berger; G. Swallow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6511Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched PathsCurrent
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 6506Supporting Authentication Trailer for OSPFv3Obsoleted
February 2012
- RFC 6515IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNCurrent
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?