[Int-area] The official instructions on the next step of APN

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Thu, 04 February 2021 01:40 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B6F53A1066; Wed, 3 Feb 2021 17:40:09 -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 fsr5JD_cbaoC; Wed, 3 Feb 2021 17:40:07 -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 5C63A3A0CDC; Wed, 3 Feb 2021 17:40:07 -0800 (PST)
Received: from fraeml701-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DWLk82n4nz67klw; Thu, 4 Feb 2021 09:36:32 +0800 (CST)
Received: from fraeml701-chm.china.huawei.com (10.206.15.50) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Thu, 4 Feb 2021 02:40:03 +0100
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.2106.2 via Frontend Transport; Thu, 4 Feb 2021 02:40:02 +0100
Received: from DGGEML512-MBS.china.huawei.com ([169.254.3.112]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0509.000; Thu, 4 Feb 2021 09:40:00 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "apn@ietf.org" <apn@ietf.org>
CC: "rtgwg@ietf.org" <rtgwg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: The official instructions on the next step of APN
Thread-Index: Adb6lleZeMHH2QFSSZ+cehjvmP7e9g==
Date: Thu, 04 Feb 2021 01:39:59 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE19883983@dggeml512-mbs.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.109.48.156]
Content-Type: multipart/alternative; boundary="_000_4278D47A901B3041A737953BAA078ADE19883983dggeml512mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/xQT_ciLX4ifeqaeieZHQHSDu_F0>
Subject: [Int-area] The official instructions on the next step of APN
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2021 01:40:10 -0000

Dear all,

You may have seen the BoF announcement https://www.ietf.org/blog/ietf110-bofs/.

The instructions on the next step of APN are officially confirmed,

1.      Presentations and discussions in the RTGWG and INTAREA meetings at IETF110.

2.      A virtual interim meeting of the RTGWG to be scheduled after IETF110 to go into more depth on this topic.

Any suggestions on how to have fruitful discussions and progress the work in IETF are very welcomed. Thank you!

"The Application-Aware Networking (APN) BOF proposal was focused on developing a framework and set of mechanisms to derive, convey, and use an identifier to allow for the signaling of fine-grained user-, application-, and service-level requirements at the network layer. This proposal was made for several previous IETF meetings and will benefit from further focused discussion at IETF 110 during the Routing Area Working Group (RTGWG<https://datatracker.ietf.org/wg/rtgwg/about/>) and Internet Area Working Group (INTAREA<https://datatracker.ietf.org/wg/intarea/about/>) meetings. A virtual interim meeting of the RTGWG to be scheduled after IETF 110 will go into more depth on this topic. Discussion continues on the Application-aware Networking<https://www.ietf.org/mailman/listinfo/apn> mailing list. "

Best regards,
Shuping