Re: [Pce] WG Adoption of draft-tokar-pce-sid-algo-05

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 18 February 2022 09:08 UTC

Return-Path: <jie.dong@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 195AB3A0C0B; Fri, 18 Feb 2022 01:08:59 -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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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 FPFnV8KCbtPP; Fri, 18 Feb 2022 01:08:53 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A02A3A0C10; Fri, 18 Feb 2022 01:08:53 -0800 (PST)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4K0Qp14kRPz685XB; Fri, 18 Feb 2022 17:07:53 +0800 (CST)
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by fraeml705-chm.china.huawei.com (10.206.15.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.21; Fri, 18 Feb 2022 10:08:47 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme754-chm.china.huawei.com (10.3.19.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.21; Fri, 18 Feb 2022 17:08:46 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2308.021; Fri, 18 Feb 2022 17:08:45 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Dhruv Dhody <dd@dhruvdhody.com>, "pce@ietf.org" <pce@ietf.org>
CC: "draft-tokar-pce-sid-algo@ietf.org" <draft-tokar-pce-sid-algo@ietf.org>, Mahendra Negi <mahendra@rtbrick.com>
Thread-Topic: [Pce] WG Adoption of draft-tokar-pce-sid-algo-05
Thread-Index: AQHYGerW/Xiyc/bGPE+YRTdXuqD42qyYQD4AgAC0eOA=
Date: Fri, 18 Feb 2022 09:08:45 +0000
Message-ID: <578c74c4444e4de490cd5a8c69d01ca3@huawei.com>
References: <CAP7zK5Z4-B9j+cbcu_hvbNSzpQCWUKdAFLR=09bMLBROsARgVQ@mail.gmail.com> <CAP7zK5a0Az+beMPxKwqgct3TJ15wQgA52jXt-D4h1d6b4D_eQQ@mail.gmail.com>
In-Reply-To: <CAP7zK5a0Az+beMPxKwqgct3TJ15wQgA52jXt-D4h1d6b4D_eQQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: multipart/alternative; boundary="_000_578c74c4444e4de490cd5a8c69d01ca3huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/rxOBxEbXd9InL06IVm-FK4WY-eM>
Subject: Re: [Pce] WG Adoption of draft-tokar-pce-sid-algo-05
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: Fri, 18 Feb 2022 09:08:59 -0000

Hi WG, chairs,

I just read the latest version of this document. In general incorporating Algorithm into PCEP could be useful. While I have the below questions on this version and it would be helpful if they can be resolved before adoption.


1.       This document introduces the algorithm constraint in the LSPA object, which means the algorithm needs to be considered in the computation of the path. IMO this is important for computing a loop-free path. While the draft also says that the “the PCE MAY insert prefix SIDs with a different Algorithm in order to successfully compute a path.” Mixing SIDs with different algorithms in a path has the risk of loops. It is suggested that the document provides some analysis about such risk, and the example of scenarios where mixing SIDs with different algorithms is safe and desired.


2.       This is related to the first question. If the analysis shows that using SIDs with different algorithms in a path is not a good idea, then it would be unnecessary to carry the algorithm ID in SERO subobjects, instead carrying it as a path attribute would be enough.



3.       Assuming the answer to question 2 is YES, the SR-ERO and SRv6-ERO subobjects were defined with a fixed format (do not support sub-TLVs), this document introduces an additional optional field to those sub-objects, and use a new flag to indicate the existence of the new optional field. To my understanding this is not a usual approach for protocol extension. Usually a new Type needs to be defined for a new format. It would be necessary to understand the implication of using flags to indicate the modification to the format of an existing object.



4.       The term “SID Algorithm” in this document is different from that is used in the RFCs of SR/SRv6 IGP/BGP extensions, where it is called “SR-Algorithm”. Suggest to make them consistent.

Best regards,
Jie

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Dhruv Dhody
Sent: Friday, February 18, 2022 12:08 PM
To: pce@ietf.org
Cc: draft-tokar-pce-sid-algo@ietf.org; Mahendra Negi <mahendra@rtbrick.com>
Subject: Re: [Pce] WG Adoption of draft-tokar-pce-sid-algo-05

Hi WG,

A reminder to please respond to the WG adoption poll by Monday!

Please be more vocal. The silence makes it difficult to judge consensus.

Also, the IPR responses from Alex, Shuping, and Mahendra are missing still.

Thanks!
Dhruv & Julien

On Fri, Feb 4, 2022 at 10:44 PM Dhruv Dhody <dd@dhruvdhody.com<mailto:dd@dhruvdhody.com>> wrote:
Hi WG,

This email begins the WG adoption poll for draft-tokar-pce-sid-algo-05.

https://datatracker.ietf.org/doc/draft-tokar-pce-sid-algo/

Should this draft be adopted by the PCE WG? Please state your reasons - Why / Why not? What needs to be fixed before or after adoption? Are you willing to work on this draft? Review comments should be posted to the list.

Please respond by Monday 21st Feb 2022.

Have a great weekend.

Thanks!
Dhruv & Julien