Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

Jeff Tantsura <jefftant.ietf@gmail.com> Sat, 02 February 2019 04:37 UTC

Return-Path: <jefftant.ietf@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 8E096130EB8 for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 20:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 5YxiPe4cHP8e for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 20:37:01 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 AC08A124D68 for <lsr@ietf.org>; Fri, 1 Feb 2019 20:37:01 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id y126so4245275pfb.4 for <lsr@ietf.org>; Fri, 01 Feb 2019 20:37:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6+BI5G0eU9b2vDOFeen4ElHzTi+IdtVmK2hRQMnovQU=; b=PwXYqa5MItuoE6oDZA1P5VhsmNSL6V+w+oGGHAgil7Gn0tyD/A57w54SLGeDdIWJwk Ph2WUj8UqkPOV14KI00USrMxWiNr1BdTQsT3S/55FNQvpJ71V/8XPfoieeA//jnLjaNv L9/IhZRzH0BEpFWHsQIDByNLifJlEqJWLAR4mbP8eKwan1TtXkkQ/rXkEyJ+ctYCRtSy urgTwgn1LFH7jnnkv+Kn3DWM8MezIZTsKZhG/qXmS+xW2HWivMIPdFU4VRgWu4q4JBpU g4nZkecmZW16K5p6dXUd7ptDzL1mSLEU9A/kZvGvSZ89JluGXPbkjVT/khhdedoRjVvA 8/Ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6+BI5G0eU9b2vDOFeen4ElHzTi+IdtVmK2hRQMnovQU=; b=FfM7muQVnrhyJ30yaWY6K7jXWT6CbqRCHQw4ZAjplORnYhF3/F73PhfgE4XYwDOAZC XpqxhCmfmlW02Ba026GtUwXKYWmN0nVfCmlWf7byi9JqttEdYRyzU3Zo5FXgWKQcEiGH 0TXknOhArR46tGZvezoRCA1G2ob14lvbWtRer5yCUrJimHElQPuxLTB2qfUlsG4BkJgq HeAfWNO04WHj0z+rngnu3ruQMI0JUMlCANCO5zQu/Oqgeo6UV+hzcPHtAze8ZYdPqrsL kKIHUAPc+MAlyax9Ohk8aTOruOTJAmRh3b3yRGvD5qmGhcMHsEQehiR6F8Xkh1vufdpT Jpow==
X-Gm-Message-State: AJcUukfFY32gzfsSc5OvSOcJMNsNDFVuFb324LV/DQB5VGWLzyO1KSJu fzCKo1ZcQMLAmdVbMMyuoWzE9QeC
X-Google-Smtp-Source: ALg8bN7SWIUqZvw4cqhLynnUnkbKQuDFfIdSOfYvb5GiZNu/4fe7LRNSH5cvY43G6704Nn7okFH8Ew==
X-Received: by 2002:a62:2082:: with SMTP id m2mr41367684pfj.163.1549082220683; Fri, 01 Feb 2019 20:37:00 -0800 (PST)
Received: from [192.168.1.12] (c-73-189-13-44.hsd1.ca.comcast.net. [73.189.13.44]) by smtp.gmail.com with ESMTPSA id h185sm15123488pfg.143.2019.02.01.20.36.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 20:36:59 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Jeff Tantsura <jefftant.ietf@gmail.com>
X-Mailer: iPhone Mail (16C101)
In-Reply-To: <a86b8b3945534445a74a31c09184b71e@XCH-ALN-001.cisco.com>
Date: Fri, 01 Feb 2019 20:36:55 -0800
Cc: Christian Hopps <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B821CEB-D4DC-456A-90D4-C4D7D0A186CF@gmail.com>
References: <sa65zu31zqk.fsf@chopps.org> <sa64l9n1yqy.fsf@chopps.org> <a86b8b3945534445a74a31c09184b71e@XCH-ALN-001.cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4nmLlboSLvJ95STbTi6aDYn3dDk>
Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
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: Sat, 02 Feb 2019 04:37:05 -0000

In favor!

Regards,
Jeff

