[Teas] Review of draft-ietf-teas-5g-ns-ip-mpls

"Wubo (lana)" <lana.wubo@huawei.com> Sun, 03 December 2023 03:40 UTC

Return-Path: <lana.wubo@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 80085C14F5FE for <teas@ietfa.amsl.com>; Sat, 2 Dec 2023 19:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJUcQ0ww5ZCa for <teas@ietfa.amsl.com>; Sat, 2 Dec 2023 19:39:59 -0800 (PST)
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 63C6EC14F5F0 for <teas@ietf.org>; Sat, 2 Dec 2023 19:39:59 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SjXZJ4q6tz6K6bq for <teas@ietf.org>; Sun, 3 Dec 2023 11:38:16 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (unknown [7.191.160.241]) by mail.maildlp.com (Postfix) with ESMTPS id 2FE561400D2 for <teas@ietf.org>; Sun, 3 Dec 2023 11:39:57 +0800 (CST)
Received: from kwepemd100003.china.huawei.com (7.221.188.180) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Sun, 3 Dec 2023 03:39:56 +0000
Received: from kwepemd500002.china.huawei.com (7.221.188.104) by kwepemd100003.china.huawei.com (7.221.188.180) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Sun, 3 Dec 2023 11:39:54 +0800
Received: from kwepemd500002.china.huawei.com ([7.221.188.104]) by kwepemd500002.china.huawei.com ([7.221.188.104]) with mapi id 15.02.1258.028; Sun, 3 Dec 2023 11:39:54 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: 'TEAS WG' <teas@ietf.org>
Thread-Topic: Review of draft-ietf-teas-5g-ns-ip-mpls
Thread-Index: AdolmWcJvwKAP6qbRoeyrRoJrziefQ==
Date: Sun, 03 Dec 2023 03:39:54 +0000
Message-ID: <2380708ae06c49acb17af477ca1055a6@huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.84.85.134]
Content-Type: multipart/alternative; boundary="_000_2380708ae06c49acb17af477ca1055a6huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/dHlCnRrmEttKdY3GDzQo1PCYNkM>
Subject: [Teas] Review of draft-ietf-teas-5g-ns-ip-mpls
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 03 Dec 2023 03:40:05 -0000

Hi Authors, WG,

I have read draft-ietf-teas-5g-ns-ip-mpls and have several general comments:

1. On the mapping between IETF Network Slice Service SDP and 5G CE, this document and draft-5g-network-slice-application (5g-application) both provide some content. I think it would be more clear to list all 5G CE options in one document and avoid the inconsistency between the two documents. For example, Section 4 Overview of the Realization Model describes three options: VLAN, IP, and MPLS. However draft-5g-application has more options than these. This document says that 5G CEs have BGP protocol mapping, while Section 5.3 of draft-5g-application does not .
2. Section 6 Transport Planes Mapping Models introduces "tunnel group" or "transport planes'. Can you clarify how to manage the tunnel groups? Does tunnel group management also requires topology and resource allocation management? As I am wondering the difference between tunnel group management and NRP management. Per Section 4.2. Control Plane Network Resource Partition Mode of draft-ietf-teas-ns-ip-mpls, NRP has a mode of control plane without data plane encapsulation mechanism.
3. Section 3 5G Network Slicing Integration in Transport Networks defines various distributed CE-PE models which are not used in subsequent sections. Are these different models related to the implementation of QoS mapping, connectivity, or capacity planning? Could you add some text to reflect that?

Thanks,
Bo Wu