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

Adrian Farrel <> Thu, 20 May 2021 11:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D6DD23A11F4; Thu, 20 May 2021 04:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.049
X-Spam-Status: No, score=-1.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, MAY_BE_FORGED=0.846, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WKD3i20ktSBj; Thu, 20 May 2021 04:37:17 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 28FFD3A11F6; Thu, 20 May 2021 04:37:16 -0700 (PDT)
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id 14KBaw0P000421; Thu, 20 May 2021 12:36:58 +0100
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 378274604B; Thu, 20 May 2021 12:36:58 +0100 (BST)
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 20F954604A; Thu, 20 May 2021 12:36:58 +0100 (BST)
Received: from (unknown []) by (Postfix) with ESMTPS; Thu, 20 May 2021 12:36:58 +0100 (BST)
Received: from LAPTOPK7AS653V ( [] (may be forged)) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id 14KBaurU013624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 20 May 2021 12:36:57 +0100
Reply-To: <>
From: "Adrian Farrel" <>
To: "'Pengshuping \(Peng Shuping\)'" <>, <>
Cc: "'Routing Area Working Group'" <>
References: <> <30d1f800-d292-4176-aab7-cf097df6d620@Spark> <> <>
In-Reply-To: <>
Date: Thu, 20 May 2021 12:36:55 +0100
Organization: Old Dog Consulting
Message-ID: <05a501d74d6c$7020e650$5062b2f0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05A6_01D74D74.D1E74A20"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHGtSFrpvgQ0I0ieYU4QcuNQUJsGAHlxjd+AZwiMS8B3uGYXqriZmoQ
Content-Language: en-gb
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--20.335-10.0-31-10
X-imss-scan-details: No--20.335-10.0-31-10
X-TMASE-Result: 10--20.334700-10.000000
X-TMASE-MatchedRID: Z/tjqhsgM6c7iuZ/mdYYttd4GtnW8ArzpZkFxNdtI04VvqM4RwhxWgeH 2ilxpqDEl1wQgiBlkGj0VCHd+VQiHhwOcB9/9tcRwgNhKyNLcsBXvJGnRCiXvWCm8jfK1Jj+Qhc sJHLuy19852h6G8F8RcmR5yDJkPg4f/TIOqPsDItGQgIVrmBL5OOj4DfnnaWN+7QmOJudfuMtOt cED7Pu8a5Ey0+C1mtS9FHjNotpdxB841u5HtOu0Oglj6bzQJp3cRFtLs5mkQO1h3Ci3ttLrX4J7 5ElE1H50rQd7slfQfoM6z3iDvziBxmyTBaqiJvcNMxGS7Dxq6XSUjkG2xf5lHA6FdsV6qSVCmZV 5HSmSt1aFJUbnQZgDxJo06V2lHTe5RMDFPANjSglSdV/WXx413Y+oFbrqO/JHwUD6lwgYVnCjJI PZLJSDITFTWXyA+s5hUy0TABax1wC966cjk9M2I2cB1+t/hleQIr1zL2sUgbQ8/DsZs53feJbyK mua0b4csb/jPY11iO8coKUcaOOvQEoHzC4m9uQUZ/6GOLJpx9hejp7pwzKTM3UiHZ4HGnVwTzZE 6vGH1wNagYbADmq551U1lojafr/poRZlfJyQho8cwBuO6HB3+eu43vHPPZUraRk79v04mO73qCn vBDccM1HQN/TlJ3Z4v0ZcDzkTys2bU9AQ/mTR/kuQv9PIVnNCS73sssHlijxtERWzypyblAN+lM +1BnUzsxJFD0fGDrnh6rB4tZovm4X43BE7qO0dDwP5ItpCOzesTw6jtmPrkkk6yagWKEsr/EwLy a77le0CeKFBeer6FICmG2RRehog8A5lLJLbX2zY4DjK+V7zz166Jh7ejx4Yxeu+Iqmk8GCmVlPl EhC+LDszp3K5gqDhUfR2rvBju6nw52XVXCkJH9lerkAA9truJb9/hh11XdrHMOappFiVMcn986q 7RyFY3ru0gcQML8=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <>
Subject: Re: [Apn] Application-Aware Networking (APN) focused interim
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Application-aware Networking <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 May 2021 11:37:23 -0000

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


For item 2 I think there are two important questions:

a.	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.
b.	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”?


Looking forward to this discussion.




From: Apn <> On Behalf Of Pengshuping (Peng Shuping)
Sent: 13 May 2021 05:02
To: Pengshuping (Peng Shuping) <>om>;
Cc: Routing Area Working Group <>
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, 





From: Apn [] On Behalf Of Pengshuping (Peng Shuping)
Sent: Friday, May 7, 2021 9:12 AM
To: <> 
Cc: Routing Area Working Group < <> >
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, 




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)

 <tel:%2B1-650-479-3208,,*01*1611493477%23%23*01*> +1-650-479-3208,,1611493477## 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

Dial  <>

You can also dial and enter your meeting number.




Join using Microsoft Lync or Microsoft Skype for Business

Dial  <>




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


Need help? Go to  <>