%% You should probably cite rfc8687 instead of this I-D. @techreport{ietf-ospf-xaf-te-01, number = {draft-ietf-ospf-xaf-te-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-ospf-xaf-te/01/}, author = {Anton Smirnov and Alvaro Retana and Michael Barnes}, title = {{OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels}}, pagetotal = 8, year = 2017, month = oct, day = 16, 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.}, }