IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities, December 2007
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- J.P. Vasseur, Ed.
J.L. Le Roux, Ed.
- ccamp (rtg)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
It is highly desired, in several cases, to take into account Traffic Engineering (TE) node capabilities during Multi Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered Label Switched Path (TE-LSP) selection, such as, for instance, the capability to act as a branch Label Switching Router (LSR) of a Point-To-MultiPoint (P2MP) LSP. This requires advertising these capabilities within the Interior Gateway Protocol (IGP). For that purpose, this document specifies Open Shortest Path First (OSPF) and Intermediate System-Intermediate System (IS-IS) traffic engineering extensions for the advertisement of control plane and data plane traffic engineering node capabilities. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.