Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers
RFC 4798, “Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers”, is a Proposed Standard document published in February 2007 by J. De Clercq, D. Ooms, S. Prevost, F. Le Faucheur. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4798 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4797 Use of Provider Edge to Provider Edge Generic Routing Encapsulation or IP in BGP/MPLS IP Virtual Private Networks
- RFC 4796 The Session Description Protocol Content Attribute
- RFC 4795 Link-local Multicast Name Resolution
- RFC 4801 Definitions of Textual Conventions for Generalized Multiprotocol Label Switching Management
- RFC 4802 Generalized Multiprotocol Label Switching Traffic Engineering Management Information Base
- RFC 4793 The EAP Protected One-Time Password Protocol
- RFC 4803 Generalized Multiprotocol Label Switching Label Switching Router Management Information Base
- RFC 4792 Encoding Instructions for the Generic String Encoding Rules