Re: [spring] more on IDs for slices

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Tue, 09 February 2021 14:45 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD153A0DCC; Tue, 9 Feb 2021 06:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 2vtG0tnFWT7v; Tue, 9 Feb 2021 06:45:47 -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 078933A0DC2; Tue, 9 Feb 2021 06:45:47 -0800 (PST)
Received: from fraeml744-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DZlwD2WSwz67Yss; Tue, 9 Feb 2021 22:42:04 +0800 (CST)
Received: from fraeml744-chm.china.huawei.com (10.206.15.225) by fraeml744-chm.china.huawei.com (10.206.15.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 9 Feb 2021 15:45:43 +0100
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by fraeml744-chm.china.huawei.com (10.206.15.225) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Tue, 9 Feb 2021 15:45:43 +0100
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.91]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0509.000; Tue, 9 Feb 2021 22:45:38 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "teas@ietf.org" <teas@ietf.org>, "spring@ietf.org" <spring@ietf.org>
CC: "apn@ietf.org" <apn@ietf.org>
Thread-Topic: more on IDs for slices
Thread-Index: Adb+XeqBDB3FzfnsQ0GCDGOfIWFeHwAk0TCg
Date: Tue, 09 Feb 2021 14:45:38 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE198BD1DC@DGGEML532-MBX.china.huawei.com>
References: <MWHPR02MB24647C04FCA5A256C216C42FD68F9@MWHPR02MB2464.namprd02.prod.outlook.com>
In-Reply-To: <MWHPR02MB24647C04FCA5A256C216C42FD68F9@MWHPR02MB2464.namprd02.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.176.18]
Content-Type: multipart/alternative; boundary="_000_4278D47A901B3041A737953BAA078ADE198BD1DCDGGEML532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/zl-sDKYChppM13IZAXX2DLhHDp0>
Subject: Re: [spring] more on IDs for slices
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2021 14:45:49 -0000

Dear Deborah,

Thank you very much for attracting people's attention on APN (Application-aware Networking) and having more discussions on this work to further clarify things. Thank you!

To all, please find more discussions in the APN mailing list (https://datatracker.ietf.org/wg/apn/about/). Please you are interest in this topic, please join us in the discussions. I have also copied the APN mailing list to make the subscribers of APN aware of these discussions happening here.

To us, the definition of a slice is not in the scope of APN.

APN is focused on developing a framework and set of mechanisms to derive, convey and use the APN attribute to allow for the implementation of fine-grain user (group)-, application (group)-, and service-level requirements at the network layer.

APN could be used to select TE paths, but it is not just about traffic engineering or traffic steering. It is about selecting next-hop paths in the network to route traffic onto links depending on the needs of the traffic. APN can also be used for the fine-granularity performance measurement and visualization within operator's network domain.

Best regards,
Shuping


From: spring [mailto:spring-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: Tuesday, February 9, 2021 5:04 AM
To: teas@ietf.org; spring@ietf.org
Subject: [spring] more on IDs for slices

Hi,

Not sure if you are aware, there was a BoF proposed on using an identifier to signal user requirements (APN) in a slice, APN BoF. It was decided it would be better to first have it further discussed at IETF110's RTGWG as it would allow for a broader coverage:
https://www.ietf.org/blog/ietf110-bofs/

Considering the current discussion in spring and the work already on-going in teas on IDs and "what is a slice", and to help focus the discussion at the meeting, I wanted to bring the following drafts to your attention. I have asked the authors to help us understand the gaps with the on-going work not being addressed and what new work is needed. The authors have done a lot of work, this is just a selection:

https://www.ietf.org/archive/id/draft-peng-apn-scope-gap-analysis-00.txt
https://www.ietf.org/archive/id/draft-li-apn-framework-01.txt
https://www.ietf.org/archive/id/draft-li-apn-problem-statement-usecases-01.txt

If you search documents on APN, you will find more.

Happy reading,
Deborah