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

"Naiming Shen (naiming)" <naiming@cisco.com> Fri, 01 February 2019 22:44 UTC

Return-Path: <naiming@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 EA24A130ECE for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 14:44:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.053
X-Spam-Level:
X-Spam-Status: No, score=-19.053 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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 gqFGcdrg8yyQ for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 14:44:09 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51C6E130EBE for <lsr@ietf.org>; Fri, 1 Feb 2019 14:44:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4866; q=dns/txt; s=iport; t=1549061049; x=1550270649; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yb2QEe4rye7z5/f5m2RNsgUAng3G4qZfxK+I8bObZPs=; b=PjVi4Xp0WxdYxCMtjB5KOhgR493j09QRMcY+MlWluCCyb5BfGeZYvEpW xWcAXOvi6rUAVcWG4YlqosTWQ7+8q+CGfqm0ReuZaNIuC4T65+2yj3bms H08j/9Yuxk5hxLLUdRc8RMlm1QeVwSh4+8GqFem/YMIdcvfm1Ps14TjDv 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAC+ylRc/5NdJa1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNngQMnCowTi3SCDZgOFIFnCwEBGA2ERwKDESI0CQ0BAwEBAgEBAm0cDIVKAQEBAQIBAQE4NAsFCwIBCA4KHhAnCyUCBA4FG4MHAYF5CA+qK4QuAQMCAoENhGcFjEAXgX+BOB+CTIMeAQECAReBFAESAR+DOoImAolriBeFCotbCQKHLosGGZJAj0+MBQIRFIEnHzhlcXAVOyoBgkGGCoUUhT9BMYpsgR+BHwEB
X-IronPort-AV: E=Sophos;i="5.56,549,1539648000"; d="scan'208";a="511996146"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2019 22:44:07 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x11Mi75J025786 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 Feb 2019 22:44:07 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 1 Feb 2019 16:44:07 -0600
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1395.000; Fri, 1 Feb 2019 16:44:06 -0600
From: "Naiming Shen (naiming)" <naiming@cisco.com>
To: Christian Hopps <chopps@chopps.org>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
Thread-Index: AQHUuilUz8L5eC2t3UmKUZY6fVsz6qXL74gA
Date: Fri, 01 Feb 2019 22:44:06 +0000
Message-ID: <4D79F7C1-0A18-42B5-996B-61462C32C37E@cisco.com>
References: <sa65zu31zqk.fsf@chopps.org> <sa64l9n1yqy.fsf@chopps.org>
In-Reply-To: <sa64l9n1yqy.fsf@chopps.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.156.165.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7E54E99CA4FB9841A14D09BBE8A6E6C6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/28P8Aqj0EgPh0lrowMTxS1MI9pM>
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 22:44:12 -0000

Support the proposal.

Regards,
- Naiming

> On Feb 1, 2019, at 4:25 AM, Christian Hopps <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> 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