IETF Logo Mail Archive

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

Christian Hopps <chopps@chopps.org> Mon, 27 August 2018 12:10 UTC

Return-Path: <chopps@chopps.org>
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 8E90C130E71 for <lsr@ietfa.amsl.com>; Mon, 27 Aug 2018 05:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 7ArPboHGZJvG for <lsr@ietfa.amsl.com>; Mon, 27 Aug 2018 05:10:37 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 216B7130DD1 for <lsr@ietf.org>; Mon, 27 Aug 2018 05:10:37 -0700 (PDT)
Received: from [192.168.2.5] (47-50-69-38.static.klmz.mi.charter.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 46EC4611B4; Mon, 27 Aug 2018 12:10:36 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <3158427D-B667-4F3B-82DF-FD022074ED27@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_AA6C2F57-924B-4DBB-B475-6A48DD19875D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 27 Aug 2018 08:10:34 -0400
In-Reply-To: <39509D13-4D2D-49A9-8738-C9D1F7C54223@tony.li>
Cc: Christian Hopps <chopps@chopps.org>, Tony Przygienda <tonysietf@gmail.com>, lsr@ietf.org, Jeff Tantsura <jefftant.ietf@gmail.com>, Peter Psenak <ppsenak@cisco.com>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
To: Tony Li <tony.li@tony.li>
References: <8F5D2891-2DD1-4E51-9617-C30FF716E9FB@cisco.com> <C64E476F-1C00-435E-9C74-BEC3053377E8@gmail.com> <2F5FDB3F-ADCA-4DB4-83DA-D2BC3129D2F2@gmail.com> <5B7E78DD.90302@cisco.com> <172728E8-49E6-4F43-9356-815E1F4C22E7@gmail.com> <5B7FCAB3.6040600@cisco.com> <3D1DEC37-ACE7-4412-BB2E-4C441A4E7455@tony.li> <CCF220A3-8308-47B8-8CC6-1989705FF05C@cisco.com> <CA+wi2hNv8AVyR81LRmJ=Pd5_p5rS2djCOjY9YDgKxG=KEO_MkA@mail.gmail.com> <39509D13-4D2D-49A9-8738-C9D1F7C54223@tony.li>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/THweQm1hYdKlysJT-8oh18bHVq0>
Subject: Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 27 Aug 2018 12:10:39 -0000


> On Aug 24, 2018, at 12:29 PM, tony.li@tony.li wrote:
> 
> Being distributed would be very nice.  However, that implies that all nodes are going to get to the exact same solution. Which implies that they all must execute the same algorithm, presumably with the same inputs.
> 
> That’s all well and good, but we don’t have an algorithm to really put on the table yet.  We need experience with one.  We know we want to tweak things based on biconnectivity, performance, and degree because doing it right day one seems unlikely.  Changing algorithms is going to be VERY painful if it’s distributed.
> 
> However, if it’s centralized, it’s completely trivial.

I find this reasoning quite compelling.

Thanks,
Chris.

v2.23.0 | Report a Bug | By Email