Re: [Teas] Comments on draft-bestbar-teas-ns-packet-00

"Dongjie (Jimmy)" <> Fri, 20 November 2020 07:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BC0083A19E6; Thu, 19 Nov 2020 23:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VXWyMM1nI1ke; Thu, 19 Nov 2020 23:36:33 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 18F4A3A19CD; Thu, 19 Nov 2020 23:36:33 -0800 (PST)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4CcpGM2Sg4z67FYX; Fri, 20 Nov 2020 15:34:35 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Fri, 20 Nov 2020 08:36:29 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 20 Nov 2020 15:36:27 +0800
Received: from ([]) by ([]) with mapi id 15.01.1913.007; Fri, 20 Nov 2020 15:36:26 +0800
From: "Dongjie (Jimmy)" <>
To: Tarek Saad <>, "" <>
CC: "" <>
Thread-Topic: [Teas] Comments on draft-bestbar-teas-ns-packet-00
Thread-Index: Ada4yFzQlsTL3WHCS6W4IaR+h6AiDQCRxtaJAJzmZBA=
Date: Fri, 20 Nov 2020 07:36:26 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_d5600bf14f474769929e8915ecbe7aeehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Teas] Comments on draft-bestbar-teas-ns-packet-00
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 20 Nov 2020 07:36:40 -0000

Hi Tarek,

Thanks a lot for your reply. Please see some further comments inline with [Jie]:

From: Teas [] On Behalf Of Tarek Saad
Sent: Sunday, November 15, 2020 1:24 PM
To: Dongjie (Jimmy) <<>>;<>
Subject: Re: [Teas] Comments on draft-bestbar-teas-ns-packet-00

Thanks Jie for your review and your comments. Please see inline for some responses from the authors.

From: Teas <<>> on behalf of "Dongjie (Jimmy)" <<>>
Date: Thursday, November 12, 2020 at 2:52 AM
To: "<>" <<>>
Cc: "<>" <<>>
Subject: [Teas] Comments on draft-bestbar-teas-ns-packet-00

Hi authors,

I've read draft-bestbar-teas-ns-packet-00, please find some review comments from my side:

To my understanding, the mechanism described in this document aligns with the VPN+ framework described in draft-ietf-teas-enhanced-vpn. More specifically, this document describes different approaches of reserving dedicated or shared network resources for logical (or virtual) networks to provide network slicing. It also describes the mechanisms to steer traffic on the specific network resources allocated for the network slices. Thus it would be reasonable to reference draft-ietf-teas-enhanced-vpn in this document.
[TS]: the draft proposes a solution on how shared network resource(s) can be allocated to different slice(s) - in control and/or data plane. This solution would be able to cater to enhanced VPN when a slice is mapped to 1 VPN. However, the solution the draft present covers other variant ranging from (M VPNs mapping to N slices). We can add some text highlighting how this solution can be used to realize an enhanced VPN service in a later version.

[Jie] From this description, it shows that the a consistent view about the relationship between the terms VPN, network slice and enhanced VPN is needed. There is some description about this in the introduction of draft-ietf-teas-enhanced-vpn, review and suggestion are welcome.

Section 4 describes three approaches for resource partitioning. First please note that the list a), b) and c) is not in the same order as sections 4.1, 4.2 and 4.3. Then I'm a little confused with this classification. If my understanding is correct, The difference is whether the resource is reserved in data plane or not (i.e. hard or soft isolation).
[TS]: thanks, we will fix the list order to be in line with the TOC.

While no matter which approach is used, the resource reservation state needs to be maintained in control plane (either in a central controller or in the control plane of devices). And the resource sharing described in 4.2 between multiple slices within a group is also possible with the data plane based resource partitioning. Thus I'm not sure "data plane only" and "control plane only" are the appropriate terms here. How about using "data plane resource partitioning" and "control plane resource reservation" instead?

