[rfc-dist] RFC 4798 on Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)

[rfc-editor at rfc-editor.org ([e-mail])]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4798

        Title:      Connecting IPv6 Islands over IPv4 
                    MPLS Using IPv6 Provider Edge Routers 
                    (6PE) 
        Author:     J. De Clercq, D. Ooms,
                    S. Prevost, F. Le Faucheur
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    jeremy.de_clercq at alcatel-lucent.be, 
                    dirk at onesparrow.com, 
                    stuart.prevost at bt.com,  flefauch at cisco.com
        Pages:      14
        Characters: 31381
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ooms-v6ops-bgp-tunnel-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4798.txt

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]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...