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

Peter Psenak <ppsenak@cisco.com> Fri, 01 February 2019 15:51 UTC

Return-Path: <ppsenak@cisco.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 50474130E6B for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 07:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.642
X-Spam-Level:
X-Spam-Status: No, score=-14.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 fePmcAaLxbh0 for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 07:51:20 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E00F130E25 for <lsr@ietf.org>; Fri, 1 Feb 2019 07:51:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4776; q=dns/txt; s=iport; t=1549036279; x=1550245879; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=ZOONU3Uv4hJkrmtOkewUizb39Pu70dVdSncVeqFaPJ8=; b=OEMtk8L5OVWOdteZLA02gBQEUNTseJ5Ct0qvU1BdnYgZdCt3A3oXLwm8 gIz3RPEEzec7OQF07rLKLilfh1KCMKe+DyQJOB+MFkbmLwb1Bm4nJQKoi W7fyhqRQ9oJIfQE1ZEq3qdZPDIEtUQLFm+H4iYJQxxXYhPqcz+kegT89L 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAABWalRc/xbLJq1kGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGCalABIBInjB1fjHQIJZgOFIFnDRgNhEcCgzM?= =?us-ascii?q?0CQ0BAwEBAgEBAm0cDIVLAQEBAwEBNjYbCw4KLicwBgEMBgIBAReDBwGCAQ+?= =?us-ascii?q?qXoQuAQMCAoENhG4FjFeBQD+BOAyCX4MeAQECAReBFAESAYV/AolrhwaBEYU?= =?us-ascii?q?Ki1sJhzCLAAYZikKHfooghS+MLIFGOGVxMxoIGxU7gmyGCoUUhUA+AzCKWII?= =?us-ascii?q?+AQE?=
X-IronPort-AV: E=Sophos;i="5.56,549,1539648000"; d="scan'208";a="9749556"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2019 15:51:16 +0000
Received: from [10.60.140.54] (ams-ppsenak-nitro5.cisco.com [10.60.140.54]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTP id x11FpF0F009290; Fri, 1 Feb 2019 15:51:16 GMT
To: Christian Hopps <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
References: <sa65zu31zqk.fsf@chopps.org> <sa64l9n1yqy.fsf@chopps.org>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <bcea3dc5-1071-f7bf-0153-e81e5ea820ea@cisco.com>
Date: Fri, 1 Feb 2019 16:51:15 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <sa64l9n1yqy.fsf@chopps.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.60.140.54, ams-ppsenak-nitro5.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/uk5hsrhEPH1RlTcCgTCepwQf3Gg>
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: Fri, 01 Feb 2019 15:51:22 -0000

Hi Chris,

sounds good to me.

thanks,
Peter

On 01/02/2019 13:25 , Christian Hopps wrote:
>
> 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
>