Re: [Lsr] LSR WG Adoption Poll for "Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints" - draft-hegde-lsr-flex-algo-bw-con-02

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 14 May 2021 07:52 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4060B3A27DB; Fri, 14 May 2021 00:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ST1erpdkFeOF; Fri, 14 May 2021 00:52:25 -0700 (PDT)
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 C33D03A27E0; Fri, 14 May 2021 00:52:24 -0700 (PDT)
Received: from fraeml739-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FhL6r0xm2z6qnR3; Fri, 14 May 2021 15:40:52 +0800 (CST)
Received: from dggeme703-chm.china.huawei.com (10.1.199.99) by fraeml739-chm.china.huawei.com (10.206.15.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Fri, 14 May 2021 09:52:16 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme703-chm.china.huawei.com (10.1.199.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 14 May 2021 15:52:14 +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.2176.012; Fri, 14 May 2021 15:52:14 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
CC: "draft-hegde-lsr-flex-algo-bw-con@ietf.org" <draft-hegde-lsr-flex-algo-bw-con@ietf.org>
Thread-Topic: [Lsr] LSR WG Adoption Poll for "Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints" - draft-hegde-lsr-flex-algo-bw-con-02
Thread-Index: AQHXR3MLVak8G/B87Uy6Hz9GuLxph6riWwyQ
Date: Fri, 14 May 2021 07:52:14 +0000
Message-ID: <6ba087997bc1433babc8f3c00b7998ee@huawei.com>
References: <0BAE6DBA-04A3-4A3A-A1E3-14EFAA0FBE68@cisco.com>
In-Reply-To: <0BAE6DBA-04A3-4A3A-A1E3-14EFAA0FBE68@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.143]
Content-Type: multipart/alternative; boundary="_000_6ba087997bc1433babc8f3c00b7998eehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/nFg0vFQa5Bfkl2zLRaNAH_lvSwc>
Subject: Re: [Lsr] LSR WG Adoption Poll for "Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints" - draft-hegde-lsr-flex-algo-bw-con-02
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 07:52:30 -0000

Hi authors,

I’ve read the latest version of this document and have the following comments:


1.       Is the generic metric type applicable to applications other than Flex-Algo? If so, it is better to make this clear in the document, or perhaps it may be defined separately from the Flex-Algo specific extensions?


2.       The “Exclude Minimum Bandwidth” constraint is compared with the maximum link bandwidth to exclude the links from the computation, it would be helpful if there is some analysis about how much this can help in traffic engineering, such as to reduce the congestion or improve the link utilization. One simple example is, if multiple Flex-Algos use this constraint to exclude the same set of links, this may increase the possibility of congestion on the rest of the links?



Perhaps a more general question is, what would be the benefit of introducing bandwidth attribute into Flex-Algo based distributed path computation?  It is known that bandwidth can be used in centralized computation for efficient path placement and resource management, can distributed computation with bandwidth constraint achieve the same, or is there some advantages compared with centralized computation?



3.       With the automatic metric calculation, it could introduce per Flex-Algo link metric value, while the existing Flex-Algo only refers to the metric of the link via metric type. Is this the expected behavior? Will it be further extended to make other link attributes flex-algo specific?



4.       In the reference bandwidth method, the draft says it simplifies the management in case the reference bandwidth needs to be changed. Since the reference bandwidth applies to the metric calculation of all the links in the flex-algo with the same proportion, it seems the change of the reference bandwidth will not impact the result of the path computation in the flex-algo. In which case the reference bandwidth need to be changed?

Best regards,
Jie

From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Thursday, May 13, 2021 5:09 AM
To: lsr@ietf.org
Cc: draft-hegde-lsr-flex-algo-bw-con@ietf.org
Subject: [Lsr] LSR WG Adoption Poll for "Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints" - draft-hegde-lsr-flex-algo-bw-con-02

Esteemed Members of the LSR WG,

This begins a 2 week WG adoption call for the following draft:

     https://datatracker.ietf.org/doc/draft-hegde-lsr-flex-algo-bw-con/

Please indicate your support or objection by May 27th, 2021.

Authors, please respond to the list indicating whether you are aware of any IPR that applies to this draft.

Thanks,
Chris and Acee