Skip to main content

OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels
draft-ietf-ospf-xaf-te-00

The information below is for an old version of the document.
Document Type Expired Internet-Draft (ospf WG)
Authors Anton Smirnov , Alvaro Retana , Michael Barnes
Last updated 2017-07-30 (Latest revision 2017-01-26)
Replaces draft-smirnov-ospf-xaf-te
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Reviews
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ietf-ospf-xaf-te-00.txt

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.

Authors

Anton Smirnov
Alvaro Retana
Michael Barnes

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)