OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels
draft-smirnov-ospf-xaf-te-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Anton Smirnov , Alvaro Retana , Michael Barnes | ||
| Last updated | 2016-04-10 (Latest revision 2015-10-08) | ||
| Replaced by | draft-ietf-ospf-xaf-te, draft-ietf-ospf-xaf-te, RFC 8687 | ||
| RFC stream | (None) | ||
| Formats | |||
| Reviews | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.)