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

tony.li@tony.li Fri, 24 August 2018 20:20 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 E6313130DDF for <lsr@ietfa.amsl.com>; Fri, 24 Aug 2018 13:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 97SnapAf4ruJ for <lsr@ietfa.amsl.com>; Fri, 24 Aug 2018 13:20:41 -0700 (PDT)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF6F130DC2 for <lsr@ietf.org>; Fri, 24 Aug 2018 13:20:41 -0700 (PDT)
Received: by mail-pf1-x42b.google.com with SMTP id x17-v6so5031354pfh.5 for <lsr@ietf.org>; Fri, 24 Aug 2018 13:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=amgaCY4kGGxm0fyAynOANl5PA6wpD2H7/vLR5juF4S4=; b=OT/9tFApOV7PQTvOUu3JS/q+FbnucI+I5aNasurmRAP8GkYNWeA1J5glYpZBOHA3Z+ OaEMZIp3rkWA4Mvobr1+ieS7P84w+OZ9e7u4WEeEU+M0pugclQY4sG7PmOKD20mmMqBo Arnwu15aIZtIdZkfTGfPqPz57GlqFO8kfJ2yLFJgPoTz3legelWI6FNzDUGqIUbr1JS6 bUsWod09ZqOEf0y29fLm3nTb7pj0RYeZPt5NJgT8pfG87HkUrbo6QYoGp3XkHnE6pLOt 1co7V8o8zZdeHenD/FyXHty3miJgdT6Wa4wqxmCb3TCYTA2+xuuklKoIVcXv0RM/NQA9 lzbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=amgaCY4kGGxm0fyAynOANl5PA6wpD2H7/vLR5juF4S4=; b=uKjxymFMS12FsMmLHTDMxDbI+xuWeshZjhabxNNXnQFu1i4GYahWnqpifnZWdoNObQ 9qDumwP5I2GOBezWva/Molw5bBHyJx001HqaBL2agjggBl+5pulK6yKykoy+MqxIUfPA /XVVi/7of6lxGL0tvWb52g340XoqGnjVitYiY88p/AJJpXGRZMOzRE9+bRh/A/q3yvxn OT7C6D2z9BOfTgA4Dl/Y0CceDKvs4YQLX67wr224v7DkMSQ8a1yGe9p/W8GjjMHk5TI1 b0AdJ1lq2WOWi9JzbASjpV1NqJvFjE4T42new6Ujynq38lphXm563zYIwq0dYx50igwC hauw==
X-Gm-Message-State: APzg51AEbMUioIUKOtHmwtZzikggabC4CnAhkOSxiQTGv0UtAXZ9/e9L WksKBqNIHiqVWcQC0xXpAbk=
X-Google-Smtp-Source: ANB0Vdbi3W3qrFZv+LR7RYdnvqs6t0KIRfHRv++GNkTB5MQ96BZaYCwDFjcNnVve1c+Ek091ZqCJHw==
X-Received: by 2002:a63:8442:: with SMTP id k63-v6mr3007774pgd.388.1535142041316; Fri, 24 Aug 2018 13:20:41 -0700 (PDT)
Received: from [172.22.228.216] ([162.210.130.3]) by smtp.gmail.com with ESMTPSA id z2-v6sm9102360pgv.12.2018.08.24.13.20.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Aug 2018 13:20:40 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: tony.li@tony.li
In-Reply-To: <5316A0AB3C851246A7CA5758973207D463ABCF95@sjceml521-mbx.china.huawei.com>
Date: Fri, 24 Aug 2018 13:20:39 -0700
Cc: Tony Przygienda <tonysietf@gmail.com>, "lsr@ietf.org" <lsr@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, Peter Psenak <ppsenak@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <54F4EE88-981B-4EB1-925B-B3573B28DAD3@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> <5316A0AB3C851246A7CA5758973207D463ABCF95@sjceml521-mbx.china.huawei.com>
To: Huaimo Chen <huaimo.chen@huawei.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/QGrpS6QUImulKc53-ei8LYkg3Fc>
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: Fri, 24 Aug 2018 20:20:43 -0000


> I think distributed is more practical too. 


I would appreciate more detailed insights as to why you (and others) feel this way.  It is not at all obvious to me.


> For computing routes, we have been using distributed SPF on every node for many years.


True, but that algorithm is (and was) very well known and a fixed algorithm that would clearly solve the problem at the time. If we were in a similar situation, where we were ready to set an algorithm in concrete, I might well agree, but it’s quite clear that we are NOT at that point yet.  We will need to experiment and modify algorithms, and as discussed, that’s easier with a centralized approach.


> In fact, we may not need to run the exact algorithm on every node. As long as the algorithms running on different nodes generate the same result, that would work. 


Insuring a globally consistent result without running the exact same algorithm on the exact same data will be quite a trick.  Debugging distributed problems at scale is already a hard problem.  Having different algorithms in different locations would add another order of magnitude in difficulty.  No thank you.

Tony