Re: [Lsr] Dynamic flooding path computation

Peter Psenak <ppsenak@cisco.com> Fri, 03 April 2020 08:11 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 99DC13A13E2 for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 01:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 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, 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 Y9cMKfR_AQAh for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 01:11:50 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 074913A13E1 for <lsr@ietf.org>; Fri, 3 Apr 2020 01:11:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2044; q=dns/txt; s=iport; t=1585901510; x=1587111110; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=qmw9B6IbLOqGk6amYfHIuHDYRnE8LVQnwrhnsGsS/mo=; b=GSWJSL5FPMnJX2JyJbf37loMssW4Dm618D+NUTBIK3D8TCW0uFy+EFMr f0l4bL+qb4cyq+4QP+5iDalBa7MXKY+NLMSU1iXXnXq6Q/AQu5f1kmwR/ BGDRrri8fxziqxCRfZt9ad5gLrYm4tPuA3Qg4Pc4TaADaaxvkNZwJKIN4 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BCAADT7oZe/xbLJq1mGQEBAQEBAQEBAQEBAQEBAQEBEQEBAQEBAQEBAQEBgXuBfYEYVSASKoQbiQGHYy2bRwoBAQEOGAsMBAEBhEQCgmc4EwIDAQELAQEFAQEBAgEFBG2FVgyFcQEBAQMBASEPAQU2GwsYAgImAgInMAcMBgIBAYMiAYJ8D61jdYEyhUuDZYE4BoEOKoxLgUE/gTiCaT6CZwEBhHeCXgSxBoJHgl6UOwYdjzeMQo8snEOBaSKBVzMaCBsVO4JpUBgNjikXgQQBCYYIgU6FQz8DMI9lAQE
X-IronPort-AV: E=Sophos;i="5.72,339,1580774400"; d="scan'208";a="24956974"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Apr 2020 08:11:47 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTP id 0338BkCK008884; Fri, 3 Apr 2020 08:11:46 GMT
To: tony.li@tony.li, lsr@ietf.org
References: <1E6B5060-2295-49CA-8303-1D85C6562F2B@tony.li>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <e438d781-3b91-d5ca-f7de-14fd83c605f0@cisco.com>
Date: Fri, 03 Apr 2020 10:11:46 +0200
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: <1E6B5060-2295-49CA-8303-1D85C6562F2B@tony.li>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.60.140.51, ams-ppsenak-nitro2.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/pxyek6Aq2QVC_XS_uI7ky4d0GTg>
Subject: Re: [Lsr] Dynamic flooding path computation
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: Fri, 03 Apr 2020 08:11:52 -0000

Hi Tony,

it may be worth to make your algorithm one of the standardized 
distributed algorithms. There might be some work to make it 
deterministic, like the selection rules mentioned below, but it should 
be doable.

What do you think?

thanks,
Peter

On 03/04/2020 01:57, tony.li@tony.li wrote:
> Hi,
> 
> In this morning’s session, Acee asked a question about node selection as part of path computation.  I would like to expound a bit in the spirit of full transparency.
> 
> First off, the selection of nodes is NOT vital to the algorithm.  That said, we found that applying some heuristics helped make the algorithm slightly more efficient in some cases.
> 
> We select the starting node for the first cycle (n0 in the slides) by picking a node with the highest possible degree in the base topology.  Ideally, we’d really like to pick the node that’s at the center of the graph (and to be very precise, a node in the centroid or Jordan center), but the computation of this is somewhat expensive and doesn’t seem worthwhile.
> 
> At the end of the first cycle, we now have a set of bi-connected nodes that each have a degree of 2 in the flooding topology.  We could start the next iteration with any of these nodes, but we already know that n0 has the highest degree of anything in the topology, so we can always start the next iteration based off of n0.  Note that we do NOT want to continue doing this for subsequent iterations because the degree of n0 would quickly spiral out of control.  Instead, we want to continue to bound the degree of the nodes in the flooding topology, so we want to select a node that is on the flooding topology, but minimizes both degree and diameter.  Again, we are not trying for optimality, so we apply a simple weighting function to aid in this selection.
> 
> I hope this makes our approach very clear.
> 
> Regards,
> Tony
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
> 
>