> On Feb 1, 2019, at 08:02, Les Ginsberg (ginsberg) <ginsberg@cisco.com> wrote:
> 
> I am in favor of this proposal.
> 
>   Les
> 
>> -----Original Message-----
>> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Christian Hopps
>> Sent: Friday, February 01, 2019 4:26 AM
>> To: lsr@ietf.org
>> Cc: chopps@chopps.org
>> Subject: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
>> 
>> 
>> Summary of where we are at with dynamic flooding reduction:
>> 
>> - We have a well written original work that came first and described the
>> problems as well as a TLVs to allow for a centralized solution (draft-li-
>> dyanmic-flooding). We do not need to standardize the centralized algorithm.
>> 
>> - A small change to this work allowed for distributed algorithms and for
>> outside work on distributed algorithms to continue in parallel.
>> 
>> - We have another original work that started primarily as a distributed
>> algorithm
>>   (draft-cc-ospf-flooding-reduction)
>> 
>> - Finally we also have:
>>   - Cross-pollination of ideas.
>>   - Failed attempts at merging.
>>   - An authors list "Arms-Race".
>> 
>> Moving forward:
>> 
>> - During IETF 103 I proposed we have no conflict if we:
>> 
>>   1) adopt draft-li-lsr-dyanmic-flooding as the base WG document.
>>   2) have authors of draft-cc-lsr-flooding-reduction work on a distributed
>> algorithm as they started with.
>> 
>> - Acee agreed during the meeting (as chair) that this was the best way
>> forward. We had some agreement form the floor as well.
>> 
>> - Any good ideas regarding the distribution of a centralized topology can be
>> debated and added (with appropriate attribution) to the base document
>> after we adopt one.
>> 
>> - This is what happens when we adopt a document as WG work, we work on
>> it.
>> 
>> - The original authors of the distributed solution can continue to work on
>> their distributed algorithm in a separate document which would also need
>> standardization.
>> 
>> Does anyone see a serious problem with this path forward?
>> 
>> Thanks,
>> Chris & Acee.
>> LSR Chairs.
>> 
>> Christian Hopps <chopps@chopps.org> writes:
>> 
>>> We've had the authors of the individual conflicting drafts take a shot at
>> merging their work.
>>> 
>>>   This has failed.
>>> 
>>> Here is the full history (which I also summarized during IETF103 as well). I
>> will send a second email discussing this.
>>> 
>>> - Jan 2, 2018 Publication: draft-li-dynamic-flooding and drfat-li-dynamic-
>> flooding-isis
>>>  published centralized solution.
>>> 
>>> - Mar 5, 2018 Publication: draft-cc-isis-flooding-reduction and draft-cc-ospf-
>> flooding-reduction
>>>  published distributed solution.
>>>  - mention of centralized solution asserting it is not good choice.
>>> 
>>> - IETF 101 (Mar 2018)
>>>  - Video:
>> https://www.youtube.com/watch?v=qHmT4ytMn4w&list=PLC86T-
>> 6ZTP5j_HaBNdfPbgxGIp22cnaWS
>>>  - Minutes: https://datatracker.ietf.org/meeting/101/materials/minutes-
>> 101-lsr-00
>>>  - draft-li-dynamic-flooding-02 presented (1 author). at IETF 101
>>>    - Generally well received.
>>>  - draft-cc-ospf-flooding-reduction-00 (4 authors) presented.
>>>    - Serious problems immediately found during presentation -- not fully
>> baked.
>>> 
>>> - Mar 18, 2018 draft-li-dynamic-flooding-03 published (1 author)
>>> - Mar 27, 2018 draft-li-dynamic-flooding-04 published (1 author)
>>> - Apr 20, 2018 draft-cc-ospf-flooding-reduction-01 revised
>>> - Jun 28, 2018 draft-li-dynamic-flooding-05 published (2 authors)
>>>  - *SMALL CHANGE TO SUPPORT DISTRIBUTED ALGORITHM*.
>>>  - Does not specify distributed algorithm only how to indicate one in use,
>> small change.
>>> 
>>> - Jul 2, 2018 draft-cc-ospf-flooding-reduction-02 published
>>> 
>>> - IETF 102 (Jul 14, 2018)
>>>  - draft-li-dynamic-flooding-05 presented.
>>>  - draft-cc-ospf-flooding-reduction-02 presented.
>>> 
>>> - Sep 12, 2018 draft-cc-ospf-flooding-reduction-03 (4 authors)
>>>  - *LARGE CHANGE ADDS NEW CENTRALIZED SOLUTION*.
>>> 
>>> - Sep 20, 2018 draft-cc-ospf-flooding-reduction-04 (4 authors)
>>> 
>>> - Oct 21, 2018 draft-li-lsr-dynamic-flooding-00 and -01 (5 authors)
>>> 
>>> - IETF 103 (Nov 3, 2018)
>>> 
>>>  - Chairs give direction
>>> 
>>>    - draft-li-lsr-dynamic-flooding-05 having come first, being well written
>> and not
>>>      specifying a distributed algorithm (merely allowing for one) is the correct
>> vehicle
>>>      to adopt as a base document.
>>> 
>>>    - Distributed algorithm work (the original basis for draft-cc-ospf-flooding-
>> reduction)
>>>      should continue as a separate document form the base which would
>> thus we have no
>>>      conflicts.
>>> 
>>> - In the meantime the authors try and merge work, this fails.
>>> 
>>> - Dec 3, 2018 draft-li-lsr-dynamic-flooding-02 (7 authors)
>>> 
>>> - Dec 10, 2018 draft-cc-lsr-flooding-reduction-00 (4 authors)
>>> 
>>> - Jan 7, 2019  draft-cc-lsr-flooding-reduction-01 (8 authors)
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr