Re: [Pce] Shepherd Review of draft-ietf-pce-association-group-06
Dhruv Dhody <dhruv.dhody@huawei.com> Thu, 07 March 2019 08:28 UTC
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0182130EBA; Thu, 7 Mar 2019 00:28:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 hkurMBO7xtsr; Thu, 7 Mar 2019 00:28:30 -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 6CB3D128AFB; Thu, 7 Mar 2019 00:28:30 -0800 (PST)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 14C07D75D76BBA87B674; Thu, 7 Mar 2019 08:28:28 +0000 (GMT)
Received: from BLREML405-HUB.china.huawei.com (10.20.4.41) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 7 Mar 2019 08:28:27 +0000
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.39]) by BLREML405-HUB.china.huawei.com ([10.20.4.41]) with mapi id 14.03.0415.000; Thu, 7 Mar 2019 13:58:16 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: "julien.meuric@orange.com" <julien.meuric@orange.com>, "'draft-ietf-pce-association-group@ietf.org'" <draft-ietf-pce-association-group@ietf.org>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] Shepherd Review of draft-ietf-pce-association-group-06
Thread-Index: AQHU1EPoXa8JbaLY6Emu21IrdEwnYaX/rqrA
Date: Thu, 07 Mar 2019 08:28:15 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8D98F3A8@BLREML503-MBX.china.huawei.com>
References: <24183_1551894081_5C800641_24183_488_1_e6b8f6b7-dab8-017b-23e1-9cfff46dae8b@orange.com>
In-Reply-To: <24183_1551894081_5C800641_24183_488_1_e6b8f6b7-dab8-017b-23e1-9cfff46dae8b@orange.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.149.39]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/JBVXq4qPmYTPfOLsY-5ohY-dhJs>
Subject: Re: [Pce] Shepherd Review of draft-ietf-pce-association-group-06
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 08:28:33 -0000
Hi Julien, Thanks for your detailed review and providing suggested text. Here is the working copy - https://raw.githubusercontent.com/dhruvdhody-huawei/ietf/master/draft-ietf-pce-association-group-08.txt Diff - https://tools.ietf.org/rfcdiff?url1=draft-ietf-pce-association-group-06&url2=https://raw.githubusercontent.com/dhruvdhody-huawei/ietf/master/draft-ietf-pce-association-group-08.txt > ------ > 4.1.1. Procedure > --- > - The last sentence of the paragraph puzzled me a bit. The current wording > may suggests that "it is RECOMMENDED to support the aforementioned > OPTIONAL TLV", which is inconsistent 2119 language. My guess is that it > should say: "In case the use of the ASSOC-Type-List TLV is triggered by a > mandatory association type, then it is RECOMMENDED that the PCEP > implementation include..." Is my understanding correct? [[Dhruv Dhody]] That is correct. Updated. > ------ > 5.1. Procedure > --- > - The current text only indirectly tackles the case where a given Assoc- > type is advertised multiple times, when forbidding overlapping ranges. A > complementary sentence explicitly mentioning non-overlapping ranges would > be welcome. [[Dhruv Dhody]] Added - An Assoc-Type MUST be present only once in the OP-CONF-ASSOC-RANGE TLV, if the same Assoc-Type is present more than once, the PCEP session MUST be rejected with error type 1 and error value 1 (PCEP session establishment failure / Reception of an invalid Open message). > ------ > Appendix A. > --- > - I am not comfortable with reading ranges in round brackets. Have square brackets been considered? > - I am not sure about the meaning of the sentence "not PCC or PCE as set > as NMS id", please rephrase. [[Dhruv Dhody]] In case the association source is not a PCEP peer (for example an NMS system), then the default range of <0x1000, 0xffff> is considered. Use of [] throws idnits, and thus I am using <>. Thanks again for your review. Regards, Dhruv
- [Pce] Shepherd Review of draft-ietf-pce-associati… julien.meuric
- Re: [Pce] Shepherd Review of draft-ietf-pce-assoc… Dhruv Dhody
- Re: [Pce] Shepherd Review of draft-ietf-pce-assoc… julien.meuric
- Re: [Pce] Shepherd Review of draft-ietf-pce-assoc… Dhruv Dhody
- Re: [Pce] Shepherd Review of draft-ietf-pce-assoc… julien.meuric