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

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Sun, 24 January 2021 07:50 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7DA03A0FD2; Sat, 23 Jan 2021 23:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 HVoL6YWiYhYt; Sat, 23 Jan 2021 23:50:34 -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 59F303A0FD1; Sat, 23 Jan 2021 23:50:34 -0800 (PST)
Received: from fraeml743-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DNlQ73GCQz67g0V; Sun, 24 Jan 2021 15:44:47 +0800 (CST)
Received: from fraeml737-chm.china.huawei.com (10.206.15.218) by fraeml743-chm.china.huawei.com (10.206.15.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Sun, 24 Jan 2021 08:50:29 +0100
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Sun, 24 Jan 2021 08:50:28 +0100
Received: from DGGEML512-MBX.china.huawei.com ([169.254.2.224]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0509.000; Sun, 24 Jan 2021 15:50:22 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: tom petch <ietfc@btconnect.com>, draft-per-app-networking-considerations <draft-per-app-networking-considerations@ietf.org>
CC: "apn@ietf.org" <apn@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: [Apn] A new draft on APN for your review, thank you!
Thread-Topic: [Apn] A new draft on APN for your review, thank you!
Thread-Index: AdbSj5OZJp0yHZz0SGiKnve9MVZvEAdzGJnwAEkAdiAAKPws4A==
Date: Sun, 24 Jan 2021 07:50:22 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE19821F72@dggeml512-mbx.china.huawei.com>
References: <4278D47A901B3041A737953BAA078ADE196CCA02@DGGEML532-MBX.china.huawei.com>, <4278D47A901B3041A737953BAA078ADE19806DB2@DGGEML532-MBX.china.huawei.com> <AM7PR07MB624864589E9149E7FDC8C688A0BF0@AM7PR07MB6248.eurprd07.prod.outlook.com>
In-Reply-To: <AM7PR07MB624864589E9149E7FDC8C688A0BF0@AM7PR07MB6248.eurprd07.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.179.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/smn5SEU041STXGm7GhlOE5cMLBU>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 07:50:37 -0000

Dear Tom,

Thank you for your interest! 

First of all, APN stands for Application-aware Networking

I had attached a APN BoF proposal document in my last email but probably it was too big to be delivered successfully. The APN6 was also introduced in this draft in the intarea WG (https://tools.ietf.org/html/draft-per-app-networking-considerations). Sorry for any confusions caused. 

Please find the APN BoF proposal in the IETF wiki for more information. 
https://trac.tools.ietf.org/bof/trac/wiki/WikiStart

The archived discussions in this APN mailing list can be found here. 
https://mailarchive.ietf.org/arch/browse/apn/

To subscribe the APN Mailing list,
https://www.ietf.org/mailman/listinfo/apn

Here are some relevant drafts and materials for your reference. 

*	Scope & Gap analysis
https://tools.ietf.org/html/draft-peng-apn-scope-gap-analysis
*	Problem statement & Use cases
https://tools.ietf.org/html/draft-li-apn-problem-statement-usecases
https://tools.ietf.org/html/draft-liu-apn-edge-usecase
https://tools.ietf.org/html/draft-zhang-apn-acceleration-usecase
https://tools.ietf.org/html/draft-yang-apn-sd-wan-usecase
*	Framework
https://datatracker.ietf.org/doc/draft-li-apn-framework/
*	Security & Privacy
https://datatracker.ietf.org/doc/draft-peng-apn-security-privacy-consideration
*	APN Community
https://github.com/APN-Community
*	Per-Application Networking Considerations
https://tools.ietf.org/html/draft-per-app-networking-considerations

Thank you! 

Best regards, 
Shuping

> -----Original Message-----
> From: tom petch [mailto:ietfc@btconnect.com]
> Sent: Saturday, January 23, 2021 8:09 PM
> To: Pengshuping (Peng Shuping) <pengshuping@huawei.com>;
> draft-per-app-networking-considerations
> <draft-per-app-networking-considerations@ietf.org>
> Cc: apn@ietf.org; int-area@ietf.org; rtgwg@ietf.org
> Subject: Re: [Apn] A new draft on APN for your review, thank you!
> 
> From: Int-area <int-area-bounces@ietf.org> on behalf of Pengshuping (Peng
> Shuping) <pengshuping@huawei.com>
> Sent: 22 January 2021 02:08
> 
> Dear authors,
> 
> We have updated the APN BoF Proposal as attached. The suggestions in your
> draft and the
> 
> <tp>
> 
> Whatever APN may stand for!  I looked at the I-D and the Abstract uses
> APN with no explanation of what it is:-(  It needs expanding on first use and
> while I could read on and perhaps find an explanation yet the idea is that the
> Abstract tells readers whether or not this is of interest to them and this
> Abstract does not.  The rest of the I-D may be clearer but I am not gong to
> spend time finding out:-)
> 
> Tom Petch
> 
> discussions with you offline inspired us a lot. The support of the user/app
> group is explicitly shown in the text although it was implicitly included. We
> have made a lot of efforts on clarifying the scope of the work, introducing
> the basic solution, and describing the concrete use case. Please advise
> whether we are clear now and how we can improve further, especially on
> the privacy concerns. Thank you!
> 
> This posted draft,
> https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis,
> would be able to give you more complete information. Please also refer to
> the recent discussions in the archives
> https://mailarchive.ietf.org/arch/browse/apn/ if you have not subscribed
> the APN mailing list yet. Based on discussions and suggestions we received,
> we will update this draft accordingly. Your reviews and comments will be
> very much appreciated.
> 
> Thank you!
> 
> Best regards,
> Shuping
> 
> 
> 
> From: Apn [mailto:apn-bounces@ietf.org] On Behalf Of Pengshuping (Peng
> Shuping)
> Sent: Tuesday, December 15, 2020 11:12 AM
> To: apn@ietf.org; rtgwg@ietf.org
> Subject: [Apn] 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.
> 
>