SRv6 and MPLS interworking for VPN service
draft-pzm-bess-spring-interdomain-vpn-02
BESS WG Z. Zhang
Internet-Draft S. Peng
Intended status: Standards Track G. Mirsky
Expires: February 15, 2021 Y. Wang
ZTE Corporation
August 14, 2020
SRv6 and MPLS interworking for VPN service
draft-pzm-bess-spring-interdomain-vpn-02
Abstract
This document describes a method to achieve an inter-domain
connection for a VPN (Virtual Private Network) service.
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 February 15, 2021.
Copyright Notice
Copyright (c) 2020 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.
Zhang, et al. Expires February 15, 2021 [Page 1]
Internet-Draft BESS SPRING inter-domain VPN August 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 2
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. Theory of operation . . . . . . . . . . . . . . . . . . . . . 3
3.1. SRv6 to SR-MPLS domain signaling . . . . . . . . . . . . 3
3.2. SR-MPLS to SRv6 domain signaling . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
[I-D.agrawal-spring-srv6-mpls-interworking] describes SRv6 and MPLS/
SR-MPLS interworking and co-existence procedures. The document
leverages the function defined in
[I-D.ietf-spring-srv6-network-programming] to give guidance to the
forwarding in routers.
[RFC4364] describes a method by which a Service Provider may use an
IP backbone to provide IP Virtual Private Networks (VPNs) for its
customers. When SRv6 and SR-MPLS are co-existed in the backbone,
controller or a control plane, for example, using BGP, should be used
to instantiate the VPN service as described in
[I-D.agrawal-spring-srv6-mpls-interworking].
In case of option B inter-domain interconnection [RFC4364], only ASBR
needs to do the stitching work between two ASes. Thus PEs in SRv6
and SR-MPLS domains do not have to support both SRv6 and SR-MPLS
functions. This document discusses the use of BGP for achieving VPN
service through option B defined in [RFC4364] across a backbone that
includes SRv6 and SR-MPLS domains.
2. Conventions used in this document
2.1. Terminology
ASBR - Autonomous System Boundary Router
PE - Provider's Equipment
AS - Autonomous System
Zhang, et al. Expires February 15, 2021 [Page 2]
Internet-Draft BESS SPRING inter-domain VPN August 2020
SR - Segment Routing
SRv6 - Segment Routing over IPv6 data plane
SR-MPLS - Segment Routing over MPLS data plane
SID - Segment Identifier
IMET - Inclusive Multicast Ethernet Tag
2.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
Show full document text