IETF Logo Mail Archive

Re: [Apn] Further revised draft Charter

Li Cong <licong@chinatelecom.cn> Mon, 23 January 2023 08:02 UTC

Return-Path: <licong@chinatelecom.cn>
X-Original-To: apn@ietfa.amsl.com
Delivered-To: apn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C82AC14CF09 for <apn@ietfa.amsl.com>; Mon, 23 Jan 2023 00:02:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Q2broHfV1bR for <apn@ietfa.amsl.com>; Mon, 23 Jan 2023 00:02:39 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.220]) by ietfa.amsl.com (Postfix) with ESMTP id 2934EC14EB18 for <apn@ietf.org>; Mon, 23 Jan 2023 00:02:38 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.48:40196.1276032570
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-120.244.160.65 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 38F6B280090 for <apn@ietf.org>; Mon, 23 Jan 2023 16:02:36 +0800 (CST)
X-189-SAVE-TO-SEND: 71080549@chinatelecom.cn
Received: from ([120.244.160.65]) by app0024 with ESMTP id a796743d25274a44b00a29c3fe2f47c5 for apn@ietf.org; Mon, 23 Jan 2023 16:02:37 CST
X-Transaction-ID: a796743d25274a44b00a29c3fe2f47c5
X-Real-From: licong@chinatelecom.cn
X-Receive-IP: 120.244.160.65
X-MEDUSA-Status: 0
Sender: licong@chinatelecom.cn
User-Agent: Microsoft-MacOutlook/16.69.23010700
Date: Mon, 23 Jan 2023 16:02:34 +0800
From: Li Cong <licong@chinatelecom.cn>
To: apn@ietf.org
Message-ID: <8044D7CE-D41E-41F4-860A-C4E5D562ED71@chinatelecom.cn>
Thread-Topic: [Apn] Further revised draft Charter
References: <196346c8.32c.185dda49a0e.Coremail.licong_ct@163.com>
In-Reply-To: <196346c8.32c.185dda49a0e.Coremail.licong_ct@163.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3757334556_3117029016"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/Ztl3oEDV2Ua_cbsRQ0F-gnBfFaw>
Subject: Re: [Apn] Further revised draft Charter
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Application-aware Networking <apn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apn>, <mailto:apn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apn/>
List-Post: <mailto:apn@ietf.org>
List-Help: <mailto:apn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apn>, <mailto:apn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2023 08:02:40 -0000

Hi all,

 

>From some new use cases we found that to be able to provide some fine-granular services we would need some extra information. 

 

For example, different site groups of a VPN need different rules to interconnect, but in a hierarchical VPN scenario the aggregate node does not have enough information to separate the site groups because the site information is missing. In the case of SFC, multiple flows share the same SFC SID List and each group of flows actually desire to have a dedicated SF instance within a SF, but the SF does not enough information to separate flow groups because there is no such flow group information. 

 

In the network deployment, generally the two cases are used together, sometimes more for example traffic steering or performance measurement, that is once the sites have been separated and different sites will go through SFC. 

 

So we believe that there are real needs for such work to be investigated in IETF.

 

Best regards,

Cong Li

 

At 2023-01-18 10:04:28, "Donald Eastlake" <d3e3e3@gmail.com> wrote:

I've gotten some comments and I've re-read some of the AD DISCUSSES and comments. Based on that I've updated the draft Charter as attached.  Comments are welcome. 


Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

v2.23.0 | Report a Bug | By Email