BGP-LS Extensions for Segment Routing based Enhanced VPN
draft-dong-idr-bgpls-sr-enhanced-vpn-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)
|
IDR Working Group J. Dong
Internet-Draft Z. Hu
Intended status: Standards Track Huawei Technologies
Expires: May 7, 2020 November 4, 2019
BGP-LS Extensions for Segment Routing based Enhanced VPN
draft-dong-idr-bgpls-sr-enhanced-vpn-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. These applications require
better isolation and have more stringent performance requirements
than that can be provided with traditional overlay VPNs. An enhanced
VPN may be used for 5G transport network slicing, and will also be of
use in more generic scenarios. This document specifies BGP-LS based
mechanism with necessary extensions to advertise the information of
Segment Routing (SR) based virtual networks. These virtual networks
could be used as the underlay of enhanced VPN service. The proposed
mechanism is applicable to both segment routing with MPLS data plane
(SR-MPLS) and segment routing with IPv6 data plane (SRv6).
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 & Hu Expires May 7, 2020 [Page 1]
Internet-Draft BGP-LS Extensions for SR VPN+ 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. Advertisement of Transport Network Slice Definition . . . . . 3
2.1. Sub-TLVs of TNSD TLV . . . . . . . . . . . . . . . . . . 4
3. Advertisement of Network Topology and Resource Attributes . . 6
3.1. Intra-domain Network Topology Advertisement . . . . . . . 6
3.1.1. MTR based Topology Advertisement . . . . . . . . . . 6
3.1.2. Flex-Algo based Topology Advertisement . . . . . . . 7
3.2. Intra-domain Resource Information Advertisement . . . . . 8
3.3. Inter-Domain Topology and Resource Information
Advertisement . . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Driven largely by needs arising from the 5G mobile network, the
concept of network slicing has gained traction
[NGMN-NS-Concept][TS23501][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 [I-D.ietf-teas-enhanced-vpn], a transport network slice
is a virtual (logical) network with a particular network topology and
a set of shared or dedicated network resources, which are used to
provide the network slice consumer with the required connectivity,
Show full document text