[Teas] Some comments on draft-ali-teas-spring-ns-building-blocks

"Dongjie (Jimmy)" <jie.dong@huawei.com> Mon, 02 August 2021 09:07 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F10F33A1497; Mon, 2 Aug 2021 02:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxxYgqw-OdFN; Mon, 2 Aug 2021 02:07:07 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92E0C3A1496; Mon, 2 Aug 2021 02:07:07 -0700 (PDT)
Received: from fraeml734-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GdXFD5gD9z6F7xx; Mon, 2 Aug 2021 17:06:56 +0800 (CST)
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by fraeml734-chm.china.huawei.com (10.206.15.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Mon, 2 Aug 2021 11:07:04 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme754-chm.china.huawei.com (10.3.19.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 2 Aug 2021 17:07:02 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2176.012; Mon, 2 Aug 2021 17:07:02 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "draft-ali-teas-spring-ns-building-blocks@ietf.org" <draft-ali-teas-spring-ns-building-blocks@ietf.org>
CC: TEAS WG <teas@ietf.org>
Thread-Topic: Some comments on draft-ali-teas-spring-ns-building-blocks
Thread-Index: AdeHe6JjiZpTuN7ZShGi+jdd9/G4Ig==
Date: Mon, 02 Aug 2021 09:07:02 +0000
Message-ID: <53039d56100543d7ae43e9d41ca3fc27@huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.153.194.116]
Content-Type: multipart/alternative; boundary="_000_53039d56100543d7ae43e9d41ca3fc27huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/x3WK9JRLyIWg3n-fj1kd8eOQbNI>
Subject: [Teas] Some comments on draft-ali-teas-spring-ns-building-blocks
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 09:07:10 -0000

Hi authors,

Thanks for the presentation in the TEAS session in last week. Here are some comments on this draft:


1.      As discussed on the TEAS meeting, the terminologies in several drafts related to network slicing realization will be aligned, thus it is suggested the terminology in this document also aligns with the "new term" to be proposed.


2.      As this document lists the SR technologies which can be used for network slice realization in SR networks, the suggestion is it should also describe and reference draft-ietf-spring-resource-aware-segments and draft-ietf-spring-sr-for-enhanced-vpn which specifies the extensions to SR segments and the mechanisms to provide SR based VTNs.



3.      Section 8 of this document describes the "stateless network slice ID" concept and the mechanisms with different data planes. The general mechanism of introducing dedicated VTN identifier in data packet for per-VTN packet processing was described in draft-dong-teas-enhanced-vpn-vtn-scalability, thus there is some overlap in this part which needs to be solved in future versions.


Best regards,
Jie