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

Peter Psenak <ppsenak@cisco.com> Thu, 10 December 2020 13:21 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71AA63A0DDA for <lsr@ietfa.amsl.com>; Thu, 10 Dec 2020 05:21:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.602
X-Spam-Level:
X-Spam-Status: No, score=-9.602 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_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LZ62tFPulpY for <lsr@ietfa.amsl.com>; Thu, 10 Dec 2020 05:21:47 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D261C3A0C54 for <lsr@ietf.org>; Thu, 10 Dec 2020 05:21:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1736; q=dns/txt; s=iport; t=1607606507; x=1608816107; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=nPHvTbBvnbNBst85UwhvqLDy85kghMQNyV51DxdUsjc=; b=FQ/WI85rHVCX8YnakvLJcH1u2XJNaFmV5YedTAmimjdMZJIOmVIxZ6uG p4Obl37E1UmrRKlhELtwO0fEcCK8lQ5VCvWYKzGY8KSx6dSuK1whv15u/ oJQsNuvd/KPrmT0kG0v7KuSfkex0qQV2iYOS0s9pbJhC9xqATHvsTU1Ae 8=;
X-IPAS-Result: A0BPBgCAINJf/xbLJq1iHQEBAQEJARIBBQUBQIFPg3YBIBKEbYkEh3sIKJwzCwEBAQ8vBAEBhEoCggAmOBMCAwEBAQMCAwEBAQEFAQEBAgEGBHGFbYVyAQEBAwEdBhVGCwsYAgIfBwICVwYBDAgBAYMigmcgrRZ2gTKFV4MwgUKBDiqNXoFBP4ERJwyCZT6EHAEBgzeCXwSCPWqBKoIYm0acGoJ+gyWYFAUHAx+DJYomhS2PQoYVjWuhTIFtI4FXMxoIGxU7gmpPGQ2OWI4TQANnAgYKAQEDCYpKAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.78,408,1599523200"; d="scan'208";a="29365350"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Dec 2020 13:21:38 +0000
Received: from [10.147.24.45] ([10.147.24.45]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id 0BADLbkf002601; Thu, 10 Dec 2020 13:21:38 GMT
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, lsr <lsr@ietf.org>
References: <777B2AC4-CACF-4AB0-BFC7-B0CFFA881EEB@cisco.com> <169b063524dc4420b37016d2428fc85c@huawei.com> <29d3d16a-237d-e657-e84c-c74a1e5a841f@cisco.com> <c779c9da19264b718effd3d0442c8616@huawei.com> <8024148b-df7d-d79f-26b6-c64b9113cd9e@cisco.com> <64d017200b9f449fb5866729c71af221@huawei.com> <ee59964d-1e9d-233a-254e-37f6141a9add@cisco.com> <db0277d7891a45d6917e84a219b880a3@huawei.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <c4d73cb1-8262-ee4e-5a7c-6a960b312b9f@cisco.com>
Date: Thu, 10 Dec 2020 14:21:37 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <db0277d7891a45d6917e84a219b880a3@huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.147.24.45, [10.147.24.45]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/iFykbU3gU8WCuQQjrlU3bYlJW18>
Subject: Re: [Lsr] WG Adoption Call for "IGP Flexible Algorithms (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Dec 2020 13:21:48 -0000

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.

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