IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities
RFC 5073, “IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities”, is a Proposed Standard document published in December 2007 by J.P. Vasseur, J.L. Le Roux. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5073 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5072 IP Version 6 over PPP
- RFC 5074 DNSSEC Lookaside Validation
- RFC 5071 Dynamic Host Configuration Protocol Options Used by PXELINUX
- RFC 5075 IPv6 Router Advertisement Flags Option
- RFC 5070 The Incident Object Description Exchange Format
- RFC 5076 ENUM Validation Information Mapping for the Extensible Provisioning Protocol
- RFC 5068 Email Submission Operations: Access and Accountability Requirements
- RFC 5078 IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees Timeline