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

Huaimo Chen <huaimo.chen@huawei.com> Sun, 03 February 2019 16:45 UTC

Return-Path: <huaimo.chen@huawei.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 9B7A6130FAB for <lsr@ietfa.amsl.com>; Sun, 3 Feb 2019 08:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 aza7lqE7xUe1 for <lsr@ietfa.amsl.com>; Sun, 3 Feb 2019 08:44:56 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0B01286D9 for <lsr@ietf.org>; Sun, 3 Feb 2019 08:44:56 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 610A056614FEFC436205; Sun, 3 Feb 2019 16:44:53 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 3 Feb 2019 16:44:52 +0000
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.95]) by SJCEML701-CHM.china.huawei.com ([169.254.3.144]) with mapi id 14.03.0415.000; Sun, 3 Feb 2019 08:44:47 -0800
From: Huaimo Chen <huaimo.chen@huawei.com>
To: David Allan I <david.i.allan@ericsson.com>, "li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com>, "robert@raszuk.net" <robert@raszuk.net>, "chopps@chopps.org" <chopps@chopps.org>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
Thread-Index: AQHUuilbECC1DxP5/E+8dX31Ej0g66XOvPaA//+DPNA=
Date: Sun, 03 Feb 2019 16:44:47 +0000
Message-ID: <5316A0AB3C851246A7CA5758973207D463B462E0@sjceml521-mbx.china.huawei.com>
References: <sa65zu31zqk.fsf@chopps.org>, <sa64l9n1yqy.fsf@chopps.org>, <CAOj+MMHVzuhfUNB+U_wLZ6M1KSPzJ_UNNAMwO0q5t9N3BoVoyQ@mail.gmail.com> <SG2PR06MB23139237E9A2CB6918C571C2FC6C0@SG2PR06MB2313.apcprd06.prod.outlook.com> <MN2PR15MB34394D9C30E039673757ABEDD06C0@MN2PR15MB3439.namprd15.prod.outlook.com>
In-Reply-To: <MN2PR15MB34394D9C30E039673757ABEDD06C0@MN2PR15MB3439.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.212.247.135]
Content-Type: multipart/alternative; boundary="_000_5316A0AB3C851246A7CA5758973207D463B462E0sjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/SUKvICzFeeBnoFoWOybSK-DdL0k>
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: Sun, 03 Feb 2019 16:45:06 -0000

Hi Dave,

There are two drafts containing the centralized solution and distributed solution already on the table too. If the two drafts are adopted, they need to be updated for one draft to focus on the centralized solution and the other on the distributed solution. The former will have all the good parts for the centralized solution, and the latter will have all the good parts for the distributed solution.

Best Regards,
Huaimo
From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of David Allan I
Sent: Sunday, February 3, 2019 10:32 AM
To: li_zhenqiang@hotmail.com; robert@raszuk.net; chopps@chopps.org
Cc: lsr@ietf.org
Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

With all respect,  there are other distributed solutions on the table…

Cheers
Dave

From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of li zhenqiang
Sent: Sunday, February 3, 2019 1:28 AM
To: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>; Christian Hopps <chopps@chopps.org<mailto:chopps@chopps.org>>
Cc: lsr <lsr@ietf.org<mailto:lsr@ietf.org>>
Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

Hello all,

At current situation, I think we'd better move both the two drafts foward in parallel keeping draft-li-dyanmic-flooding focus on  the centralized solution and  draft-cc-ospf-flooding-reduction on the distributed solution. Thanks.

Best Regards,
Zhenqiang Li
________________________________
li_zhenqiang@hotmail.com<mailto:li_zhenqiang@hotmail.com>

From: Robert Raszuk<mailto:robert@raszuk.net>
Date: 2019-02-02 20:20
To: Christian Hopps<mailto:chopps@chopps.org>
CC: lsr<mailto:lsr@ietf.org>
Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
Sound like best plan fwd.

Thx,
R.

On Fri, Feb 1, 2019, 13:26 Christian Hopps <chopps@chopps.org<mailto:chopps@chopps.org> 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<mailto: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<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr