Control Plane Considerations for Enhanced VPN
draft-dong-teas-enhanced-vpn-control-plane-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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)
Network Working Group                                            J. Dong
Internet-Draft                                                     Z. Li
Intended status: Informational                       Huawei Technologies
Expires: May 7, 2020                                              F. Qin
                                                            China Mobile
                                                        November 4, 2019

             Control Plane Considerations for Enhanced VPN
             draft-dong-teas-enhanced-vpn-control-plane-00

Abstract

   Enhanced VPN (VPN+) is an enhancement to VPN services to support the
   needs of new applications, particularly including the applications
   that are associated with 5G services.  An enhanced VPN may be used
   for 5G transport network slicing, and will also be of use in more
   generic scenarios.  [I-D.ietf-teas-enhanced-vpn] describes the
   framework and candidate component technologies for providing enhanced
   VPN services.  This document describes the control plane
   requirements, functions and considerations to enable VPN+ services.
   Specifically, the scalability of control plane is analyzed, and the
   proposed optimization mechanisms are described.

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 RFC 2119 [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 May 7, 2020.

Dong, et al.               Expires May 7, 2020                  [Page 1]
Internet-Draft             VPN+ Control Plane              November 2019

Copyright Notice

   Copyright (c) 2019 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements on Control Plane . . . . . . . . . . . . . . . .   3
     2.1.  Support of Isolation  . . . . . . . . . . . . . . . . . .   3
       2.1.1.  Data Plane Isolation  . . . . . . . . . . . . . . . .   3
       2.1.2.  Control Plane Isolation . . . . . . . . . . . . . . .   4
     2.2.  Attributes of Network Slice . . . . . . . . . . . . . . .   5
     2.3.  Number of Network Slices  . . . . . . . . . . . . . . . .   5
   3.  Control Plane Functions . . . . . . . . . . . . . . . . . . .   6
     3.1.  Distributed Control Plane . . . . . . . . . . . . . . . .   6
     3.2.  Centralized Controller  . . . . . . . . . . . . . . . . .   7
   4.  Scalability Considerations  . . . . . . . . . . . . . . . . .   8
     4.1.  Distributed Control Plane . . . . . . . . . . . . . . . .   8
     4.2.  Centralized Control Plane . . . . . . . . . . . . . . . .   9
   5.  Optimization Mechanisms . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Driven largely by needs arising from the 5G mobile network, the
   concept of network slicing has gained traction [TS28530].  Network
   slicing requires to partition the physical network to several pieces
   to provide each network slice with the required networking,
   computing, and storage resources and functions to meet the
   requirement of slice tenants.  As specified in
Show full document text