Connecting IPv4 Islands over IPv6 MPLS Using IPv4 Provider Edge Routers (4PE)
draft-li-bess-4pe-02

Document Type Active Internet-Draft (individual)
Last updated 2017-03-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
BGP Enabled Services                                               Z. Li
Internet-Draft                                              China Mobile
Intended status: Standards Track                           March 9, 2017
Expires: September 10, 2017

Connecting IPv4 Islands over IPv6 MPLS Using IPv4 Provider Edge Routers
                                 (4PE)
                          draft-li-bess-4pe-02

Abstract

   This document explains how to interconnect IPv4 islands over a
   Multiprotocol Label Switching (MPLS)-enabled IPv6-only core.  This
   approach relies on IPv4 Provider Edge routers (4PE), which are Dual
   Stacks in order to connect to IPv4 islands and to the MPLS core.  The
   4PE routers exchange the IPv4 reachability information transparently
   over the core using the Multiprotocol Border Gateway Protocol (MP-
   BGP).  MP-BGP is extended to do this.  A new Subsequence Address
   Family Identifier (SAFI) with corresponding new format Network Layer
   Reachability Information (NLRI), is introduced.  The BGP Next Hop
   field is used to convey the IPv4 address of the 4PE router, a field
   is added in Network Layer Reachability Information (NLRI) to convey
   the IPv6 address of the 4PE router, so that dynamically established
   IPv6-signaled MPLS Label Switched Paths (LSPs) can be used without
   explicit tunnel configuration.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Li                     Expires September 10, 2017               [Page 1]
Internet-Draft                     4PE                        March 2017

   This Internet-Draft will expire on September 10, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   3
   3.  4PE SAFI  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Exchange IPv4 reachability information among 4PE routers  . .   6
   5.  Transport IPv4 packets among 4PE routers  . . . . . . . . . .   7
   6.  IANA Requirements . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Consideration  . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   After IPv6 [RFC2460] is widely deployed, IPv6-only networks and nodes
   will become dominate.  How to provide the connectivity for the
   remaining IPv4-only islands through the IPv6-only MPLS network will
   become a problem, as depicted in the following figure.

Li                     Expires September 10, 2017               [Page 2]
Internet-Draft                     4PE                        March 2017

      +--------------+
      |  IPv4-only   |
      |  island A    CE--4PE----------------+
      |              |     |                |
      +--------------+     |                |    +----------------+
                           |   IPv6-only    |    |                |
Show full document text