Re: [Teas] Magnus Westerlund's No Objection on draft-ietf-teas-pce-native-ip-15: (with COMMENT)

Aijun Wang <wangaj3@chinatelecom.cn> Fri, 22 January 2021 01:58 UTC

Return-Path: <wangaj3@chinatelecom.cn>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87E393A0F3A; Thu, 21 Jan 2021 17:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 PLFzwki6LUqi; Thu, 21 Jan 2021 17:58:47 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.219]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1F43A0F41; Thu, 21 Jan 2021 17:58:45 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.218:6214.703854341
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.75?logid-73255c52b35347ba9069753bbf853a43 (unknown [172.18.0.218]) by chinatelecom.cn (HERMES) with SMTP id 234FE280099; Fri, 22 Jan 2021 09:58:32 +0800 (CST)
X-189-SAVE-TO-SEND: 66040164@chinatelecom.cn
Received: from ([172.18.0.218]) by App0025 with ESMTP id 73255c52b35347ba9069753bbf853a43 for draft-ietf-teas-pce-native-ip@ietf.org; Fri Jan 22 09:58:43 2021
X-Transaction-ID: 73255c52b35347ba9069753bbf853a43
X-filter-score: filter<0>
X-Real-From: wangaj3@chinatelecom.cn
X-Receive-IP: 172.18.0.218
X-MEDUSA-Status: 0
Sender: wangaj3@chinatelecom.cn
From: "Aijun Wang" <wangaj3@chinatelecom.cn>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>, "'The IESG'" <iesg@ietf.org>
Cc: <draft-ietf-teas-pce-native-ip@ietf.org>, <teas-chairs@ietf.org>, <teas@ietf.org>, "'Lou Berger'" <lberger@labn.net>
References: <161123908659.32347.6359692293030979970@ietfa.amsl.com>
In-Reply-To: <161123908659.32347.6359692293030979970@ietfa.amsl.com>
Date: Fri, 22 Jan 2021 09:58:25 +0800
Message-ID: <006b01d6f062$1bdeb610$539c2230$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQK5sqYP2c3RpYpZuhYtKSlk5CClwahtVYfQ
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/RzXjNvTQ5Cp0lZaBxALTJBspiUM>
Subject: Re: [Teas] Magnus Westerlund's No Objection on draft-ietf-teas-pce-native-ip-15: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 01:58:50 -0000

Hi, Magnus:

Please see the detail response inline [WAJ].
Wish it can address your concern.


Best Regards

Aijun Wang
China Telecom

-----Original Message-----
From: noreply@ietf.org <noreply@ietf.org> 
Sent: Thursday, January 21, 2021 10:25 PM
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-teas-pce-native-ip@ietf.org; teas-chairs@ietf.org; teas@ietf.org; Lou Berger <lberger@labn.net>et>; lberger@labn.net
Subject: Magnus Westerlund's No Objection on draft-ietf-teas-pce-native-ip-15: (with COMMENT)

Magnus Westerlund has entered the following ballot position for
draft-ietf-teas-pce-native-ip-15: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-teas-pce-native-ip/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I think this whole idea is based on the fact that you can actually have multiple different prefix the traffic based on the network treatment it should have. I think that has very limited applicability unless we are talking a deployment where one target tunnels between in ingress and egress that does traffic classification based on other aspects. Can this assumption about that the IP traffic needs to use different IP addresses with different prefix to get any differential treatment be expanded in the discussion?
[WAJ] The logic of this document is the followings:
1. Different applications have different QoS requirement.
2. Different applications have different IP Prefix.
3. These different IP Prefix needs to find different path to pass within the network.
4. we use the different BGP sessions to advertise these different prefixes, manage the route the nexthop these BGP sessions, then influence the path of these application traffic.
5. Usage scenarios can be found in https://tools.ietf.org/html/rfc8735
6. Using tunnel between the ingress and egress are also possible accomplished under the procedures described in current documents.

Are the above short description address your concerns?