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

[Feng Yang <[e-mail]>]

Hi Shuping,

 

SD-WAN is expected to carry quite some applications over hybrid links, such as internet, mpls, etc. Only with the application information, , it is possible for SD-WAN CPE to direct the traffic over different paths according to the application requirement.

For the application information, quite some ways work properly if the traffic is not encrypted. So the problem here is how to get the application information from the encrypted packets.  

 

Application information is the base that we can provide a lot of services. We expect to combine this with SRv6  in order to provide a new competitive SD-WAN service which can put SLA service、cloud based VAS(Value Added Service) together in a flexible way.

 

BR，

 

杨锋

Feng Yang

 

发件人: Apn [mailto:[e-mail]] 代表 Pengshuping (Peng Shuping)
发送时间: 2021年1月20日 14:18
收件人: [e-mail]; [e-mail]
主题: Re: [Apn] A new draft on APN for your review, thank you!

 

Dear all, 

 

In the MEF 70 “SD-WAN Service Attribute and Services”, Table 4 on Page 36 has defined the fields (from layer 2 through layer 4) which are expected to be able to match against ingress IP Packets. APPID is explicitly listed as a criterion.

 

“The APPID Policy Criterion provides the ability for the Service Provider to define and name both simple and complex matches. These can include standard matches available to all of the Service Provider’s Subscribers from a catalog and/or custom matches developed by the Service Provider by agreement with a particular Subscriber.”

 

https://www.mef.net/wp-content/uploads/2019/07/MEF-70.pdf

 

Is there anybody who knows more about the details about this criterion and its implementations of the catalog and the interactions? How does the standard match and the custom match work in the real system? What are the key elements in the system? How do they interact? 

 

Many thanks!

 

Best regards, 

Shuping 

 

 

From: Pengshuping (Peng Shuping) 
Sent: Tuesday, December 15, 2020 11:12 AM
To: [e-mail]; [e-mail]
Subject: 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.