Use of IP Tunnels In IP VPNs
draft-zmw-bess-tunnel-vpn-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
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)
BESS                                                        Zheng. Zhang
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                             Shaowen. Ma
Expires: April 25, 2019                                          Juniper
                                                               Cui. Wang
                                                    Matrium Technologies
                                                        October 22, 2018

                      Use of IP Tunnels In IP VPNs
                      draft-zmw-bess-tunnel-vpn-00

Abstract

   This document updates [RFC6513], [RFC6514] and
   [I-D.ietf-idr-tunnel-encaps] to provide additional details about
   using GRE tunnels for IP VPN, and using IP tunnels for Multicast VPN
   (MVPN).

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 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 April 25, 2019.

Copyright Notice

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

Zhang, et al.            Expires April 25, 2019                 [Page 1]
Internet-Draft             BESS TUNNEL IP VPN               October 2018

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  GRE Considered as a Tunnel Type Whose Encapsulation
           Includes VNI field  . . . . . . . . . . . . . . . . . . .   3
     3.2.  Attach Tunnel Encap Attribute to MVPN PMSI/Leaf A-D
           Routes  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Terminology

   This document uses terminologies defined in [RFC6513], [RFC6514].

2.  Introduction

   [RFC4364] specifies protocol and procedures for providing IP Virtual
   Private Network (IP VPN) service using BGP signaling and MPLS data
   plane, often referred to as BGP/MPLS VPN.  Along with the great
   success of BGP/MPLS VPN, use of IP tunneling instead of MPLS has been
   growing significantly, especially in Data Centers or where MPLS
   infrastructure is not available.

   IP tunnels typically include GRE, VXLAN, VXLAN-GPE, and NVGRE.  Both
   VXLAN and NVGRE are targeted at Layer 2 Overlay services and the
   payload after the VXLAN or NVGRE header is Ethernet.  For GRE
   [RFC2784] and VXLAN-GPE, the payload could be either IP or Ethernet
   or others.  [I-D.ietf-idr-tunnel-encaps] specifies how these tunnels
   can be used for VPNs, and [RFC6513] describes how GRE tunnels can be
   used for Multicast VPNs (MVPN).

   However, existing documents do not fully cover some deployment
   scenarios as listed below.

Zhang, et al.            Expires April 25, 2019                 [Page 2]
Internet-Draft             BESS TUNNEL IP VPN               October 2018

   o  Use of GRE tunnel for IP VPN: GRE tunnel is currently not listed
      as one of the three tunnel types whose encapsulation header
      includes a Virtual Network Identifier (VNI), even though an
      optional key in GRE header can be used as a VNI.  As a result,
      currently there is no document specifies the use of GRE tunnel for
Show full document text