Re: [Apn] Application-Aware Networking (APN) focused interim

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Fri, 21 May 2021 10:25 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 AA7163A22D2; Fri, 21 May 2021 03:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, 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 fEfZkL9alILw; Fri, 21 May 2021 03:25:11 -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 88E183A22D0; Fri, 21 May 2021 03:25:10 -0700 (PDT)
Received: from fraeml706-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Fmj9N5Crkz6Wxqk; Fri, 21 May 2021 18:13:12 +0800 (CST)
Received: from dggeml707-chm.china.huawei.com (10.3.17.137) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 21 May 2021 12:24:58 +0200
Received: from dggeml757-chm.china.huawei.com (10.1.199.137) by dggeml707-chm.china.huawei.com (10.3.17.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 21 May 2021 18:24:57 +0800
Received: from dggeml757-chm.china.huawei.com ([10.1.199.137]) by dggeml757-chm.china.huawei.com ([10.1.199.137]) with mapi id 15.01.2176.012; Fri, 21 May 2021 18:24:57 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "apn@ietf.org" <apn@ietf.org>
CC: 'Routing Area Working Group' <rtgwg-chairs@ietf.org>
Thread-Topic: [Apn] Application-Aware Networking (APN) focused interim
Thread-Index: AQHXQsiOTU5+/jETLkqlXYNY/6nV0arXMsUQgAmfglCACvrqgIABvdrw
Date: Fri, 21 May 2021 10:24:57 +0000
Message-ID: <3549bf4eb9af429a84d445b84ae7e6a8@huawei.com>
References: <1093984095.2655431620340260682.JavaMail.nobody@rva2rmd102.webex.com> <30d1f800-d292-4176-aab7-cf097df6d620@Spark> <ba91a4c7291a493b98a657422f8dda80@huawei.com> <0bc7b79e2c554038b05316d14750983f@huawei.com> <05a501d74d6c$7020e650$5062b2f0$@olddog.co.uk>
In-Reply-To: <05a501d74d6c$7020e650$5062b2f0$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.114]
Content-Type: multipart/alternative; boundary="_000_3549bf4eb9af429a84d445b84ae7e6a8huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/tTHfPToyQHo0EITKj1X21dYW6mc>
Subject: Re: [Apn] Application-Aware Networking (APN) focused interim
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: Fri, 21 May 2021 10:25:17 -0000

Hi Adrian,

Thank you for your comments. Please find in line below.

