OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels
draft-ietf-ospf-xaf-te-01
| Document | Type | Expired Internet-Draft (lsr WG) | |
|---|---|---|---|
| Authors | Anton Smirnov , Alvaro Retana , Michael Barnes | ||
| Last updated | 2018-04-19 (Latest revision 2017-10-16) | ||
| Replaces | draft-smirnov-ospf-xaf-te | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
SECDIR Last Call review
(of
-07)
Has Nits
RTGDIR Last Call review
(of
-02)
Has Nits
|
||
| 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) |
https://www.ietf.org/archive/id/draft-ietf-ospf-xaf-te-01.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.)