Advertising a Router's Local Addresses in OSPF Traffic Engineering Extensions
RFC 5786, “Advertising a Router's Local Addresses in OSPF Traffic Engineering Extensions”, is a Proposed Standard document published in March 2010 by R. Aggarwal, K. Kompella. It updates RFC 3630. It has since been updated by RFC 6827, RFC 8687. The canonical text is published by the RFC Editor.
Abstract
OSPF Traffic Engineering (TE) extensions are used to advertise TE Link State Advertisements (LSAs) containing information about TE-enabled links. The only addresses belonging to a router that are advertised in TE LSAs are the local addresses corresponding to TE-enabled links, and the local address corresponding to the Router ID.
In order to allow other routers in a network to compute Multiprotocol Label Switching (MPLS) Traffic Engineered Label Switched Paths (TE LSPs) to a given router's local addresses, those addresses must also be advertised by OSPF TE.
This document describes procedures that enhance OSPF TE to advertise a router's local addresses. [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 5786 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5785 Defining Well-Known Uniform Resource Identifiers
- RFC 5787 OSPFv2 Routing Protocols Extensions for Automatically Switched Optical Network Routing
- RFC 5784 Sieve Email Filtering: Sieves and Display Directives in XML
- RFC 5788 IMAP4 Keyword Registry
- RFC 5783 Congestion Control in the RFC Series
- RFC 5789 PATCH Method for HTTP
- RFC 5782 DNS Blacklists and Whitelists
- RFC 5790 Lightweight Internet Group Management Protocol Version 3 and Multicast Listener Discovery Version 2 Protocols