Re: [dispatch] APN presentation in DISPATCH on Monday

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Thu, 11 March 2021 03:09 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31BD23A091B; Wed, 10 Mar 2021 19:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 cWUXMlvELeOt; Wed, 10 Mar 2021 19:09:39 -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 6517F3A0907; Wed, 10 Mar 2021 19:09:39 -0800 (PST)
Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Dwty32Cbmz67cgg; Thu, 11 Mar 2021 11:01:31 +0800 (CST)
Received: from fraeml710-chm.china.huawei.com (10.206.15.59) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 11 Mar 2021 04:09:36 +0100
Received: from DGGEML421-HUB.china.huawei.com (10.1.199.38) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Thu, 11 Mar 2021 04:09:35 +0100
Received: from DGGEML512-MBX.china.huawei.com ([169.254.2.49]) by dggeml421-hub.china.huawei.com ([10.1.199.38]) with mapi id 14.03.0513.000; Thu, 11 Mar 2021 11:09:06 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
CC: "apn@ietf.org" <apn@ietf.org>
Thread-Topic: APN presentation in DISPATCH on Monday
Thread-Index: AdcSFzZu8w2qQ9elQ62TC2X0SJq0egECd0mA
Date: Thu, 11 Mar 2021 03:09:30 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE199A3224@dggeml512-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.182.152]
Content-Type: multipart/alternative; boundary="_000_4278D47A901B3041A737953BAA078ADE199A3224dggeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/y0EAc-fB2bKwB4lZ3AUoTqEfSkQ>
Subject: Re: [dispatch] APN presentation in DISPATCH on Monday
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2021 03:09:42 -0000

Hi Folks,

Many thanks for your very valuable discussions and feedback on the APN presentation in the ARTAREA on Monday!

When going through the discussions in the Jabber room, we found that some similar questions have been frequently asked, so we summarized a list of FAQs as below to further clarify the confusions and concerns. Your review and feedback will be very much welcomed and appreciated. Thank you!

1. Are there any applications that can benefit from APN?
I would like to ask how many of us have experienced the Meetecho issues in this IETF and the virtual ones before. This is one of the applications that can benefit from APN. :)

In this IETF, we had a hackathon "Application-aware G-SRv6 networking", which shows the improvements that can be achieved with APN, using which the traffic is steered into the appropriate SRv6 path [1]. The results are going to be presented and demonstrated in the INFOCOM2021. There was also the first demonstration of APN in the INFOCOM2020 [2].

[1]https://github.com/APN-Community/IETF-110-Hackathon-Demo/blob/master/Application-aware_G-SRv6_networking__Demo_and_Test.pdf
[2]https://ieeexplore.ieee.org/abstract/document/9162934

2. How APN can help resolve the QoE issues?
As shown in the APN demonstrations, we can see the differences/improvements which APN can make in the network. QoE is complex and has many impacting factors including the terminal, access, and network. APN aims to provide ways to improve the QoE within the network.

3. Who is to set the APN attribute?
It is the network edge device such as CPE (Customer Premises Equipment) not the application.

4. How to set the APN attribute?
There are many possible ways that can be used to classify the traffic flow at the network edge, e.g., the N-tuples as defined in the MEF70 and the AI technologies. An APN attribute can be derived by using the match items published in MEF70 as well as the access port in the edge device.

5. How the APN attribute is used in the network?
The APN attribute is carried in the data packet's header, and it can be used in the various nodes/service functions along the network path to enforce the policies on the differentiated traffic flow, e.g.,
1) at the headend to steer into corresponding path satisfying SLAs
2) at the midpoint to collect corresponding performance measurement data
3) at the service function to execute particular policies

Best regards,
Shuping


From: Pengshuping (Peng Shuping)
Sent: Saturday, March 6, 2021 7:28 AM
To: 'dispatch@ietf.org' <dispatch@ietf.org>
Cc: apn@ietf.org
Subject: APN presentation in DISPATCH on Monday

Hi Folks,

Thanks to the DISPATCH Chairs and the ADs, we are going to present APN (Application-aware Networking) in the DISPATCH working group at 13:00-15:00 (UTC+1) Monday.

APN is focused on developing a framework and set of mechanisms to derive, convey and use an attribute information to allow for the implementation of fine-grain user (group)-, application (group)-, and service-level requirements at the network layer. APN works within a limited trusted domain, which typically is defined as a service provider's limited domain in which MPLS, VXLAN, SR/SRv6 and other tunnel technologies are adopted to provide services.

In the presentation, we would like to introduce the concepts, clarify the scope, attract people to understand and discuss the topic, and collect feedback and suggestions on this work, to further address the main concerns that were raised by the IESG.

For the ARTers, we would like to especially know about the new applications' trends and requirements on the network, and how the network can serve these groups/types of applications better.

Please find the latest version of the key draft, clarifying the scope and the gap analysis.
https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis-01

We have been discussing in the APN mailing list regarding the various aspects of APN. If you have not subscribed, you are very welcome to subscribe. You can also find the archived discussions.
https://datatracker.ietf.org/wg/apn/about/

More information about APN can be found here.
https://github.com/APN-Community

Best Regards,
Shuping