Segment Routing for Enhanced VPN Service
draft-dong-spring-sr-for-enhanced-vpn-04
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-07-01
|
|
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)
|
Network Working Group J. Dong
Internet-Draft S. Bryant
Intended status: Standards Track Huawei Technologies
Expires: January 2, 2020 T. Miyasaka
KDDI Corporation
Y. Zhu
China Telecom
F. Qin
Z. Li
China Mobile
July 1, 2019
Segment Routing for Enhanced VPN Service
draft-dong-spring-sr-for-enhanced-vpn-04
Abstract
Enhanced VPN (VPN+) is an enhancement to VPN technology to enable it
to support the needs of new applications, particularly applications
that are associated with 5G services. These applications require
better isolation from both control and data plane's perspective and
have more stringent performance requirements than can be provided
with overlay VPNs. The characteristics of an enhanced VPN as
perceived by its tenant needs to be comparable to those of a
dedicated private network. This requires tight integration between
the overlay VPN and the underlay network topology and resources in a
scalable manner. An enhanced VPN may form the underpinning of 5G
network slicing, but will also be of use in its own right. This
document describes the use of segment routing based mechanisms to
provide the enhanced VPN service with required network topology and
resources. The overall mechanism of using segment routing to provide
enhanced VPN service is also described. The proposed mechanism is
applicable to both SR with MPLS data plane and SR with IPv6 data
plane (SRv6).
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
Dong, et al. Expires January 2, 2020 [Page 1]
Internet-Draft SR for VPN+ July 2019
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 January 2, 2020.
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4
3. Segment Routing with Topology and Resource Awareness . . . . 4
3.1. SR-MPLS . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. SRv6 . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Virtual Network Topology and Resource Computation . . . . 8
5.2. Network Resource and SID Allocation . . . . . . . . . . . 9
5.3. Construction of SR Virtual Networks . . . . . . . . . . . 11
5.4. VPN Service to SR Virtual Network Mapping . . . . . . . . 12
5.5. Virtual Network Visibility to Customer . . . . . . . . . 13
6. Benefits of the Proposed Mechanism . . . . . . . . . . . . . 13
7. Service Assurance . . . . . . . . . . . . . . . . . . . . . . 14
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
Show full document text