Re: [Lsr] FW: New Version Notification for draft-white-distoptflood-00.txt

<7riw77@gmail.com> Mon, 01 April 2019 01:18 UTC

Return-Path: <7riw77@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 AA26E120041 for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 18:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v_r0841DjEdc for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 18:18:06 -0700 (PDT)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (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 1F04A120013 for <lsr@ietf.org>; Sun, 31 Mar 2019 18:18:06 -0700 (PDT)
Received: by mail-ot1-x332.google.com with SMTP id t8so7018655otp.7 for <lsr@ietf.org>; Sun, 31 Mar 2019 18:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=ZpbHrgcQWQF0/r8CE4/fO21CCT+o+RHrhSb+VjQUZ8A=; b=NSZLyjk75M7lGZ3CXc7bdJz6xifIQaSfk1PS8Z2U+VzPc7jIZMfEKCl2SjC2KI2I7l K1IBvizyE0eJhXXMIeglgvGPYnVuAtGWmztrlfUWEic3RlEOjggLg8kA5NE2rcTvnjLS 1anxHl7avCqm3exEnJF3IUk8/70apfI5zSBGwB2zSIxvEnvcJQB4HkX5PJhngM4DZw56 dl/BSuJjWc2RCY6TuKMShejNf9+IuYX7NPIoFTJ7C+tAQsam255hnom88R6SfQMW7EsH lZ3LiA3B2c6UxgS6Y8Zzp4WYZV3EJvHrY5sLuoQUe3aEajcCDnZTQpOE/eSzfCHvbumS Ibng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=ZpbHrgcQWQF0/r8CE4/fO21CCT+o+RHrhSb+VjQUZ8A=; b=WhN12MbGHa5322NqaT68hOJWvpTP/HDrhjJofXXYbhUq0Ei63zgUM/TSunN/Ma3M+C NpQWBcssZVI1lw0VMxl17EUyRExfHLkvFSJk/K3pqD+jg1kee2KkKSiVGcL1ElmD/2gm QgV0SIOY3hz3vbTzy4Q956HH0re0o81LGYrXwg3xUG4lW5IeDIdNWKD7Ixthqk++Hmv/ v31fhM9FgkuomQesDGmP78hSwRefUyYGBLpThoXx2M0lTPB4gO2PFxh72v1gUhJdXHXk LCysEw1cf9I5hCtp2pQK9zlcjKIJ1HenkTslzLmI6kJHglPEa2KBf3TruGdjHBXuv3ww +2XA==
X-Gm-Message-State: APjAAAU67Hg81j8kJPkpIOFGYbMhpv5eaFpIGOe08GAeMdeKqR8zlnuU nDKBVBYWjAkfcBZeyZXCS9U=
X-Google-Smtp-Source: APXvYqz4LPvzovsdfH96NVO+brV8HOhO/hLIhWTHEcoJ/baXo9A+t6USCOPjn3JBhqLk7HtMuFvtVQ==
X-Received: by 2002:a9d:7e91:: with SMTP id m17mr16962839otp.78.1554081485429; Sun, 31 Mar 2019 18:18:05 -0700 (PDT)
Received: from RussPC ([2600:1700:720:1050::440]) by smtp.gmail.com with ESMTPSA id v24sm3408005oic.32.2019.03.31.18.18.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 31 Mar 2019 18:18:05 -0700 (PDT)
From: 7riw77@gmail.com
To: "'Les Ginsberg (ginsberg)'" <ginsberg@cisco.com>, lsr@ietf.org
References: <155406381670.12357.17272312414769230549.idtracker@ietfa.amsl.com> <04bf01d4e7ff$e16d7230$a4485690$@gmail.com> <BYAPR11MB3638929C928DC680677E182DC1540@BYAPR11MB3638.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB3638929C928DC680677E182DC1540@BYAPR11MB3638.namprd11.prod.outlook.com>
Date: Sun, 31 Mar 2019 21:18:04 -0400
Message-ID: <073101d4e828$c2209c80$4661d580$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLwM/JIkPbzT8Vkdbi80JHv2Wjy+QFj45+JAYMdoeSj2LEcUA==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/RL0hjX-voSuVX_4uGBoVWH5DdUk>
Subject: Re: [Lsr] FW: New Version Notification for draft-white-distoptflood-00.txt
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: Mon, 01 Apr 2019 01:18:08 -0000

> The WG just went through a lengthy consideration of multiple flooding
> optimization drafts and selected https://datatracker.ietf.org/doc/draft-ietf-
> lsr-dynamic-flooding/ as the vehicle for the WG to use to move forward in
> this area.

Yep.

> It would be good if, in the context of the above, you articulated why it makes
> sense for the WG to do yet another round of such discussion.

==
In this idea, the flooding topology is computed within an IGP area
   with the dense topology either centrally on an elected node, termed
   the Area Leader, or in a distributed manner on all nodes that are
   supporting Dynamic Flooding.
==

Because this is only one way to solve the problem... The process outlined in the draft I just published is a different and simpler way that applies to a wider range of topologies than the dynamic flooding draft does, afaict. 

😊 /r