IPv4 NLRI with IPv6 Next Hop Use Cases
draft-mishra-bess-deplment-guidlin-ipv4nlri-ipv6nh-00

Document Type Active Internet-Draft (individual)
Authors Gyan Mishra  , Mankamana Mishra  , Jeff Tantsura  , Lili Wang  , Qing Yang  , Adam Simpson  , Shuanglong Chen 
Last updated 2021-03-22
Replaces draft-mishra-bess-ipv4nlri-ipv6nh-use-cases
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
BESS Working Group                                             G. Mishra
Internet-Draft                                              Verizon Inc.
Intended status: Best Current Practice                         M. Mishra
Expires: September 23, 2021                                Cisco Systems
                                                             J. Tantsura
                                                                 L. Wang
                                                  Juniper Networks, Inc.
                                                                 Q. Yang
                                                         Arista Networks
                                                              A. Simpson
                                                                   Nokia
                                                                 S. Chen
                                                     Huawei Technologies
                                                          March 22, 2021

                 IPv4 NLRI with IPv6 Next Hop Use Cases
         draft-mishra-bess-deplment-guidlin-ipv4nlri-ipv6nh-00

Abstract

   As Enterprises and Service Providers upgrade their brown field or
   green field MPLS/SR core to an IPv6 transport, Multiprotocol BGP (MP-
   BGP)now plays an important role in the transition of the core as well
   as edge from IPv4 to IPv6.  Operators can now continue to support
   legacy IPv4, VPN-IPv4, and Multicast VPN-IPv4 customers.

   This document describes the critical use case and OPEX savings of
   being able to leverage the MP-BGP capability exchange usage as a pure
   transport, allowing both IPv4 and IPv6 to be carried over the same
   BGP TCP session.  By doing so, allows for the elimination of Dual
   Stacking on the PE-CE connections.  Thus making the eBGP peering
   IPv6-ONLY to now carry both IPv4 and IPv6 Network Layer Reachability
   Information (NLRI).

   This document now provides a solution for IXPs (Internet Exchange
   points) that are facing IPv4 address depletion at these peering
   points to use BGP-MP capability exchange defined in [RFC8950] to
   carry IPv4 (Network Layer Reachability Information) NLRI in an IPv6
   next hop using the [RFC5565] softwire mesh framework.

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

Mishra, et al.         Expires September 23, 2021               [Page 1]
Internet-DraDeployment Guidelines for Edge Peering for IPv4-  March 2021

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://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."

   This Internet-Draft will expire on September 23, 2021.

Copyright Notice

   Copyright (c) 2021 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
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   3.  eBGP PE-CE IPv4 and IPv6 NLRI over IPv6 Next Hop Peer Use
       Case Interop Testing  . . . . . . . . . . . . . . . . . . . .   5
   4.  RFC 8950 updates to RFC 5549  . . . . . . . . . . . . . . . .   6
   5.  Operational Improvements with Single IPv6 transport peer  . .   7
   6.  Operational Considerations  . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Appendix A.  IPv4 NLRI IPv6 Next Hop Vendor Testing . . . . . . .  10
     A.1.  Router and Switch Vendors Support and Quality Assurance
           Engineering Lab Results.  . . . . . . . . . . . . . . . .  11
Show full document text