Re: [Apn] A new draft on APN for your review, thank you!

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Wed, 20 January 2021 06:18 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 631273A0408; Tue, 19 Jan 2021 22:18:08 -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 JSr3GD8SEFPy; Tue, 19 Jan 2021 22:18:06 -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 17D733A03FA; Tue, 19 Jan 2021 22:18:06 -0800 (PST)
Received: from fraeml713-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DLFYZ3Q3xz67dTN; Wed, 20 Jan 2021 14:12:34 +0800 (CST)
Received: from fraeml713-chm.china.huawei.com (10.206.15.32) by fraeml713-chm.china.huawei.com (10.206.15.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 20 Jan 2021 07:18:03 +0100
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by fraeml713-chm.china.huawei.com (10.206.15.32) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Wed, 20 Jan 2021 07:18:02 +0100
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.117]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0509.000; Wed, 20 Jan 2021 14:17:57 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "apn@ietf.org" <apn@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Thread-Topic: A new draft on APN for your review, thank you!
Thread-Index: AdbSj5OZJp0yHZz0SGiKnve9MVZvEAcTh4oQ
Date: Wed, 20 Jan 2021 06:17:56 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE197FAE1A@DGGEML532-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.153.194.142]
Content-Type: multipart/alternative; boundary="_000_4278D47A901B3041A737953BAA078ADE197FAE1ADGGEML532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/oNYKxkWAQ1voBNR-dXJUlIkvUB4>
Subject: Re: [Apn] A new draft on APN for your review, thank you!
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 20 Jan 2021 06:18:09 -0000

Dear all,

In the MEF 70 “SD-WAN Service Attribute and Services”, Table 4 on Page 36 has defined the fields (from layer 2 through layer 4) which are expected to be able to match against ingress IP Packets. APPID is explicitly listed as a criterion.

“The APPID Policy Criterion provides the ability for the Service Provider to define and name both simple and complex matches. These can include standard matches available to all of the Service Provider’s Subscribers from a catalog and/or custom matches developed by the Service Provider by agreement with a particular Subscriber.”

https://www.mef.net/wp-content/uploads/2019/07/MEF-70.pdf

Is there anybody who knows more about the details about this criterion and its implementations of the catalog and the interactions? How does the standard match and the custom match work in the real system? What are the key elements in the system? How do they interact?

Many thanks!

Best regards,
Shuping


From: Pengshuping (Peng Shuping)
Sent: Tuesday, December 15, 2020 11:12 AM
To: apn@ietf.org; rtgwg@ietf.org
Subject: A new draft on APN for your review, thank you!


Dear all,



A new draft on APN has been posted, https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis.



In this draft, we clarified the scope of the APN work in IETF, introduced an example use case and the basic solution. Moreover, we compared with the existing “similar” work/solutions and did corresponding gap analysis.



Your review and comments are very much appreciated. Thank you!



Best regards,

Shuping





A new version of I-D, draft-peng-apn-scope-gap-analysis-00.txt

has been successfully submitted by Shuping Peng and posted to the IETF repository.



Name:              draft-peng-apn-scope-gap-analysis

Revision: 00

Title:                 APN Scope and Gap Analysis

Document date:      2020-12-16

Group:              Individual Submission

Pages:              11

URL:            https://www.ietf.org/archive/id/draft-peng-apn-scope-gap-analysis-00.txt

Status:         https://datatracker.ietf.org/doc/draft-peng-apn-scope-gap-analysis/

Htmlized:       https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis

Htmlized:       https://tools.ietf.org/html/draft-peng-apn-scope-gap-analysis-00





Abstract:

   The APN work in IETF is focused on developing a framework and set of

   mechanisms to derive, convey and use an identifier to allow for

   implementing fine-grain user-, application-, and service-level

   requirements at the network layer.  This document describes the scope

   of the APN work and the solution gap analysis.