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

Tony Li <> Thu, 20 May 2021 04:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1DED43A2DDB; Wed, 19 May 2021 21:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id I0K9PPJS4_Kj; Wed, 19 May 2021 21:20:10 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AA77A3A2DDC; Wed, 19 May 2021 21:20:10 -0700 (PDT)
Received: by with SMTP id g24so8429422pji.4; Wed, 19 May 2021 21:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=M9TswfYH2JDijOErxUAvBRNkDRSc+1UR9niasjotnH4=; b=PEM6h0Rv2P+u8GdDKQdFPZxe9F7UzUspQkHmu/LoRe6JlYWU5HnodjJlBaJpLb1tuh 9/ADnU1EyDaEQUAjuKKjRyTr1ZhDJTpFr1i2KhB04xIVDNVE6b/Gz9zdFC2lXikOuoHt QnS/WIbocqYVOpHLwWFD5C+V2phrvJe5hcK5vV/h5Sjb38ITwBJLhTatpUuE6PvZ+oRM r/GE31cL1kexAInDv5mXUWmnL15kEO3qw/pSE/9dTBFhnSJFB1xQddg5KPOQHLMFljVf H36QoV7CirL56UgbRoPqp1QcNqfGfzIcLsdsCyVq8l89ewgBWuskxkJpk+hvROLO1qkD WK+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=M9TswfYH2JDijOErxUAvBRNkDRSc+1UR9niasjotnH4=; b=aGF2URwHvG06fm/nd/fMpn4u79k8dybaWim5VpVRGfqvYw8Mv8UH5hIDnc58ohk6sq jtpPmuQnosKrzOobNbo2d5GA929tNkPBz0nE6ID1V9SIYPhavylhwLbXJsT6qPYiCfoF OeEytGNJR86oiqtWMS6oeZ67J+nL2SyGP/N0ktgPW+fB8S9C7gvmHhgdd7K+ipsuv/B+ guhQ1xOp+dGqyPJh+mJq6GdE2jgpJP2ksITJ8JMuKKOfHJy6owC6duxGQND0y5yBzo/B BzjEUuwMwkVF2PFlmN608bAw1qVAE0QM/cn5JuxKFy0Y1+NbgqvLMe6IXPmW10sm6uIc GuIw==
X-Gm-Message-State: AOAM53192JQjXUlct9DW1xlxxiTaoCafvlSMAuTgKL7Rix1QE3lj9YOj pNScXgLZWfyv3xGTG3sakT4=
X-Google-Smtp-Source: ABdhPJydRT3tTANE8mjmzlIZEi6mfsj3wXRP4pgn6C+tHx0uH7Nxnc2YpdX6E3OvkxlQvALkOqXCpg==
X-Received: by 2002:a17:902:650f:b029:ef:905f:e82f with SMTP id b15-20020a170902650fb02900ef905fe82fmr3383175plk.78.1621484409206; Wed, 19 May 2021 21:20:09 -0700 (PDT)
Received: from ( []) by with ESMTPSA id 185sm730448pfb.184.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 May 2021 21:20:08 -0700 (PDT)
Sender: Tony Li <>
From: Tony Li <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1062FA28-12AB-4DC3-899E-65A63D7AE5BD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
Date: Wed, 19 May 2021 21:20:08 -0700
In-Reply-To: <>
References: <,> <,> <> <>
X-Mailer: Apple Mail (2.3654.
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: Thu, 20 May 2021 04:20:16 -0000

Hi Peng Shaofu,

> On May 19, 2021, at 6:55 PM, wrote:
> Let's go back to the bandwidth-metric related to bandwidth capability. My worry is that bandwidth-metric (whether it is automatically calculated or manually configured) is not cumulative in nature, which is different from IGP default metric/TE metric/delay metric, so that SPF based on bandwidth-metric may get an unexpected path (see the example of the original mail). Can more text be added in the draft to describe why this can work ?

The whole point of the bandwidth metric (and indeed, of all of FlexAlgo) is to get a different path computation result than what we might get with the standard IGP metric. What it will do in any given topology is highly dependent on the topology, as you’ve seen.  It may or may not ‘work’ by whatever definition you have in mind. However, what matters is what the network operator is trying to achieve. It doesn’t have to work for every topology or every purpose.