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

Aijun Wang <> Tue, 25 May 2021 02:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C9D083A09D7; Mon, 24 May 2021 19:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vgg_Vl6FgOuV; Mon, 24 May 2021 19:01:03 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7FC573A09C3; Mon, 24 May 2021 19:01:01 -0700 (PDT)
Received: from DESKTOP2IOH5QC (unknown []) by (Hmail) with ESMTPA id 7960F1C010D; Tue, 25 May 2021 10:00:53 +0800 (CST)
From: "Aijun Wang" <>
To: "'Tony Li'" <>, "'Ketan Jivan Talaulikar'" <>
Cc: <>, <>, "'Acee Lindem \(acee\)'" <>
References: <> <> <>
In-Reply-To: <>
Date: Tue, 25 May 2021 10:00:53 +0800
Message-ID: <007201d75109$cb3bac00$61b30400$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0073_01D7514C.D961D230"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGCHewxXNMdyq1O1SgwkvAA6Y4xTwI4yiRDAeQlYyirfOuXsA==
Content-Language: zh-cn
X-HM-Tid: 0a79a140deafd993kuws7960f1c010d
Archived-At: <>
Subject: Re: [Lsr] LSR WG Adoption Poll for "Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints" - draft-hegde-lsr-flex-algo-bw-con-02
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 May 2021 02:01:09 -0000

Hi, Tony:

7.      The document introduces a new Generic Metric type called Bandwidth metric. I’ve been trying to follow some of the discussion related to this on the mailing list – about it being cumulative or not. I am perhaps somewhat confused by those discussions. The OSPF/ISIS SPT computation has always worked with cumulative link (and prefix) metrics. If the computation for the Generic Metric of this new type b/w is not going to be cumulative (I thought it is – but not very clear anymore), then the document needs to describe the computation algorithm. Is it then hop count based? Perhaps I am missing something very basic here and if so, please point me to the text in the draft.



I’m sorry if this has been confusing. My understanding is that the metric is cumulative. Others had other expectations.


When there are multiple links with the same bandwidth, and thus the same metric, then the total path metric becomes (link metric) * (number of links).

[WAJ] Such cumulative may be problematic in some situations and would need the manual intervention to “override” the automatic calculation “total path metric” to achieve the desired results. (please refer to the example in

The difficulty is to how to find the unexpected paths in complex topology.


My suggestion is still not introduce such non-cumulative metric to cumulative based SPF calculation process.



Best Regards


Aijun Wang

China Telecom