Protocol Action: 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE)' to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The IESG has approved the following document:

- 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge 
   Routers (6PE) '
   <draft-ooms-v6ops-bgp-tunnel-06.txt> as a Proposed Standard

This document is the product of the Inter-Domain Routing Working Group. 

The IESG contact persons are Bill Fenner and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ooms-v6ops-bgp-tunnel-06.txt

Technical Summary 

This document explains how to interconnect IPv6 islands over a
Multi-Protocol 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
Multi-Protocol 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.

Working Group Summary 

The v6ops working group had consensus to develop this approach, 
and handed the document off to the idr working group for its BGP
expertise. There were no comments on the document during the idr
WG Last Call.

Protocol Quality 

There are multiple implementations of this specification. Specifically
there are two implementations by the router vendors, and three
implementations by the network test equipment vendors. The full
implementation report is available (see
http://www.ietf.org/IESG/Implementations/Implementation_draft-levy-idr-6pe-survey.txt).
 
Note to RFC Editor
 
Please insert the following paragraph after the first paragraph of section
1:

        The 6PE approach is required in addition to the use of
        standard tunnels, as it provides a solution for an MPLS
        environment where all tunnels are established dynamically,
        or for an environment where the effort to configure and
        maintain explicitly configured tunnels is not acceptable.


_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux