Re: [Lsr] Open issues with Dynamic Flooding

Peter Psenak <ppsenak@cisco.com> Tue, 05 March 2019 20:26 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 76D1C129508 for <lsr@ietfa.amsl.com>; Tue, 5 Mar 2019 12:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, RCVD_IN_DNSWL_HI=-5, 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 ydU4PPnKOoRw for <lsr@ietfa.amsl.com>; Tue, 5 Mar 2019 12:26:19 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AD6B130DEA for <lsr@ietf.org>; Tue, 5 Mar 2019 12:26:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2644; q=dns/txt; s=iport; t=1551817580; x=1553027180; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=wxTjwJZMn73S0TJA11SSWE9CTpabq1bwzkLuCKkikhc=; b=W/O7vTIV5cy+R7Wxlk0U3dxWhacRpjmQ5VK2AYdTGWzyr2bEsMlHH0Jp g9e99eCFP7Di8/hcMTmQtqPrDck11P3GUma4mY5OCzusRA/9iQPhhbw+H xItYQa6aMFfZGBIGf1Ibp9zVXWZVxiJtjD2hmEsmJkYPuQntlRT5E9JLl k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOAAAq235c/xbLJq1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBVAEBAQEBAQsBgWCCGieECIh5jHiaHA2EbAKETjcGDQEBAwEBAwEDAm0cDIVKAQEBAQIBDhUPAQUtFBALGAICJgICVxMGAgEBgx6BbgirQ4EvhUSEbIELJAGLPoFAP4ERJ4I9LoRadII9glcCikKZRQmSbgYZgXSFZIMiiC2dMoFdIoFWMxoIGxWDJ4k+hw4+AzCOSCqCIwEB
X-IronPort-AV: E=Sophos;i="5.58,445,1544486400"; d="scan'208";a="10561034"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Mar 2019 20:26:18 +0000
Received: from [10.60.140.54] (ams-ppsenak-nitro5.cisco.com [10.60.140.54]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTP id x25KQGmo001012; Tue, 5 Mar 2019 20:26:17 GMT
To: tony.li@tony.li
References: <AAD29CF0-F0CA-4C3C-B73A-78CD2573C446@tony.li> <c1adac3a-cd4b-130e-d225-a5f40bf0ef55@cisco.com> <F3C4B9B2-F101-4E28-8928-9208D5EBAF99@tony.li> <be28dbcf-8382-329a-229f-5b146538fabe@cisco.com> <966E5756-8CEF-47F4-8564-E23D38F0743E@tony.li>
Cc: lsr@ietf.org
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <c8f40acb-94fe-f42a-aa0a-3a42e0067be8@cisco.com>
Date: Tue, 05 Mar 2019 21:26:16 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <966E5756-8CEF-47F4-8564-E23D38F0743E@tony.li>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.60.140.54, ams-ppsenak-nitro5.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/MzMxlakfj-3tK7GEQbyrcOIYOvY>
Subject: Re: [Lsr] Open issues with Dynamic Flooding
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: Tue, 05 Mar 2019 20:26:21 -0000

Hi Tony,

On 05/03/2019 17:47 , tony.li@tony.li wrote:
>
> Hi Peter,
>
>>>> Adding all links on a single node to the flooding topology is not
>>>> going to cause issues to flooding IMHO.
>>>
>>>
>>> Could you (or John) please explain your rationale behind that? It
>>> seems counter-intuitive.
>>
>> it's limited to the links on a single node. From all the practical
>> purposes I don't expect single node to have thousands of adjacencies,
>> at least not in the DC topologies for which the dynamic flooding is
>> being primary invented.
>
>
> What if the node in question is one of the spines?  Folks are building
> systems that large… and it seems inevitable that port counts will only
> grow.  Toto, I don’t think that’s an AGS any more…. ;-)
>
>
>> In the environments with large number of adjacencies (e.g.
>> hub-and-spoke) it is likely that we would have to make all these links
>> part of the flooding topology anyway, because the spoke is typically
>> dual attached to two hubs only. And the incremental adjacency bringup
>> is something that an implementation may already support.
>
>
> LS topologies can have a very large number of adjacencies as well,
> typically with multiple spines, so for a new spine, all of the of the
> links may be unnecessary.

ok, we talked bout the balance before - adding one link at a time to the 
FT may result in slow recovery, while adding all link is claimed to be 
dangerous. What is the right number? I feel that the increment value can 
be something that the implementation can choose or even make 
configurable, so the user can decide based on the particular topology 
and scale. We are not going to find the magic value I'm afraid.

>
>
>>> Our simulations suggest that this is not necessarily optimal.  There
>>> are lots of topologies (e.g., parallel LANs) where this blanket
>>> approach is suboptimal.
>>
>> the question is how much are true LANs used as transit links in
>> today's networks.
>
>
> As Xiaohu suggested, the management plane would be an obvious
> application. Interconnects also seem likely.

I believe his case is completely orthogonal to this discussion as in his 
case there is a single giant LAN used for flooding and we all know we 
can not optimize flooding inside a LAN itself.

>
> Let’s set the algorithmic parts aside.  Do you have an objection to
> supporting them in the signaling?

will get complicated, especially for OSPF/OSPFv3. Also temporary 
flooding operation on LAN is tricky and sub-optimal. I don't really 
believe it's worth the complexity.

my 2c,
Peter

>
> Tony
>