[RTG-DIR] Rtgdir last call review of draft-ietf-teas-pce-native-ip

"Yemin (Amy)" <amy.yemin@huawei.com> Fri, 07 August 2020 08:12 UTC

Return-Path: <amy.yemin@huawei.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839983A0D2F for <rtg-dir@ietfa.amsl.com>; Fri, 7 Aug 2020 01:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 5TSWiCN0D9Sa for <rtg-dir@ietfa.amsl.com>; Fri, 7 Aug 2020 01:12:01 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C1543A0D2D for <rtg-dir@ietf.org>; Fri, 7 Aug 2020 01:12:01 -0700 (PDT)
Received: from lhreml735-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 6C915181ADA3998A6363 for <rtg-dir@ietf.org>; Fri, 7 Aug 2020 09:11:58 +0100 (IST)
Received: from dggema768-chm.china.huawei.com (10.1.198.210) by lhreml735-chm.china.huawei.com (10.201.108.86) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Fri, 7 Aug 2020 09:11:57 +0100
Received: from dggema769-chm.china.huawei.com (10.1.198.211) by dggema768-chm.china.huawei.com (10.1.198.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 7 Aug 2020 16:11:55 +0800
Received: from dggema769-chm.china.huawei.com ([10.9.128.71]) by dggema769-chm.china.huawei.com ([10.9.128.71]) with mapi id 15.01.1913.007; Fri, 7 Aug 2020 16:11:54 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: "rtg-dir@ietf.org" <rtg-dir@ietf.org>
Thread-Topic: Rtgdir last call review of draft-ietf-teas-pce-native-ip
Thread-Index: AdZsklOA/q5V47YbQumFIPm8Bm515w==
Date: Fri, 07 Aug 2020 08:11:54 +0000
Message-ID: <18b8887085ac4372aedf721ff16133f7@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.169.28.202]
Content-Type: multipart/mixed; boundary="_002_18b8887085ac4372aedf721ff16133f7huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/GIumiTEvsnF-DsKdndzzXJsQxk4>
Subject: [RTG-DIR] Rtgdir last call review of draft-ietf-teas-pce-native-ip
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Aug 2020 08:12:04 -0000

Forward Loa's mail to RTG-DIR list. 


-----邮件原件-----
发件人: Loa Andersson [mailto:loa@pi.nu] 
发送时间: 2020年8月7日 14:28
收件人: rtg-ads@ietf.org; "review: ddraft-ietf-teas-pce-native-.all"@ietf.org; TEAS WG Chairs <teas-chairs@ietf.org>; TEAS WG <teas@ietf.org>; pce@ietf.org; Yemin (Amy) <amy.yemin@huawei.com>; LucAndré Burdet <laburdet.ietf@gmail.com>
主题: teas


RtgDir review: ddraft-ietf-teas-pce-native-ip-09

Hello,

I have been selected as the Routing Directorate reviewer for this draft. 
The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see ​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-teas-pce-native-ip-09
Reviewer: Loa Andersson
Review Date: 2020-07-08
IETF LC End Date: date-if-known
Intended Status: copy-from-I-D - Experimental (see issues list).

Summary:


I'm departing from the normal list, since if this would have been a standard tracks document there would have been serious issues.

However, the document describes a TE experiment in a native IP network.
I think is so interesting that I wouldn't object if the issues I point are not (fully) resolved. Actually I would very much like to see published and followed up by a document that reports the results from the experiment.

I have the following issues with the document.

It is a framework that gives the framework for an experiment. Its intended status is Experimental. While agree that the accompanying specification should be Experimental I think that in accordance with earlier document a framework should be Informational.

The document describes the experiment in some detail, I would like to see more, especially evaluation criteria and bench marking. To have an overview of the test bed would be interesting.

I would recommend that someone take a look at the document from a language point of view. When I read I find myself correcting and clarifying the English (this is probably not a good idea, since my English is probably worse than the current authors).

There are loads of not expanded abbreviations, authors should go through the document and compare to:
https://www.rfc-editor.org/materials/abbrev.expansion.txt
to decide what needs to be expanded or not.

I would also want to suggest that someone with experience of "Native IP networks". both specification and operation should look at the document. From the early days of MPLS I remember that one motivation to create a strong tunnel technology was that the Route Reflectors no longer scaled.

I normally review document based on a word document, I have included the word-file, and it contains about everything form major issues to nits.


/Loa


-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64