Re: [Lsr] Dynamic Flooding on Dense Graphs - draft-ietf-lsr-dynamic-flooding

Tony Li <tony.li@tony.li> Tue, 14 June 2022 22:52 UTC

Return-Path: <tony1athome@gmail.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 37FD3C15AAE5 for <lsr@ietfa.amsl.com>; Tue, 14 Jun 2022 15:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.508
X-Spam-Level:
X-Spam-Status: No, score=-1.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b9d92WWUwh3E for <lsr@ietfa.amsl.com>; Tue, 14 Jun 2022 15:52:18 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30084C15AADD for <lsr@ietf.org>; Tue, 14 Jun 2022 15:52:18 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id o17so8938677pla.6 for <lsr@ietf.org>; Tue, 14 Jun 2022 15:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7GdpZVYIlNlRQVyhWuSWwh92+VQKRWpglgDLLkwmpMM=; b=dlsVt9LS+98NL8JXWT5ZDnKcMQ/riLdCznk3T6yUqsdeDlgzM83gq6YcEPCLWSOd/n QYOdxJCWedSEcmg2JzekLcbC9ozlPy2/2kQ8sYwpbIFOK/24vpRvMLC5IQjGa07O9SY9 /BmAiT+1SOlAarQUPC8oaKpnpqw3/4WSi16qeUz8Prpow5FS9HBZvVol44HEsYfM8a1U zAADPTe1BXCHZik1AslRrIyOqRlOqoTPwQeAlMg++Wp0d9t+qpYGIk75nQNCbG9DCGof Wr2VHY7n/7pr8kGF4baRbjbF9saBppazT0rARrYyYYrUWzw0VZPcQgcZTQbuGl5bxG+v kzig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=7GdpZVYIlNlRQVyhWuSWwh92+VQKRWpglgDLLkwmpMM=; b=7wZjfMKjFoK4ft2Lyz7FB3At+rH4xwktQAC6f20wW+Qyw+6EI2Xy+rg9uA1Vm5bzij hYFFZDbcAhgv9QDhkfjHHLiUwR7JCa78Fo/DEBmXDMenkHqtNdTStwgZK/Cmk6mZxtnt Slm/WrHheeITXMcOY45lyLdbFesVMWZM5sOchRb3xcO/eSt3OzrWXm8Hsq2w2ja13UHc 8+IJXVXdQx0q+sB4ZeLI/4ICyIqHbpEUjBlRX5z9iy+qvrpMBq5PSabpOP9VKRUJSr5e H5GzHaR0KUgPCdfjboUEpCsxmme8WSpqLiNQkf/DKPVrjL4gx2Z1tf2OWxMc8GPAJNvy d5UQ==
X-Gm-Message-State: AJIora+R/1qcD3yHEhnt/aV+JibbI/4FbmkF5wG+fz8ofOHjjqdr32hp wulQ433Sz90TDAnGoI8TSZo=
X-Google-Smtp-Source: AGRyM1v6u2VdU8YQfdWgmNSPwgLtSWXGiFLmpPrTiLSRBqqO7xxz9fkGIJYJwRVroHeNAQRONeWcQQ==
X-Received: by 2002:a17:90b:4b83:b0:1e3:3ad3:612c with SMTP id lr3-20020a17090b4b8300b001e33ad3612cmr6684451pjb.87.1655247137519; Tue, 14 Jun 2022 15:52:17 -0700 (PDT)
Received: from smtpclient.apple (c-67-169-103-239.hsd1.ca.comcast.net. [67.169.103.239]) by smtp.gmail.com with ESMTPSA id e8-20020a170902784800b001645730e71bsm7785575pln.59.2022.06.14.15.52.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jun 2022 15:52:16 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAOj+MMEdZOhrWGmXkxxBQ3rgPaULbLLJn=FABHqZ0F-xQMXJtg@mail.gmail.com>
Date: Tue, 14 Jun 2022 15:52:15 -0700
Cc: Gyan Mishra <hayabusagsm@gmail.com>, John E Drake <jdrake=40juniper.net@dmarc.ietf.org>, "Acee Lindem (acee)" <acee@cisco.com>, John Scudder <jgs@juniper.net>, "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>, tom petch <ietfc@btconnect.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E3FBCE0-277A-4CA7-872D-834916610D0A@tony.li>
References: <AC1AF8B2-07D5-46CB-85B9-DC8607C5E88B@cisco.com> <AM7PR07MB6248CDBA763EF1A0BAF626ADA0AB9@AM7PR07MB6248.eurprd07.prod.outlook.com> <8C14FCF1-C477-4D9C-A7C2-2260F2B7B7A5@tony.li> <BY5PR11MB43377349791AE499BE49682DC1AB9@BY5PR11MB4337.namprd11.prod.outlook.com> <3E5027F4-5A78-4AC0-BB24-5A0E13D2F979@tony.li> <BY5PR11MB433717C52D1A960ED987EFA6C1AB9@BY5PR11MB4337.namprd11.prod.outlook.com> <0076DD08-6CCB-40F7-82F9-6A42257C0A50@juniper.net> <BY5PR11MB4337E1D6A9487B37DC600DE0C1AA9@BY5PR11MB4337.namprd11.prod.outlook.com> <BY3PR05MB8081E3E92BBD7AA4C28B433EC7AA9@BY3PR05MB8081.namprd05.prod.outlook.com> <BY5PR11MB4337AFA5277F57D824740835C1AA9@BY5PR11MB4337.namprd11.prod.outlook.com> <BY3PR05MB8081900E45C9E1CBFFD9C5B4C7AA9@BY3PR05MB8081.namprd05.prod.outlook.com> <CABNhwV2=-nqguuvgcrooeyBwkyPhNbAsqyE2J4+0PvYOEvXjWA@mail.gmail.com> <4AD1A78E-0EB9-401C-9A6F-91245C5B8B44@tony.li> <CAOj+MMEdZOhrWGmXkxxBQ3rgPaULbLLJn=FABHqZ0F-xQMXJtg@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/7o-lTvXVlKdXoPZhniiMAdA44QU>
Subject: Re: [Lsr] Dynamic Flooding on Dense Graphs - draft-ietf-lsr-dynamic-flooding
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
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, 14 Jun 2022 22:52:19 -0000

Robert,

> > So, can we PLEASE stop beating a dead horse?
> 
> Are you stating that computing dynamic flooding topologies has no use case outside of MSDCs or for that matter ANY-DCs ? 


There may be a zillion use cases. But there is not critical mass for deploying this feature or other flooding reduction features. The time to solve this problem was back BEFORE people decided to repurpose BGP to solve their problems.  Now, it’s a classic ‘installed base’ problem. People will only consider alternatives if an alternative path represents less pain than the established path. We’re not there. BGP wins.


> PS. It is true that folks even running 10 racks think BGP is the only choice for the underlay but to me this is failure of deployment folks in vendors to properly position each dynamic routing protocol then nothing else. 


Well, we can blame marketing all we want.  All I know is that we, as a group, failed to come together and present a unified front with interoperable implementations. That left us in a position where marketing is pushing rocks up hills and customers are waiting for the dust to settle. 

T