From: Apn [mailto:apn-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Thursday, May 20, 2021 7:37 PM
To: Pengshuping (Peng Shuping) <pengshuping@huawei.com>om>; apn@ietf.org
Cc: 'Routing Area Working Group' <rtgwg-chairs@ietf.org>
Subject: Re: [Apn] Application-Aware Networking (APN) focused interim

Hi Shuping,

This seems like a good set of topics (and thanks to the RTGWG chairs for giving us some time to discuss).

For your item 1, I presume this includes “What information do we need to include in the attribute?” and that compares with items 3 and 4 where we are looking at “What information and actions do we need to instruct the network devices to perform when they match on an attribute?”

Shuping> Yes, you are right. Just for the item 1, we may also need to consider the length of the attribute.

For item 2 I think there are two important questions:

  1.  Will different data planes need different information carried in the attribute? My feeling is, “No”, but it is possible that the control plane and management plane instructions and actions will be different in different data planes.

Shuping> I tend to agree with you that the same information is encapsulated on different data planes, and accordingly the control plane and management plane instructions are different. Just different data planes have different encapsulation formats, and each format has its own limitation in the available fields to carry this APN attribute, so we may need to consider this limitation and select the location for this attribute, and also whether this limitation will impact the design of the carried attribute. Just in this way, it would become a bit complex. It would be good to hear more opinions from the community to find reasonable solutions. This actually relates with item 1 and your following question.


  1.  Do we want to have identical encoding of the attribute in every data plane? I think the answer is, “Yes, if we can manage it.” I give you, as an example… Suppose we decide that an attribute should be 32 bits, but in MPLS we *could* use a label value (only 20 bits), would we do that or would we say, “No, we must always have 32 bits”?

Shuping> Yes, that relates with the design of the APN attribute and its length, whether it should be a fixed one or a flexible one, since it needs to better fit in the data plane limitation.

Looking forward to this discussion.

Shuping> Yes, it would be good to have more feedback from the community in the solution discussions.

Thank you!

Adrian


Best regards,
Shuping


From: Apn <apn-bounces@ietf.org<mailto:apn-bounces@ietf.org>> On Behalf Of Pengshuping (Peng Shuping)
Sent: 13 May 2021 05:02
To: Pengshuping (Peng Shuping) <pengshuping@huawei.com<mailto:pengshuping@huawei.com>>; apn@ietf.org<mailto:apn@ietf.org>
Cc: Routing Area Working Group <rtgwg-chairs@ietf.org<mailto:rtgwg-chairs@ietf.org>>
Subject: Re: [Apn] Application-Aware Networking (APN) focused interim


Hi all,



After some discussions, it seems that the use cases of APN have been clear, so people would like to directly focus on discussing the solutions of APN in the interim meeting.



I list a few relevant aspects of the solutions which we could discuss during the interim meeting, including

1.       the design of the APN attribute itself

2.       the encapsulation of the APN attribute on the various data planes

3.       the control plane protocols extensions for exchanging the APN attribute

4.       NETCONF/YANG models for the NBI and SBI

Your comments and suggestions are very welcomed.

Thank you!

Best regards,
Shuping



From: Apn [mailto:apn-bounces@ietf.org] On Behalf Of Pengshuping (Peng Shuping)
Sent: Friday, May 7, 2021 9:12 AM
To: apn@ietf.org<mailto:apn@ietf.org>
Cc: Routing Area Working Group <rtgwg-chairs@ietf.org<mailto:rtgwg-chairs@ietf.org>>
Subject: [Apn] FW: Application-Aware Networking (APN) focused interim

Dear all,

Thanks to the Chairs of RTGWG, the APN focused interim meeting has been scheduled. You are very welcomed to join the discussions.

We are preparing the agenda and will share with you soon.

If you have any suggestions, please let us know in the meanwhile.

Thank you!

Best regards,
Shuping


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
Sent: Friday, May 7, 2021 6:38 AM
To: Routing WG <rtgwg-chairs@ietf.org<mailto:rtgwg-chairs@ietf.org>>; RTGWG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Application-Aware Networking (APN) focused interim

Dear RTGWG,

We have scheduled Application-Aware Networking (APN) focused interim (agenda to be published), June 3rd, 2021, 7:00AM PST

Looking forward to seeing you,

Cheers,
Jeff and Chris




When it's time, start your Webex meeting here.






Thursday, June 3, 2021

7:00 AM  |  (UTC-07:00) Pacific Time (US & Canada)  |  2 hrs





Start meeting<https://ietf.webex.com/ietf/j.php?MTID=mc8ee2b80cb0fdd92745199a121f452db>





More ways to join:




Join from the meeting link

https://ietf.webex.com/ietf/j.php?MTID=mc8ee2b80cb0fdd92745199a121f452db





Join by meeting number


Meeting number (access code): 161 149 3477


Meeting password: gpN26drAet4





Tap to join from a mobile device (attendees only)

+1-650-479-3208,,1611493477##<tel:%2B1-650-479-3208,,*01*1611493477%23%23*01*> Call-in toll number (US/Canada)




Join by phone

1-650-479-3208 Call-in toll number (US/Canada)

Global call-in numbers<https://ietf.webex.com/ietf/globalcallin.php?MTID=m8fc024386f16ac264aaa306eeb5dff0c>





Join from a video system or application

Dial 1611493477@ietf.webex.com<sip:1611493477@ietf.webex.com>

You can also dial 173.243.2.68 and enter your meeting number.





Join using Microsoft Lync or Microsoft Skype for Business

Dial 1611493477.ietf@lync.webex.com<sip:1611493477.ietf@lync.webex.com>





If you are a host, click here<https://ietf.webex.com/ietf/j.php?MTID=m6b0d9545f1c064a6aa8f7739e2d4c763> to view host information.



Need help? Go to https://help.webex.com