OSPF Routing with Cross-Address Family Traffic Engineering Tunnels


== Abstract ==

When using Traffic Engineering (TE) in a dual-stack IPv4/IPv6 network the Multiprotocol Label Switching (MPLS) TE Label Switched Paths (LSP) infrastructure may be duplicated, even if the destination IPv4 and IPv6 addresses belong to the same remote router. In order to achieve an integrated MPLS TE LSP infrastructure, OSPF routes must be computed over MPLS TE tunnels created using information propagated in another OSPF instance. This is solved by advertising cross-address family (X-AF) OSPF TE information.  This document describes an update to RFC5786 that allows for the easy identification of a router's local X-AF IP addresses.


== Original document ==

The different versions of the original document can be found in:

* [http://dx.doi.org/10.17487/rfc8687 http://dx.doi.org/10.17487/rfc8687]

* [https://www.rfc-editor.org/info/rfc8687 https://www.rfc-editor.org/info/rfc8687],
: [https://www.rfc-editor.org/rfc/rfc8687.txt https://www.rfc-editor.org/rfc/rfc8687.txt],
: [https://tools.ietf.org/html/rfc8687 https://tools.ietf.org/html/rfc8687],
: [https://tools.ietf.org/html/draft-ietf-ospf-xaf-te-05 https://tools.ietf.org/html/draft-ietf-ospf-xaf-te-05],
: [https://academic.microsoft.com/#/detail/2564109585 https://academic.microsoft.com/#/detail/2564109585]