[Apn] Problem statement

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Thu, 04 May 2023 01:53 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: apn@ietfa.amsl.com
Delivered-To: apn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFCE5C151B37 for <apn@ietfa.amsl.com>; Wed, 3 May 2023 18:53:53 -0700 (PDT)
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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 h9bdo08P41iD for <apn@ietfa.amsl.com>; Wed, 3 May 2023 18:53:51 -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 A2CE4C15171E for <apn@ietf.org>; Wed, 3 May 2023 18:53:51 -0700 (PDT)
Received: from lhrpeml100002.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4QBcJM560mz67gR6 for <apn@ietf.org>; Thu, 4 May 2023 09:52:19 +0800 (CST)
Received: from canpemm500007.china.huawei.com (7.192.104.62) 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.23; Thu, 4 May 2023 02:53:48 +0100
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm500007.china.huawei.com (7.192.104.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Thu, 4 May 2023 09:53:46 +0800
Received: from canpemm500008.china.huawei.com ([7.192.105.151]) by canpemm500008.china.huawei.com ([7.192.105.151]) with mapi id 15.01.2507.023; Thu, 4 May 2023 09:53:46 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "apn@ietf.org" <apn@ietf.org>
Thread-Topic: Problem statement
Thread-Index: Adl+J33SOEYjCPzjRXyHXvv/CLDBUw==
Date: Thu, 04 May 2023 01:53:45 +0000
Message-ID: <484bb9971aff4810ae45a756e849420a@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.153.176.106]
Content-Type: multipart/alternative; boundary="_000_484bb9971aff4810ae45a756e849420ahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/e7BQn4hDXiHltDqjheF3QbQ6XVA>
Subject: [Apn] Problem statement
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Application-aware Networking <apn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apn>, <mailto:apn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apn/>
List-Post: <mailto:apn@ietf.org>
List-Help: <mailto:apn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apn>, <mailto:apn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 May 2023 01:53:53 -0000

Hi all,

We now start working to craft a problem statement and trying to clarify the problem space to be addressed. The following text describing the problem was produced while talking with people during IETF116 and other activities later. Maybe we could take this as a starting point. Your comments and suggestions are appreciated.

The text is also uploaded in Github.
https://github.com/APN-Github/Problem-statement

================

In a network operator controlled domain, the ingress edge devices usually have access to much richer information, such as VLAN/QinQ, VPN, and access interface, which is used to classify the packets into fine granular virtual groups of flows at the edge. However, after the packets enter the network operator's domain, all such information is lost together with the continuous fine granularity within the network. Indeed, the information is mapped into small fields like DSCP (6 bits) or MPLS EXP (3 bits). However, such small fields are only able to provide relatively coarse grained QoS treatment. The packet treatments needed may vary at different parts of the packet's path within the domain, and enough information is needed to determine these treatments. Thus, the continuous fine grained network services within the network domain cannot be provided efficiently. This information can be carried directly in the packet or achieved through a mapping from an opaque tag. Existing protocols such as SFC/NSH, SR/SRv6, MPLS, VXLAN, and IPv6, can be taken as implementation basis, but in each case the protocol may need extensions.

=================

Best Regards,
Shuping