Re: [Lsr] WG Adoption Call for "IGP Flexible Algorithms (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01

Huzhibo <> Fri, 11 December 2020 09:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9550B3A0844 for <>; Fri, 11 Dec 2020 01:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 5sKzYV4sDQyX for <>; Fri, 11 Dec 2020 01:40:01 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1AECB3A0820 for <>; Fri, 11 Dec 2020 01:40:01 -0800 (PST)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4Csm093QVzz67MNq for <>; Fri, 11 Dec 2020 17:37:13 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Fri, 11 Dec 2020 10:39:53 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 11 Dec 2020 17:39:51 +0800
Received: from ([]) by ([]) with mapi id 15.01.1913.007; Fri, 11 Dec 2020 17:39:51 +0800
From: Huzhibo <>
To: Peter Psenak <>, "Dongjie (Jimmy)" <>, "Acee Lindem (acee)" <>, lsr <>
Thread-Topic: [Lsr] WG Adoption Call for "IGP Flexible Algorithms (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01
Thread-Index: AQHWyCa69SgvuXvqQUSruOMjcUOnRanukOqg//+JYYCAAJ+NMP//h7yAgACWrCCAALhHgIAAjD2w//+7mIAANZ9iQP//n+8A//91SPA=
Date: Fri, 11 Dec 2020 09:39:51 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Lsr] WG Adoption Call for "IGP Flexible Algorithms (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01
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, 11 Dec 2020 09:40:04 -0000

Hi Peter:

Following this approach, IP and SR Flex-Algo can also be distinguished by using different FA IDs, thus there is no need to treat them as separate applications, and the existing SR FAD TLV can be reused?
My suggestion is to have a clear and consistent rule in FA participation, either defining application-specific FA partifcipation for each data plane (IPv4, IPv6, SR-MPLS, SRv6, etc.), or do not define any applications and simply use different FA IDs to distinguish them.  

-----Original Message-----
From: Lsr [] On Behalf Of Peter Psenak
Sent: Friday, December 11, 2020 5:13 PM
To: Dongjie (Jimmy) <>om>; Acee Lindem (acee) <>rg>; lsr <>
Subject: Re: [Lsr] WG Adoption Call for "IGP Flexible Algorithms (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01

Hi Jimmy,

On 11/12/2020 09:17, Dongjie (Jimmy) wrote:
> Hi Peter,
>> -----Original Message-----
>> From: Peter Psenak []
>> Sent: Thursday, December 10, 2020 9:22 PM
>> To: Dongjie (Jimmy) <>om>; Acee Lindem (acee) 
>> <>rg>; lsr <>
>> Subject: Re: [Lsr] WG Adoption Call for "IGP Flexible Algorithms 
>> (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01
>> Hi Jimmy,
>> On 10/12/2020 13:02, Dongjie (Jimmy) wrote:
>>> In Flex-Algo draft, it says:
>>> "Application-specific Flex-Algorithm participation advertisements 
>>> MAY be
>> topology specific or MAY be topology independent, depending on the 
>> application itself."
>>> The preassumption of current IP Flex-Algo participation is that one 
>>> node
>> always participate in a Flex-Algo for both IPv4 and IPv6, and for all 
>> the topologies it joins.
>>> I'm not saying this does not work, just want to understand the 
>>> reason of this
>> design, and whether some flexibility (e.g. AF specific or topology 
>> specific) would be useful in some cases.
>> this was the choice of authors, because there does not seem to be a 
>> string reason to do it per topology.
>>> BTW, a similar case is about SR-MPLS and SRv6 being treated as a 
>>> single
>> application. Below is the discussion quoted from a previous mail on this list:
>>>     [Jie] OK. While the meaning of "app" here maybe a little vague, 
>>> are
>> SR-MPLS and SRv6 considered the same or different apps?
>>>     [Peter] These are considered as single app, and share the same
>> participation signaling. Please note that SRv6 support is signaled 
>> independently of FA participation.
>>> Does this imply that for Flex-Algo path computation with SRv6, in 
>>> addition to
>> the Flex-Algo participation information, the SRv6 support information 
>> of nodes also needs to be considered, so that nodes participate in 
>> this Flex-Algo but do not support SRv6 will be pruned from the topology?
>> no.
> Let me elaborate with an example:
>        20   20
>      A------B-------C
>   10 |  10 |    /
>      |    |   /  10
>      D------E --*
>        10
> (The metrics on the links are delay metric)
> - Flex-Algo 128 is defined to use delay metric for computation. This FAD is application independent, thus can be used by all applications.
> - All of the nodes (A, B, C, D, E) participate in FA 128.
> - Node A, B, C, D support both SR-MPLS and SRv6.
> - Node E support SR-MPLS only, it may support IPv6.
> Then node A computes the path to node C with FA 128. According to the computation rules of FA 128, the path would be A-D-E-C. This path can be used to send SR-MPLS packet to node C.
> But if node A sends SRv6 packets with node C's SRv6 SID in FA 128 as the destination address, when the packet arrives at E, it will be dropped, because node E does not have the forwarding entry for C's SRv6 SID in FA 128.
> Do you think this is a problem?
> IMO this problem is due to the FA calculation is based on the combination of the constraints in FA definition, and the nodes' FA participation (which is app specific), while since SR-MPLS and SRv6 are treated as one single application, the difference in supporting SR-MPLS or SRv6 is not considered in FA calculation. This is why I asked whether the SRv6 support information also need be considered in FA calculation.
> To solve this problem, there are several options:
> Option 1: Define two different Flex-Algos for delay metric computation, one for SR-MPLS, the other one for SRv6. But this makes the FAD application dependent.

Option 1 is the right one, given the way things are defined. And honestly I do not see a need to change it.

> Option 2: Include the SR-MPLS or SRv6 information in Flex-Algo participation, i.e. make SR-MPLS and SRv6 separate applications.

Theoretically you can make SR MPLS and SRv6 a different applications 
using FA. Given the SR nature of both we intentionally kept them as a 
single app from FA perspective.

> Option 3: Also consider the SRv6 (or SR-MPLS) capability information in FA calculation.

no. This is not being done for algo 0 either and it has nothing to do 
with FA.


> Or do you have other options in mind?
> Best regards,
> Jie
>> thanks,
>> Peter
>>> If so, IMO this needs to be specified in the Flex-Algo draft. If not, please
>> clarify how to prune the nodes which participate in the same Flex-Algo for
>> SR-MPLS only? Thanks.
>>> Best regards,
>>> Jie

Lsr mailing list