metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8687: OSPF Routing with Cross-Address Family Traffic Engineering Tunnels

In plain English — editorial summary, not part of the RFC

When using Traffic Engineering (TE) in a dual-stack IPv4/IPv6 network, the Multiprotocol Label Switching (MPLS) TE Label Switched Path (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 issue is solved by advertising cross-address family (X-AF) OSPF TE information. This document describes an update to RFC 5786 that allows for the easy identification of a router's local X-AF IP addresses.

Document record

Document ID
RFC8687
Published
November 2019
Authors
A. Smirnov; A. Retana; M. Barnes
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
8
Also known as
—
Updates:
RFC 5786

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8687-ospf-routing-with-cross-address-family-traffic-engineering-tunnels