Skip to main content

Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions
RFC 5786

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'OSPF Traffic Engineering (TE) extensions are used to advertise TE Link State Advertisements (LSAs) containing information …
Received changes through RFC Editor sync (changed abstract to '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]')
2015-10-14
(System) Notify list changed from ospf-chairs@ietf.org, draft-ietf-ospf-te-node-addr@ietf.org to (None)
2010-03-10
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2010-03-10
Cindy Morgan [Note]: 'RFC 5786' added by Cindy Morgan
2010-03-10
(System) RFC published