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

Document Type Expired Internet-Draft (ospf WG)
Last updated 2017-07-30 (latest revision 2017-01-26)
Replaces draft-smirnov-ospf-xaf-te
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
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 (as@cisco.com)
Alvaro Retana (aretana@cisco.com)
Michael Barnes (mjbarnes@cisco.com)

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