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

"Pengshuping (Peng Shuping)" <> Tue, 25 May 2021 03:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E0813A0FF0; Mon, 24 May 2021 20:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.595
X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HKEs4csuXIB5; Mon, 24 May 2021 20:56:49 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D207F3A10BC; Mon, 24 May 2021 20:56:48 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4Fq0R40l1kz6L5RM; Tue, 25 May 2021 11:48:00 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Tue, 25 May 2021 05:56:45 +0200
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Tue, 25 May 2021 11:56:43 +0800
Received: from ([]) by ([]) with mapi id 15.01.2176.012; Tue, 25 May 2021 11:56:43 +0800
From: "Pengshuping (Peng Shuping)" <>
To: Gyan Mishra <>
CC: "" <>, 6MAN <>, Routing Area Working Group <>, "" <>, RTGWG <>
Subject: RE: [Apn] FW: Application-Aware Networking (APN) focused interim
Thread-Topic: [Apn] FW: Application-Aware Networking (APN) focused interim
Thread-Index: AQHXQsiOTU5+/jETLkqlXYNY/6nV0ariLrWggAvpyACABYG6gA==
Date: Tue, 25 May 2021 03:56:42 +0000
Message-ID: <>
References: <> <30d1f800-d292-4176-aab7-cf097df6d620@Spark> <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_c7dcd415d3874047999736f3d71d7364huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 May 2021 03:56:55 -0000

Hi Gyan, folks,

Thank you for your suggestions! Besides the guiding slides for the solution discussions, we will also have a set of slides for the problem statement to clarify the WHY.

According to the feedback we have received so far, we have updated the main drafts to sync the information.

The main changes we have made to the drafts are as follows:

1. Removed the application-side solution, only keep the network-side solution

2. The APN attribute is acquired based on the existing information in the packet header such as 5-tuple and QinQ (S-VLAN and C-VLAN) at the edge devices of the APN domain, added to the data packets along with the tunnel encapsulation.

3. When the packets leave the APN domain, the attribute will be removed together with the tunnel encapsulation header.

4. APN aims to apply various policies in different nodes along a network path onto a traffic flow altogether, for example, at the headend to steer into corresponding path, at the midpoint to collect corresponding performance measurement data, and at the service function to execute particular policies.

Your reviews and comments are very welcomed. Thank you!

Best regards,

From: Apn [] On Behalf Of Gyan Mishra
Sent: Saturday, May 22, 2021 6:39 AM
To: Pengshuping (Peng Shuping) <>
Cc:; 6MAN <>; Routing Area Working Group <>;
Subject: Re: [Apn] FW: Application-Aware Networking (APN) focused interim

Hi Shuping & APN WG

I agree as well that the agenda looks good and many thanks to the RTGWG for providing a time slot to host the discussion.

I support the basic concept of the gap APN is trying to solve and provide fine grain SLA for primary use case of 5G network slicing.

Traditionally and historically customer SLA been provided using Diffserv QOS Marking and PHB scheduling as well as customer application layer SLA using RSVP TE class or path based tunnel selection DS TE RFC 4124 and RFC 3270 MPLS Diffserv uniform and pipe mode explicit null framework to meet customer SLA requirements.  Also ALTO / SDN PCE / PCE CC based network based application flow optimizations of flows as well as ACTN abstraction framework for underlay path resource provisioning.

As an agenda item I think it maybe a good idea to briefly touch on the problem statement and the gap that requires a solution based on  existing technologies and solutions that exist today.

Also applicability of the APN ID fine grain SLA for 5G network slicing, DETNET, SD WAN as well as any other use cases.

As we have discussed caveats and complexity related to host to network signaling that it makes sense to update the existing drafts to reflect application edge CE based network marking of the APN ID.   Also, as the APN ID marking as we have discussed will change  to network layer marking on the application edge CE, how does the marking closely or not resemble the VTN ID marking in the data packet for VPN+ E2E network slicing.

This will help facilitate the discussion so we don’t get stuck on the complexity of host to network signaling.

Kind Regards


On Thu, May 13, 2021 at 8:55 PM Pengshuping (Peng Shuping) <<>> wrote:
Dear all,

The APN Interim meeting has been scheduled on June 3rd. Please find the meeting information shared by the Chairs of the RTG WG below.

In this APN Interim meeting, we are going to focus more on the discussions of the solutions (more overview than details), including
1.       the design of the APN attribute itself
2.       the encapsulation of the APN attribute on the various data planes (the encapsulation on the IPv6 data plane is an example)
3.       the control plane protocols extensions for exchanging the APN attribute
4.       NETCONF/YANG models for the NBI and SBI

You are very welcomed to join the discussions, and your comments and suggestions are very much appreciated.

Thank you!

Best regards,

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


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

Looking forward to seeing you,

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<>

More ways to join:

Join from the meeting link

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<>

Join from a video system or application


You can also dial and enter your meeting number.

Join using Microsoft Lync or Microsoft Skype for Business


If you are a host, click here<> to view host information.

Need help? Go to

Apn mailing list<>


Gyan Mishra

Network Solutions Architect


M 301 502-1347