Re: [RTG-DIR] [Pce] RtgDir review: draft-ietf-pce-stateful-pce-p2mp-10.txt

Dhruv Dhody <dhruv.dhody@huawei.com> Tue, 19 February 2019 05:15 UTC

Return-Path: <dhruv.dhody@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 2D218126C01; Mon, 18 Feb 2019 21:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 aX1wD3cAgO9J; Mon, 18 Feb 2019 21:15:37 -0800 (PST)
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 C3498124C04; Mon, 18 Feb 2019 21:15:36 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 504DBF60D66713F9D498; Tue, 19 Feb 2019 05:15:34 +0000 (GMT)
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 19 Feb 2019 05:15:33 +0000
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 19 Feb 2019 05:15:33 +0000
Received: from BLREML406-HUB.china.huawei.com (10.20.4.43) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 19 Feb 2019 05:15:33 +0000
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.112]) by BLREML406-HUB.china.huawei.com ([10.20.4.43]) with mapi id 14.03.0415.000; Tue, 19 Feb 2019 10:45:23 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "draft-ietf-pce-stateful-pce-p2mp.all@ietf.org" <draft-ietf-pce-stateful-pce-p2mp.all@ietf.org>
Thread-Topic: [Pce] RtgDir review: draft-ietf-pce-stateful-pce-p2mp-10.txt
Thread-Index: AQHUx82Kca7KjkuFrUuPSsNe9xSxP6XmlHFA
Date: Tue, 19 Feb 2019 05:15:23 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8D9532D7@BLREML503-MBX.china.huawei.com>
References: <CAA=duU0tv-q5BRg3nudfnao-DYwf2YVLcERGZBvjp+X2tBv38A@mail.gmail.com>
In-Reply-To: <CAA=duU0tv-q5BRg3nudfnao-DYwf2YVLcERGZBvjp+X2tBv38A@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.149.39]
Content-Type: multipart/related; boundary="_004_23CE718903A838468A8B325B80962F9B8D9532D7BLREML503MBXchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/o5AQPDB1A_IECcYMw-qZL8Hmi0M>
Subject: Re: [RTG-DIR] [Pce] RtgDir review: draft-ietf-pce-stateful-pce-p2mp-10.txt
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: Tue, 19 Feb 2019 05:15:39 -0000

Hi Andy,



Thanks for your review. Your comments are incorporated in the -11 version.



The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-p2mp/



A diff from the previous version is available at:

https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-stateful-pce-p2mp-11



Regards,

Dhruv



Dhruv Dhody
Lead Architect
Network Business Line
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru, Karnataka - 560066
Tel: + 91-80-49160700 Ext 71583 II Email: dhruv.dhody@huawei.com<mailto:dhruv.dhody@huawei.com>
[Huawei-small]
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: 19 February 2019 02:34
To: <rtg-ads@ietf.org> <rtg-ads@ietf.org>
Cc: rtg-dir@ietf.org; pce@ietf.org; draft-ietf-pce-stateful-pce-p2mp.all@ietf.org
Subject: [Pce] RtgDir review: draft-ietf-pce-stateful-pce-p2mp-10.txt

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-pce-stateful-pce-p2mp-10.txt
Reviewer: Andy Malis
Review Date: 18 February 2019
IETF LC End Date: N/A (in preparation for IETF LC)
Intended Status: Standards Track

Summary:

This document is basically ready for publication, but has nits that should be considered prior to publication.

Comments:

It was very easy to follow the draft. Excellent work by all involved.

Major issues:

No major issues found.

Minor Issues:

No minor issues found.

Nits:

1. Section 3..1, second paragraph:

Replace:
For P2MP this is an added advantage, where the size of message is much larger.

With:
For P2MP, where the size of message is much larger, this is an added advantage.

2. Section 5.1, fifth paragraph:

Replace:
Path Computation LSP Initiate Message (PCInitiate):  is a PCEP

With:
Path Computation LSP Initiate Message (PCInitiate): PCInitiate is a PCEP

3. Section 5.2, first paragraph:

Replace:
PCEP speakers advertise Stateful capability via STATEFUL-PCE-CAPABILITY TLV in open message.

With:
PCEP speakers advertise Stateful capability via the STATEFUL-PCE-CAPABILITY TLV in the OPEN object.

4. Section 5.2, third paragraph (N Flag): In two places, replace "changes" with "change".

5.. Section 5.3, first paragraph: Expand "LSR" (Label Switching Router) on first use. It's not on the RFC Editor's list of well-known acronyms.

6. Section 5.3, second paragraph: Expand "PCED" (PCE Discovery TLV) on first use.

7. Section 6.2, last paragraph: A right ")" is missing at the end of the paragraph.

8. Section 6.5, first paragraph: In the second line, replace the comma with a period and capitalize the following "this".

9. Section 6.5, last paragraph: A right ")" is missing at the end of the paragraph.

10. Section 8, second paragraph: Add the word "The" to the start of the paragraph.

11. Section 11.2, first paragraph. Change "and a registry was created" to "and the STATEFUL-PCE-CAPABILITY TLV Flag Field subregistry was created"

12. Section 11.3, first paragraph: Change "and a registry was created" to "and the LSP Object Flag Field subregistry was created"

Regards,
Andy