Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 4420

Updates:

RFC 3209,RFC 3473

Updated by:

RFC 6510

Authors:

A. Farrel, Ed.
D. Papadimitriou
JP. Vasseur
A. Ayyangar

Stream:

IETF

Source:

ccamp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5420

Discuss this RFC: Send questions or comments to the mailing listccamp@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5420

Abstract

Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) maybe established using the Resource Reservation Protocol TrafficEngineering (RSVP-TE) extensions. This protocol includes an object(the SESSION_ATTRIBUTE object) that carries a Flags field used toindicate options and attributes of the LSP. That Flags field haseight bits, allowing for eight options to be set. Recent proposals inmany documents that extend RSVP-TE have suggested uses for each ofthe previously unused bits.

This document defines a new object for RSVP-TE messages that allowsthe signaling of further attribute bits and also the carriage ofarbitrary attribute parameters to make RSVP-TE easily extensible tosupport new requirements. Additionally, this document defines a wayto record the attributes applied to the LSP on a hop-by-hop basis.

The object mechanisms defined in this document are equally applicableto Generalized MPLS (GMPLS) Packet Switch Capable (PSC) LSPs and toGMPLS non-PSC LSPs.

This document replaces and obsoletes the previous version of thiswork, published as RFC 4420. The only change is in the encoding of theType-Length-Variable (TLV) data structures. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.