After reading section 4.3, my understanding is this subsection actually talks about two things of a network slice: resource reservation and topology customization. Then perhaps it should not be listed as the third approach for resource partitioning/reservation. The combination of the resource and topology attributes may be described in a separate section.
[TS] In the "Data Plane Network Resource Slicing" (Section 4.1) approach, there is no per-slice resource reservation state maintained in the control-plane. In fact, some path placement techniques would select the best path without consideration to the network state or utilization (e.g. IGP based path selection, SR flex-algo path, or LDP).. Those would map traffic on the best selected path (usually leveraging ECMP) but without any network state reservations. Section 4.1 covers enhancing those usecases to enable data-plane slicing along such paths. In the "Control Plane Network Resource Slicing" (Section 4.2) approach, the control-plane (be it on the devices or on some central controller) maintains per-slice resource reservation state. And this facilitates Slice-aware TE path placement. The approach discussed in Section 4.3 ties both of the approaches together.

[Jie] Thanks for your explanation. Then my understanding is with "data plane network resource slicing" in this document, path computation and selection is based on a common topology (constraints), which means the network slices need to share the same topology attribute. This presumption may be true for some of the slices, while it may be difficult to ensure that all the network slices have the same topology. Thus a more generic approach is to allow either topology sharing or customization between network slices, and the data plane resource can be either dedicated or shared. Then "data plane resource slicing" and "control plane slicing" in this document can be seen as the special cases.

In section 5.1, it mentions a network slice may be realized using a network slice service Layer, and a device/resource Layer. In management plane, this separation of functionality can be seen in the context of RFC 8309 by considering that the NBI described here is a customer service interface, which is mapped down to network and device configuration interfaces. The term network slice service layer aligns with the NS-DT documents that a network slice is a service provided to a consumer. Then one question is: can the device/resource layer also be called a network slice? Using the same term for both the service layer and the resource layer may cause ambiguity. Maybe it is better to provide a dedicated term for the resource layer in the network slice context? For example, in draft-ietf-teas-enhanced-vpn, the virtual underlay network is called a VTN.
[TS] The service definition of the "network slice" is outside the scope of this document and (as you are well aware) is discussed in detail in various other documents. The only assumption that this document makes is that there is some controller(s) that would translate this service layer intent to a network wide consistent slice per-hop definition that is provisioned on slice-capable nodes. The slice per-hop definition is required to enforce the proper per slice treatment onto slice traffic on each hop.

[Jie] I think we agree that in NS-DT the term "network slice" refers to the service layer. I understand the functions described in this document and its relationship with the network slice service layer, I'm just not sure whether the same term could be used for both the service layer and the resource layer, as they may have different characteristics and granularity.

Section 5.2.1 describes two options for Slice data plane selector, and analyzed the scalability challenges with the first approach. This section is relevant to draft-dong-spring-sr-for-enhanced-vpn, which describes the mechanism of using different SR SIDs or SRv6 Locators to identify the nodes/links and the resources allocated to different VTNs. And the scalability considerations for VPN+ are described in draft-dong-teas-enhanced-vpn-vtn-scalability, which provides the scalability analysis and optimizations in both the control plane and the data plane. For IPv6 data plane, one approach to carry the VTN identifier in data packet is described in draft-dong-6man-enhanced-vpn-vtn-id. My understanding to this section is it may aim to cover the native IP and legacy MPLS cases? Anyway, some coordination between these drafts would be helpful.
TS] The primary motivation behind this document is to offer a solution that is agnostic to the path control technology used in the slicing domain and uses a model that caters to a variety of IP (including native IP and SRv6) and MPLS data-plane slice selectors to provide slice specific treatment on a given device. Operators can choose any specific slice selector that suits their deployment - section 5.2.1 provides the considerations for picking a suitable slice selector. And yes, always welcome to coordinate with relevant drafts.

[Jie] Understood. Look forward to the coordination with the data plane related drafts.

Section 6 provide some general considerations about routing protocol extensions. For this part you may refer to the VTN and VPN+ drafts in LSR and IDR WG, which provides the control plane solutions with different scalability and flexibility characteristics. Comments are always welcomed.

[TS] Ack, thanks. We will make sure that there is coordination with relevant drafts as we make progress on Slice-aware TE specific control plane enhancements.
Hope this helps.

[Jie] Good to know this, thanks.

Best regards,

Tarek (for the authors)

Hope this helps.

Best regards,