Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

J.P. Vasseur, Ed.
J.L. Le Roux, Ed.

Stream:

IETF

Source:

ccamp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

It is highly desired, in several cases, to take into account TrafficEngineering (TE) node capabilities during Multi Protocol LabelSwitching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered LabelSwitched Path (TE-LSP) selection, such as, for instance, thecapability to act as a branch Label Switching Router (LSR) of aPoint-To-MultiPoint (P2MP) LSP. This requires advertising thesecapabilities within the Interior Gateway Protocol (IGP). For thatpurpose, this document specifies Open Shortest Path First (OSPF) andIntermediate System-Intermediate System (IS-IS) traffic engineeringextensions for the advertisement of control plane and data planetraffic engineering node capabilities. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.