Re: [Lsr] draft-peng-lsr-flex-algo-l2bundles

Peter Psenak <> Fri, 12 March 2021 12:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EA8E63A1983 for <>; Fri, 12 Mar 2021 04:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -11.902
X-Spam-Status: No, score=-11.902 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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PKCrZtVPjipG for <>; Fri, 12 Mar 2021 04:04:07 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D67123A1981 for <>; Fri, 12 Mar 2021 04:04:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=4780; q=dns/txt; s=iport; t=1615550647; x=1616760247; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=cBKtknmUPryYnYS7yVbYG40UZJqo47UbqPV8wk6J4Us=; b=g9n++QcxLSFaOifAvtN7WLPT7vW5V8SoeziXZEKgZ+Ea9NZRRbriItYt oIK3V+jjml8yeHIVtZ1MeQXwFbH/BILppN5u4VCSh1j57PgxK7at4WuUI kPNOhmwEBnwuZiJ6p8IspQ6HzfQa5pHh1pHf7Oh5rZj5YxaguoHnX/NrF Y=;
IronPort-HdrOrdr: A9a23:/PD/X69bEaBnnpqXlaZuk+GRdb1zdoIgy1knxilNYDZeG/b1q+ mFmvMH2RjozBMYX389kd6NUZPwJk/035hz/IUXIPOeRwHgomSlN8VP6oHlzj3mFUTFh4hg/I 1ndLVzD8C1MEhiga/BkW2FOvsp3dXvysCVrMjEyXMFd29XQoFmqzx0EwOKVnBxLTM2YKYRML q5yo55qyG7eXIRB/7LZEUte+TYvdXEmNbHTHc9ZiIP0wWFgTO25LOSKXHxtSs2aD9Bzawv9m LIiWXCiZmLie2xyRPXygbohah+pd2J8LZ+LfCXhtNQAjvhjRvAXvUDZ5Sy+BYoveqo9FEm1P 7LrhtIBbUK11rhOkeovBDqxw7slAwL1kan41qZjXz/yPaJPQ4HNw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,243,1610409600"; d="scan'208";a="34136930"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Mar 2021 12:04:02 +0000
Received: from [] ( []) by (8.15.2/8.15.2) with ESMTP id 12CC425B011874; Fri, 12 Mar 2021 12:04:02 GMT
References: <>
From: Peter Psenak <>
Message-ID: <>
Date: Fri, 12 Mar 2021 13:04:01 +0100
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] draft-peng-lsr-flex-algo-l2bundles
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: Fri, 12 Mar 2021 12:04:09 -0000

Hi Shaofu,

please see inline (##PP):

On 12/03/2021 04:26, wrote:
> Hi Peter,
> Thanks for your important comments.
> It seems that we have a consensus that the use-case described in the 
> draft is valid.
> I've heard some people say that flex-algo has already supported this 
> l2-bundles scenario, no additional definition is needed. This seems 
> that, from the view of some people, the use-case need to be solved 
> through flex-algo itself.

no, flex-algo does not have any support for l2-bundles at this point.

> The solution currently described in this document may not be mature, but 
> the direction may not be wrong ?

as I expressed earlier, my preference would be to keep the flex-algo 
being based on L3 link information only and not to use L2 link 
information during the flex-algo computation. There are other ways to 
solve your problem. But I will let the WG to discuss and decide.

> Others please see inline [PSF].
> Regards,
> 原始邮件
> *发件人:*PeterPsenak
> *收件人:*;
> *日 期 :*2021年03月09日 18:08
> *主 题 :**[Lsr] draft-peng-lsr-flex-algo-l2bundles*
> Dear authors,
> here are couple of comments to draft-peng-lsr-flex-algo-l2bundles:
> 1. Flex-algo specification as specified in draft-ietf-lsr-flex-algo only
> uses L3 link information for path computation. This is consistent with
> the regular Algo 0 path computation. My preference would be to keep it
> that way.
> *[PSF] There maybe one way not to violate this rule, but more complex. *
> *[PSF] Currently for an L3 link there are multiple Application specific 
> attributes, is it possible for an application (such as Flex-algo) there 
> are multiple APP Instance specific attributes ? For example, an 
> L2-bundle interface can have multiple Flex-algo APP instance delay 
> metric, for algorithm-128 the delay metric is 10ms (exactly get from the 
> dynamic detection of member link 1), for algorithm-129 the delay metric 
> is 20ms (exactly get from the dynamic detection of member link 2), for 
> algorithm-0 the delay metric get from the dynamic detection of bundles 
> itself.** However I don't like the this way. Other ways?*

what you are proposing above is a per flex-algo ID link attributes, but 
I don't believe that is the direction we want to go. It does not scale.

> 2. Flex-algo is not a replacement for SRTE. The problem that you are
> trying to solve can be solved by SRTE with the usage of the L2 Adj-SIDs.
> *[PSF] Flex-algo is constraint based SPF, for the initial purpose, is 
> SID stack depth optimization for SR-TE path ? It's hard to convince 
> operators by just saying that "the problem is out the scope of 
> Flex-algo" when he has already selected Flex-algo *to reduce the number 
> of Adj-SIDs.**

Flex-algo is constraint based SPF, but so far based on L3 link 
information only.

> 3. Usage of the L2 link data for flex-algo path computation is much more
> complex than defining the L-flag in the FAD. You would need to deal with
> things like:
> a) conflicting information in L3 and L2 link information
> b) missing information in L3 or L2 link information
> *[PSF] Yes, more computation rules need be added based on the existing 
> ones defined in draft-ietf-lsr-flex-algo. I think it's no more complex 
> than Flex-algo itself.*

the question is how much extra complexity do we want to add for the 
benefit it brings.

We need to consider how frequent is the use case that you describe 
present in the field and whether existing mechanisms like SRTE, or usage 
of L3 links instead if L2 bundles in such case, are not sufficient to 
address the problem.

The fact that it is possible to address the problem by flex-algo does 
not mandate the usage of it.


> which would require to define a strict path computation preference rules
> and conflict resolutions that all routers would need to follow. I would
> argue that this is much easier to be done with SRTE, where the logic to
> select the path is a local matter compared to consistency in path
> selection that is required for distributed calculation used by flex-algo.
> *[PSF] Unfortunately we are now in the context of Flex-algo, not SR-TE.*
> thanks,
> Peter
> _______________________________________________
> Lsr mailing list