From nobody Thu Jan 21 23:53:51 2021 Return-Path: X-Original-To: rtgwg@ietfa.amsl.com Delivered-To: rtgwg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BCA3A11B5; Thu, 21 Jan 2021 23:53:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 yQhAD5n5Fw1a; Thu, 21 Jan 2021 23:53:47 -0800 (PST) Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 287283A11B4; Thu, 21 Jan 2021 23:53:43 -0800 (PST) Received: from spf.mail.chinamobile.com (unknown[172.16.121.9]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee1600a8476c9e-b413a; Fri, 22 Jan 2021 15:53:28 +0800 (CST) X-RM-TRANSID: 2ee1600a8476c9e-b413a X-RM-TagInfo: emlType=0 X-RM-SPAM-FLAG: 00000000 Received: from cmccPC (unknown[223.69.29.182]) by rmsmtp-syy-appsvr05-12005 (RichMail) with SMTP id 2ee5600a8476a5a-8fe2b; Fri, 22 Jan 2021 15:53:28 +0800 (CST) X-RM-TRANSID: 2ee5600a8476a5a-8fe2b From: "Feng Yang" To: "'Pengshuping \(Peng Shuping\)'" , , References: <4278D47A901B3041A737953BAA078ADE197FAE1A@DGGEML532-MBX.china.huawei.com> In-Reply-To: <4278D47A901B3041A737953BAA078ADE197FAE1A@DGGEML532-MBX.china.huawei.com> Subject: =?utf-8?Q?=E7=AD=94=E5=A4=8D:_=5BApn=5D_A_new_draft_on_APN_for?= =?utf-8?Q?_your_review=2C_thank_you!?= Date: Fri, 22 Jan 2021 15:53:30 +0800 Message-ID: <006f01d6f093$ad416090$07c421b0$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0070_01D6F0D6.BB64A090" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdbSj5OZJp0yHZz0SGiKnve9MVZvEAcTh4oQAGxAxeA= Content-Language: zh-cn Archived-At: X-BeenThere: rtgwg@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Routing Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2021 07:53:50 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0070_01D6F0D6.BB64A090 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Shuping, =20 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. =20 =20 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=E3=80=81cloud based = VAS(Value Added Service) together in a flexible way. =20 BR=EF=BC=8C =20 =E6=9D=A8=E9=94=8B Feng Yang =20 =E5=8F=91=E4=BB=B6=E4=BA=BA: Apn [mailto:apn-bounces@ietf.org] = =E4=BB=A3=E8=A1=A8 Pengshuping (Peng Shuping) =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2021=E5=B9=B41=E6=9C=8820=E6=97=A5 = 14:18 =E6=94=B6=E4=BB=B6=E4=BA=BA: apn@ietf.org; rtgwg@ietf.org =E4=B8=BB=E9=A2=98: Re: [Apn] A new draft on APN for your review, thank = you! =20 Dear all,=20 =20 In the MEF 70 =E2=80=9CSD-WAN Service Attribute and Services=E2=80=9D, = 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. =20 =E2=80=9CThe 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=E2=80=99s Subscribers from a catalog and/or custom matches = developed by the Service Provider by agreement with a particular = Subscriber.=E2=80=9D =20 https://www.mef.net/wp-content/uploads/2019/07/MEF-70.pdf =20 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?=20 =20 Many thanks! =20 Best regards,=20 Shuping=20 =20 =20 From: Pengshuping (Peng Shuping)=20 Sent: Tuesday, December 15, 2020 11:12 AM To: apn@ietf.org; rtgwg@ietf.org Subject: A new draft on APN for your review, thank you!=20 =20 Dear all,=20 =20 A new draft on APN has been posted, = https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis. =20 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 =E2=80=9Csimilar=E2=80=9D work/solutions and = did corresponding gap analysis.=20 =20 Your review and comments are very much appreciated. Thank you! =20 Best regards,=20 Shuping=20 =20 =20 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. =20 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 =20 =20 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. =20 =20 ------=_NextPart_000_0070_01D6F0D6.BB64A090 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

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. = =C2=A0

 

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

 

BR=EF=BC=8C

 

=E6=9D=A8=E9=94=8B

Feng Yang

 

=E5=8F=91=E4=BB= =B6=E4=BA=BA: Apn = [mailto:apn-bounces@ietf.org] =E4=BB=A3=E8=A1= =A8 Pengshuping = (Peng Shuping)
=E5=8F=91=E9=80= =81=E6=97=B6=E9=97=B4: = 2021=E5=B9=B41=E6=9C=8820=E6=97=A5 14:18
=E6=94=B6=E4=BB=B6=E4=BA=BA: apn@ietf.org; = rtgwg@ietf.org
=E4=B8=BB=E9=A2=98: Re: [Apn] A new draft on = APN for your review, thank = you!

 

Dear all,

 

In the MEF = 70 =E2=80=9CSD-WAN Service Attribute and Services=E2=80=9D, 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.

 

=E2=80=9CThe 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=E2=80=99s Subscribers from a catalog = and/or custom matches developed by the Service Provider by agreement = with a particular Subscriber.=E2=80=9D

 

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: apn@ietf.org; = rtgwg@ietf.org
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-an= alysis.

 

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 =E2=80=9Csimilar=E2=80=9D = 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:         &= nbsp;    = 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:         &n= bsp;  https://www.ietf.org/archive/id/draft-peng-apn-scope-gap-analysi= s-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-an= alysis

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.

 

 

------=_NextPart_000_0070_01D6F0D6.BB64A090--