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

Peter Psenak <> Thu, 27 May 2021 13:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5FE563A0CD8; Thu, 27 May 2021 06:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id h4bp7CS3Fua3; Thu, 27 May 2021 06:50:40 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9B0913A0CCC; Thu, 27 May 2021 06:50:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1195; q=dns/txt; s=iport; t=1622123439; x=1623333039; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=3fwS+6LVLCBFnpt5jsJNm8L0PY36J4pDFIFhyBP5na4=; b=kprkqAWI3ffG+u/SA5eWfMy5QRWvMRNRga9NSqlCA4JKX//jgYMnAqN4 7KVEgC5IT2YGBztQMtTLoBh0B1yG9l6SMKKhtmxFhD0jDtNmlDDB0VFba sr7jKwLFufQGdSw54LWrziuc+YO6sNJCY0A/TQCYxR7VXMuZE35QPDuFt k=;
X-IronPort-AV: E=Sophos;i="5.82,334,1613433600"; d="scan'208";a="33977690"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 May 2021 13:50:38 +0000
Received: from [] ( []) by (8.15.2/8.15.2) with ESMTP id 14RDoasg009731; Thu, 27 May 2021 13:50:37 GMT
To: "Ketan Talaulikar (ketant)" <>, Shraddha Hegde <>, Tony Li <>
Cc: "" <>, "" <>, "Acee Lindem (acee)" <>
References: <> <> <> <> <> <> <>
From: Peter Psenak <>
Message-ID: <>
Date: Thu, 27 May 2021 15:50:36 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
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, 27 May 2021 13:50:46 -0000

Hi Ketan,

On 27/05/2021 15:37, Ketan Talaulikar (ketant) wrote:

> For ISIS, Maximum Link Bandwidth sub-TLV is allowed in ASLA just that 
> different values for different applications is not allowed. Maximum Link 
> bandwidth is also allowed with all bits set to zero in SABM/UDABM  or 
> each individual application bit set for all applications making use of ASLA.
> */[KT2] Yes, you are correct. The RFC8919 does not mandate or require 
> Max Link Bandwidth to be signaled within ASLA (at least that was my 
> reading). If so, perhaps it is better to not require that in this 
> document – just keep in the base. Would that not work? And if it were 
> advertised in the ASLA (as RFC8919 allows it), then perhaps a reference 
> to the RFC8919 will be important on how it is to be done – basically 
> exactly what you described above./*

given that RFC8919 allows the Max Link Bandwidth to be signaled within 
ASLA, we need to be able to support it, in case someone uses that. What 
we would probably need to do is to look at the ASLA advertisement of Max 
Link Bandwidth first and if none is available fallback to legacy