datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)
draft-ooms-v6ops-bgp-tunnel-07

RFC
Document Stream: IETF
Last updated: 2006-12-12
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 4798
Responsible AD: Bill Fenner
Send notices to: idr-chairs@tools.ietf.org, jeremy.de_clercq@alcatel.be, dirk@onesparrow.com, stuart.prevost@bt.com, flefauch@cisco.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ooms-v6ops-bgp-tunnel.

Abstract:
This document explains how to interconnect IPv6 islands over a Multiprotocol Label Switching (MPLS)-enabled IPv4 cloud. This approach relies on IPv6 Provider Edge routers (6PE), which are Dual Stack in order to connect to IPv6 islands and to the MPLS core, which is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6 reachability information transparently over the core using the Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4. In doing so, the BGP Next Hop field is used to convey the IPv4 address of the 6PE router so that dynamically established IPv4-signaled MPLS Label Switched Paths (LSPs) can be used without explicit tunnel configuration. [STANDARDS-TRACK]

Authors:
Jeremy De Clercq <jeremy.de_clercq@alcatel-lucent.be>
Dirk Ooms <dirk@onesparrow.com>
Francois Le Faucheur <flefauch@cisco.com>
Stuart Prevost <stuart.prevost@bt.com>

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