[Apn] 回复:Re:回复:GoalsofneartermAPNwork
yangfeng <yangfeng@chinamobile.com> Sat, 21 January 2023 17:18 UTC
Return-Path: <yangfeng@chinamobile.com>
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 513F1C14CE24 for <apn@ietfa.amsl.com>; Sat, 21 Jan 2023 09:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 G2eh4SSZlBeZ for <apn@ietfa.amsl.com>; Sat, 21 Jan 2023 09:18:46 -0800 (PST)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0A4A6C151709 for <apn@ietf.org>; Sat, 21 Jan 2023 09:18:41 -0800 (PST)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.99]) by rmmx-syy-dmz-app09-12009 (RichMail) with SMTP id 2ee963cc1e6a266-e2d50; Sun, 22 Jan 2023 01:18:40 +0800 (CST)
X-RM-TRANSID: 2ee963cc1e6a266-e2d50
X-RM-SPAM-FLAG: 00000000
Received: from yangfeng@chinamobile.com ( [172.16.114.21] ) by ajax-webmail-syy-appsvrnew10-11020 (Richmail) with HTTP; Sun, 22 Jan 2023 01:18:39 +0800 (CST)
Date: Sun, 22 Jan 2023 01:18:39 +0800
From: yangfeng <yangfeng@chinamobile.com>
To: apn <apn@ietf.org>
Message-ID: <2b0c63cc177be4f-0001c.Richmail.00004020385373484359@chinamobile.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_65883_420911497.1674321519755"
X-Priority: 3
X-RM-TRANSID: 2b0c63cc177be4f-0001c
X-RM-OA-ENC-TYPE: 0
X-CLIENT-INFO: X-TIMING=0&X-MASSSENT=0&X-SENSITIVE=0
X-Mailer: Richmail_Webapp(V2.4.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/W5xBJMuxwr2HVBXoZFHeeOPx7vQ>
Subject: [Apn] 回复:Re:回复:GoalsofneartermAPNwork
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: Sat, 21 Jan 2023 17:18:49 -0000
Hi Andrew, Normally, DSCP can prioritize some traffic. But in case of congestion(maybe caused by degradation of transportation or some public event like black Friday) , prioritization is unfair for those with lower priority. Traffic needs to be rebalanced across the network by moving some traffic from the congested paths to somewhere else. This depends on where the traffic comes from and goes to, and the SLA contact. Thus linear space is necessary to make this work get much easier. Br, Feng -------原始邮件------- 发件人:Andrew Alston - IETF <andrew-ietf=40liquid.tech@dmarc.ietf.org> 发送时间:2023-01-21 18:48:06 收件人:yangfeng <yangfeng@chinamobile.com>,jmh <jmh@joelhalpern.com>,apn <apn@ietf.org> 主题:Re: [Apn]回复:GoalsofneartermAPNwork Feng, again – asking with no hats on, How exactly does this differ from DSCP – (or extended dscp with more bits.) When I read what you wrote below – to me – this reads exactly like more in depth dscp, and maybe I’m reading this wrong so I’m open to hearing otherwise. But (putting hat back on) – I see this as much of the problem with getting broad based support and adequately defining a charter. There seems to be a lot of confusion about what exactly is being attempted here. A simplistic reading of what is below, points to something like more dscp bits, yet, at the same time, we here talk of the need for something else for reasons that don’t seem to be clearly defined. To built a broad based community support for this work, I think there needs to be more clarity around what is actually being attempted – because that forms the basis of creating a framework, which in turn leads to solutions. There were very large fears raised about the privacy and security aspects at the original BOF, and assurances were given at RTGWG that things like the ability to identify an application direct etc wouldn’t be there. That got us some movement, but its lead to another question, if you remove that, is what you are left with nothing more than more DSCP bits (or something along those lines), and its lead to a question of, remove the application identification parts (which create significant security and privacy issues which the last BOF and what I believe was indicated in RTGWG clearly show are not tenable) – what’s left? If indeed we are saying – this is purely an expanded form of DSCP or something similar – then – that needs to be crystal clear and spelled out as such, but there seems to be different messages about this. Andrew From: Apn <apn-bounces@ietf.org> On Behalf Of yangfeng Sent: Saturday, January 21, 2023 5:36 AM To: jmh <jmh@joelhalpern.com> apn <apn@ietf.org> Subject: [Apn] 回复:GoalsofneartermAPNwork Hi Joel, Chasing good QoE is quite nature. As described in my previous email, we are currently distinguishing services by source IP address at our network edge devices. However, the source addresses are discrete, we hope there is a way to transform the address from discrete space into a linear space , which will make it be easier for classification, so that the services and policies along the tunnel can be combined in a simple way. Eventually that can improve our efficiency and reduce costs. The tagged information is not associated with any user or application. It is a group of users that have the same requirements on the network, and they will have the matched treatments on the various nodes along the tunnel. Br Feng -------原始邮件------- 发件人:Joel Halpern <jmh@joelhalpern.com> 发送时间:2023-01-21 03:25:56 收件人:apn <apn@ietf.org> 主题:[Apn] Goals of near term APN work I have re-read the email discussions and the most recent draft of the charter. I am quite confused by the charter. Aw far as I can tell, it assumes that we need a new IP header field, that the field will carry a range of information that will help a range of network behaviors, and that we do not have the ability to address these needs currently. It then says that the WG will develop a framework for such a field. Is developing and defining a new (variable length?) header field to address some ill-defined broad range of needs really the goal? Yours, Joel -- Apn mailing list Apn@ietf.org https://www.ietf.org/mailman/listinfo/apn Internal All Employees