Scalability Considerations for Enhanced VPN (VPN+)
draft-dong-teas-enhanced-vpn-vtn-scalability-01
TEAS Working Group J. Dong
Internet-Draft Z. Li
Intended status: Informational Huawei Technologies
Expires: May 6, 2021 F. Qin
China Mobile
G. Yang
China Telecom
November 2, 2020
Scalability Considerations for Enhanced VPN (VPN+)
draft-dong-teas-enhanced-vpn-vtn-scalability-01
Abstract
Enhanced VPN (VPN+) aims to provide enhancements to existing VPN
services to support the needs of new applications, particularly
including the applications that are associated with 5G services.
VPN+ could be used to provide network slicing in 5G, and may also be
of use in more generic scenarios, such as enterprise services which
have demanding requirement. With the requirement for VPN+ services
increase, scalability would become an important factor for deployment
of VPN+. This document describes the scalability considerations in
the control plane and data plane to enable VPN+ services, some
optimization mechanisms are also described.
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 6, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Dong, et al. Expires May 6, 2021 [Page 1]
Internet-Draft VPN+ Scalability Considerations November 2020
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. VPN+ Scalability Requirements . . . . . . . . . . . . . . . . 3
3. VPN+ Scalability Considerations . . . . . . . . . . . . . . . 4
3.1. Control Plane Scalability . . . . . . . . . . . . . . . . 5
3.1.1. Distributed Control Plane . . . . . . . . . . . . . . 5
3.1.2. Centralized Control Plane . . . . . . . . . . . . . . 5
3.2. Data Plane Scalability . . . . . . . . . . . . . . . . . 6
3.3. Gap Analysis of Existing Mechanisms . . . . . . . . . . . 6
4. Possible Optimizations . . . . . . . . . . . . . . . . . . . 7
4.1. Control Plane Optimization . . . . . . . . . . . . . . . 7
4.2. Data Plane Optimization . . . . . . . . . . . . . . . . . 9
5. Solution Evolution for Improved Scalability . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Virtual Private Networks (VPNs) have served the industry well as a
means of providing different groups of users with logically isolated
connectivity over a common network infrastructure. The VPN service
is provided with two network layers: the overlay and the underlay.
The underlay is responsible for establishing network connectivity and
managing network resources to meet the service requirement. The
overlay is used to distribute the membership and reachability
information of the tenants, and provide logical separation of service
Show full document text