RFC 5786

"Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions", March 2010

Canonical URL:

http://www.rfc-editor.org/rfc/rfc5786.txt
This document is also available in this non-normative format: PDF.

Status:

PROPOSED STANDARD

Updates:

RFC 3630

Updated by:

RFC 6827

Authors:

R. Aggarwal
K. Kompella

Stream:

IETF

Source:

ospf (rtg)

Please refer here for any errata for this document. To submit a new errata report, go to the main errata page.

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]

For the definition of Stream, see RFC 4844.