IETF Logo Mail Archive

Re: [Idr] draft-dong-idr-flowspec-network-slice-ts-01 (1/27 to 2/10)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 10 February 2023 10:12 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DFB8C169527 for <idr@ietfa.amsl.com>; Fri, 10 Feb 2023 02:12:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 jBuT3ZZ__aht for <idr@ietfa.amsl.com>; Fri, 10 Feb 2023 02:12:38 -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 A6028C14CF05 for <idr@ietf.org>; Fri, 10 Feb 2023 02:12:38 -0800 (PST)
Received: from lhrpeml500001.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4PCqDk5G7bz67lBv for <idr@ietf.org>; Fri, 10 Feb 2023 18:08:06 +0800 (CST)
Received: from kwepemi100015.china.huawei.com (7.221.188.125) by lhrpeml500001.china.huawei.com (7.191.163.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.17; Fri, 10 Feb 2023 10:12:34 +0000
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi100015.china.huawei.com (7.221.188.125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Fri, 10 Feb 2023 18:12:32 +0800
Received: from kwepemi500017.china.huawei.com ([7.221.188.110]) by kwepemi500017.china.huawei.com ([7.221.188.110]) with mapi id 15.01.2375.034; Fri, 10 Feb 2023 18:12:32 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, Susan Hares <shares@ndzh.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] draft-dong-idr-flowspec-network-slice-ts-01 (1/27 to 2/10)
Thread-Index: AQHZPTVYj9TWLzepfE+TlvtC9QCcJq7H8q7Q
Date: Fri, 10 Feb 2023 10:12:32 +0000
Message-ID: <f47a4a497cfb4d78a4ee46a287208519@huawei.com>
References: <BYAPR08MB4872F603F8FD6C7304064007B3CC9@BYAPR08MB4872.namprd08.prod.outlook.com> <FB5043AD-1074-4793-A0C1-5D551330FCF4@tsinghua.org.cn>
In-Reply-To: <FB5043AD-1074-4793-A0C1-5D551330FCF4@tsinghua.org.cn>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: multipart/alternative; boundary="_000_f47a4a497cfb4d78a4ee46a287208519huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/MZc1OlJooATQVodpt2gv8fYoFqM>
Subject: Re: [Idr] draft-dong-idr-flowspec-network-slice-ts-01 (1/27 to 2/10)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2023 10:12:43 -0000

Hi Aijun,

Thanks for your support and valuable comments. Please see some replies inline:

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Aijun Wang
Sent: Friday, February 10, 2023 5:50 PM
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Subject: Re: [Idr] draft-dong-idr-flowspec-network-slice-ts-01 (1/27 to 2/10)

Yes/Support its adoption.

After discussing with the authors, some suggestions to the document for future updates:
1) The descriptions of section 3.1.1 and 3.1.2 are not easy to be understood. Will it be more clearer to clarify them into the following two parts:
A: When the packet doesn’t include NRP-ID information
B: When the packet includes NRP-ID information

As you suggested, in next revision we could polish the text to clarify the cases where the packets carry an NRP-ID, and the cases where the packets does not carry NRP-ID.

2) Should the action for encapsulating NRP-ID be independent from the traffic steering BE or TE mode?

The encapsulating NRP-ID action is applicable to the case of steering traffic into BE paths of an NRP.  We will clarify it in next revision.

3) Section 3.2 can also be clarified and described in similar way that described in 1)

OK. Will improve the readability in next version.

After the above clarifications, will the document be more easier to be understood?
Yes, thanks again for the suggestions.
Best regards,
Jie

Aijun Wang
China Telecom


On Jan 27, 2023, at 22:06, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:

This begins 2 Week WG adoption call for
draft-dong-idr-flowspec-network-slice-ts-01.txt
(1/27/2023 to 2/10/2023).

The authors should respond to this message indicating whether
they know of any IPR.

The IDR WG should consider if this addition to
Flow specification v2 is useful for networks
Deploying network slice technology.

Cheerily, Sue



_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr

v2.46.0 | Report a Bug | By Email | System Status