Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
John E Drake <jdrake@juniper.net> Thu, 14 February 2019 13:57 UTC
Return-Path: <jdrake@juniper.net>
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 AF265130E6C for <lsr@ietfa.amsl.com>; Thu, 14 Feb 2019 05:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 l2i7zJtSpI6c for <lsr@ietfa.amsl.com>; Thu, 14 Feb 2019 05:57:48 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 C606012D84D for <lsr@ietf.org>; Thu, 14 Feb 2019 05:57:47 -0800 (PST)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x1EDi0bL016202; Thu, 14 Feb 2019 05:57:41 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=amMKhjbEQHKG2MoxqVqxB73zmBqQ/o81fxLyeaXiKvM=; b=AFHzhg3JFaz2ohcScYSYdJv4492g5pkjb+N0yNrZtcSEO2fjefuKvq2ehO/Gr9V4ac7R DuNQyug/R0GhR1ZPex3jC9i70n8bXS9jpqrX+OmdiecO78ZnIq5oKZvJg+FSiV/+JoK6 kY8hQVPo1SNf3Rnb2Q1Ur7XgaUvXyTKm1mD50TuTzraf9LjJLVDtUhK2ZGAWtmBRFoFy r2EhnHoGJrLbnl7Wq99vsgHTaA/sc0eGltRDGocqKHLv5A+mCh+EdryTWARXbdftnZQL wSZrrtTjeZm8I8897WMbnTf2F0CuxmCzO7UFLt9b9z3GOnAKfM5mvQJiGLAxX1zbdduC lg==
Received: from nam04-co1-obe.outbound.protection.outlook.com (mail-co1nam04lp2055.outbound.protection.outlook.com [104.47.45.55]) by mx0b-00273201.pphosted.com with ESMTP id 2qn8w9g2n8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 14 Feb 2019 05:57:40 -0800
Received: from BYAPR05MB5029.namprd05.prod.outlook.com (20.177.230.211) by BYAPR05MB4870.namprd05.prod.outlook.com (52.135.235.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.7; Thu, 14 Feb 2019 13:57:37 +0000
Received: from BYAPR05MB5029.namprd05.prod.outlook.com ([fe80::b58f:10f1:a40b:abf7]) by BYAPR05MB5029.namprd05.prod.outlook.com ([fe80::b58f:10f1:a40b:abf7%4]) with mapi id 15.20.1622.016; Thu, 14 Feb 2019 13:57:37 +0000
From: John E Drake <jdrake@juniper.net>
To: Peter Psenak <ppsenak@cisco.com>, Huaimo Chen <huaimo.chen@huawei.com>, "Acee Lindem (acee)" <acee@cisco.com>, Christian Hopps <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
Thread-Index: AQHUuilQ2AhEojvKJEO+J5oQ2yEy9KXL+4UAgAJPrQCAAAO6AIAEQYiAgAvHngCAAKHCgIAAbBPA
Date: Thu, 14 Feb 2019 13:57:37 +0000
Message-ID: <BYAPR05MB50297AC638F8974BAC6A5006C7670@BYAPR05MB5029.namprd05.prod.outlook.com>
References: <sa65zu31zqk.fsf@chopps.org> <sa64l9n1yqy.fsf@chopps.org> <5316A0AB3C851246A7CA5758973207D463B3B9D8@sjceml521-mbx.china.huawei.com> <8378287F-27B9-4663-A22B-F8A2EC6C9FC3@cisco.com> <5316A0AB3C851246A7CA5758973207D463B46315@sjceml521-mbx.china.huawei.com> <f3dca967-9adc-d67f-2606-548624ceef91@cisco.com> <5316A0AB3C851246A7CA5758973207D463B4A6AB@sjceml521-mbx.china.huawei.com> <25021deb-2032-9fcc-4bf4-fcaaa21598b9@cisco.com>
In-Reply-To: <25021deb-2032-9fcc-4bf4-fcaaa21598b9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.1.100.23
dlp-reaction: no-action
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 11849046-3a50-4db8-1094-08d6928460f6
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4870;
x-ms-traffictypediagnostic: BYAPR05MB4870:
x-ms-exchange-purlcount: 4
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4870; 23:oBZdflMk5zzvpXfV0MhPsXQNfLPYMjVkCVzKKM8kqQx4ip4Gzpu5fxzyX/BPLhFPPVyGKVHCfWEWqDSVEypVPBek1q5JEjBYgsEu06ZpLwx11wLAVJe0idsqLm7x0O6mEdP18JrJT5EMDmZIlPROnaVPlEHUxxB8e1i9tfhQsAqgKUAFoqLOZUv0Baq9gKJTq3qtM/ctpTQVDj0l89t0LdUxbAsNFZoRpLwxRjzzoKxzitAixWnBktej0kMGRBE8ciklGaVy8uXVJNgQl/li5BMZX0ONkxunKgHjDxcAieAc+1gyuv5OxkXrS65sS5b0bt0F7GylZSkMByR1v9Py+bZ4ovZmYmfK0hJpUdqkDecqMspro6WbpKbneY3hirgzlC946xLum/zf6bXmLTnSPHCjFU2DxAteeuzGn4Afd6g62MhW7UqDZ8Fy/nja169dpnzpZK1/T27f2WBP9ZXUr15WH6dcGzDC/9K0au+zyLfrLEmggaLtQSla5fcKXl2GqZGb6HPLo8jqoaKA8JxTvbEMrtAc4VPMQsAA6Vag2lFtsSEki/Pc420QUSOr9aSn/mtJ0ahODDAQf4DPwdVMjrIEQ+Dq5RRa7GmlvYG1JYh31YZQXnb/ZdAx6qPvuX+bW2s8UJO2LfmEHLXFUEPLCuQZJmALus4avsH5B0z0HG3bqYD9nsuxAOa6IBeIXkj5DvKXwX4MHEtZNqxvrd7lli8QnI0AIsJIjSx4pGQb1VjibxGD04gspYS8MNCEVMqZMOJZz70tQaRvq7p6VvOp9kFWFJN9IVrRa5Aw7XSp4UYQHXm9zp/qWlbnMd7O8Q1uBSsgl1k62VrDF7Ve3fLdlOlrVGcVW1hmj105XesH7pFvl41jv5b8VgEvYpAgRrrHjWAr1IkULSRHv6rxISsSQrFYoc3eEkVRbA2Epxs9D91S/uQ7CvjE//9ETfhOv3Yb6CwQAeJycI6ZROSc1EIWmxDS+1yivX0V9WmdGOFzdEE97AuyXGvcuaE5iTR3Gr69J3B57k05DHtcc4dsB54Y/g8ZHc/c/eVKdsbhRezKPzlHobMT9fEsuQlN6I/Dtt+9qznvVkmKZw4hPPdSR7mYJb8Rdxd8SJO82QnoV8fu440hd4u/LxR85knNsDF2T95Izn3jTlGlfRXBfy7lr+7mrIcgNlKpy6N5KsTk67KJoUK1rUazFADuNrVxJ2/xpUq+JetetSuflbramRXgXVq228mCoC8TV70SZucdwjEU5bNQXvYO/ivgyoInqtivH4drMsP2gqhrmMieB794WBVJLPhdFFeYgFjN81huMeppTAe2QvmgNtHt+63hGWKhhzTGe0HOdcaTS7F3FOXi5JGX+KT9zspIuUuzpKWvKdqp+Sw=
x-microsoft-antispam-prvs: <BYAPR05MB487096C9E5E0C5DE63A0796FC7670@BYAPR05MB4870.namprd05.prod.outlook.com>
x-forefront-prvs: 09480768F8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(396003)(376002)(39860400002)(366004)(53754006)(199004)(189003)(13464003)(51444003)(55674003)(81156014)(86362001)(256004)(9686003)(186003)(6306002)(55016002)(316002)(6116002)(26005)(8936002)(11346002)(3846002)(446003)(8676002)(81166006)(66066001)(486006)(25786009)(6506007)(2501003)(53546011)(476003)(19627235002)(102836004)(30864003)(33656002)(71190400001)(93886005)(7696005)(478600001)(97736004)(305945005)(2906002)(71200400001)(68736007)(76176011)(99286004)(7736002)(966005)(110136005)(105586002)(6246003)(53936002)(6436002)(229853002)(106356001)(14454004)(74316002)(21314003); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4870; H:BYAPR05MB5029.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: PAGzjKTVHielJ+08iZJIRC4HQWNCTAlMvKnPbFueProPQAs9tUhF02glEK+js25TUUF/6SVXiiAdfRzpkB+rnrg5cDuEyBndjs4XVitUlJCsNjBWfSMFz4ytzpFW07Qqh/J48rRxTR9SkuZMJ2LwzFRxNMe4QVZ672Ry33oD5GPm5aE8hZsK943HLf43iWj8/WvSFpeJZb55CowFxqKM2Iqby/bHONmJ6w3cGzEYDV/pNDtsFUZSX5vtVLYEMp1GUQsr4+TdCEalPsfXBmNNCgpmgSLajbHbidpFBQt+aM+Gy8XFBnMzWUmz2iq2pzulwkN7F9QEp8/vzM5qr9L2Sg/GyNUFyQvll7wuzTXCfInP6nAShdAYjVzxUGhZVBPY78fP5aqqlxXQqb3MTYsRX4vdzC/WCUuzqelJ9Qugxbk=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 11849046-3a50-4db8-1094-08d6928460f6
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2019 13:57:37.7869 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4870
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-02-14_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1902140098
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/2iry-Fwuu90z_MEwO2g2JjWCmr4>
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: Thu, 14 Feb 2019 13:57:51 -0000
Hi, I completely agree with Peter. Yours Irrespectively, John > -----Original Message----- > From: Lsr <lsr-bounces@ietf.org> On Behalf Of Peter Psenak > Sent: Thursday, February 14, 2019 2:30 AM > To: Huaimo Chen <huaimo.chen@huawei.com>; Acee Lindem (acee) > <acee@cisco.com>; Christian Hopps <chopps@chopps.org>; lsr@ietf.org > Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux] > > Hi Huaimo, > > On 13/02/2019 22:50 , Huaimo Chen wrote: > > Hi Peter, > > > > My explanations/answers are in line below with prefix [HC]. > > > > -----Original Message----- > > From: Peter Psenak [mailto:ppsenak@cisco.com] > > Sent: Wednesday, February 6, 2019 4:58 AM > > To: Huaimo Chen <huaimo.chen@huawei.com>; Acee Lindem (acee) > > <acee@cisco.com>; Christian Hopps <chopps@chopps.org>; lsr@ietf.org > > Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux] > > > > Hi Huaimo, > > > > On 03/02/2019 17:58 , Huaimo Chen wrote: > >> Hi Acee, > >> > >> > >> > >> I agree with you on keeping the signaling for two modes. The > >> other parts for the distributed solution need to be removed. > > optimized flooding is not only about algorithm to calculate the flooding > topology and the way it is distributed/computed. It is also about local rules to > make sure the flooding remains consistent. These are _independent_ of > centralized/distributed modes. And it make no sense to specify these rules in > two drafts. > > > > There are no "other" parts specific for the distributed solution. > > > > [HC] Some behaviors for the distributed solution/mode are described in draft- > li-dynamic-flooding. For example, there are a few of places from page 27 to 30, > which define the behaviors specific for the distributed solution/mode. > > I strongly disagree. The fact that we say in centralized mode area leader > recomputes and in distributed mode all nodes recompute make no difference in > behavior. > > thanks, > Peter > > > > > draft-li-dyanmic-flooding defines: > > > > 1. the signalling that is common and used by both modes 2. distribution of the > flooding-topology, which is specific to centralized mode 3. common behavior of > the nodes that support the extension, which is independent of the mode of > operation. > > > > [HC] In addition to these, draft-cc-lsr-flooding-reduction defines more, > including concrete protections, operations, and algorithms for computing a > flooding topology. > > > > Best Regards, > > Huaimo > > > > thanks, > > Peter > > > > > >> > >> > >> > >> Best Regards, > >> > >> Huaimo > >> > >> *From:* Acee Lindem (acee) [mailto:acee@cisco.com] > >> *Sent:* Sunday, February 3, 2019 11:45 AM > >> *To:* Huaimo Chen <huaimo.chen@huawei.com>; Christian Hopps > >> <chopps@chopps.org>; lsr@ietf.org > >> *Subject:* Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft > >> Redux] > >> > >> > >> > >> Hi Huaimo, > >> > >> > >> > >> See inline. > >> > >> > >> > >> *From: *Lsr <lsr-bounces@ietf.org <mailto:lsr-bounces@ietf.org>> on > >> behalf of Huaimo Chen <huaimo.chen@huawei.com > >> <mailto:huaimo.chen@huawei.com>> > >> *Date: *Saturday, February 2, 2019 at 12:27 AM > >> *To: *Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>>, > >> "lsr@ietf.org <mailto:lsr@ietf.org>" <lsr@ietf.org > >> <mailto:lsr@ietf.org>> > >> *Subject: *Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft > >> Redux] > >> > >> > >> > >> Hi Everyone, > >> > >> > >> > >> We proposed the distributed solution first, and Tony proposed the > >> centralized solution first. Tony added the distributed solution > >> (except for the algorithms to compute flooding topology) into his > >> draft. And then we added the centralized solution into our draft. The > >> latest versions of the two drafts have largely converged at least at > >> the high level to a solution for solving the same problem. > >> > >> > >> > >> Our draft has multiple key technical advantages over Tony's draft as > >> we described in our email to the LSR list, which are summarized below: > >> > >> 1. It uses a fraction of flooding resource (i.e., it is multiple > >> times more efficient in flooding topology encoding); > >> > >> 2. It provides fault tolerance to multiple failures, minimizing > >> impact on network convergence, thus minimizing traffic lose; and > >> > >> 3. It is simpler and needs less processing time (i.e., faster and > >> more efficient) in multiple scenarios. > >> > >> Based on the technical merits, our draft should be moved forward. > >> However, Chair proposed to move Tony's draft forward and have us work > >> on a distributed algorithm as we started with. > >> > >> > >> > >> I think that the distributed solution in Tony's draft needs to be > >> removed and they work on the centralized solution. We remove the > >> centralized solution from our draft and work on the distributed solution. > >> > >> > >> > >> I'm against "cutting the baby in half" given that the signaling for > >> the distributed solution is a proper subset of what is required for > >> the centralized solution. It is undesirable to have different > >> signaling for the two modes. For the distributed algorithm you are > >> proposing, do see problems with the signaling? > >> > >> > >> > >> Thanks, > >> > >> Acee > >> > >> > >> > >> Best Regards, > >> > >> Huaimo > >> > >> > >> > >> -----Original Message----- > >> > >> From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Christian Hopps > >> > >> Sent: Friday, February 1, 2019 7:26 AM > >> > >> To: lsr@ietf.org <mailto:lsr@ietf.org> > >> > >> Cc: chopps@chopps.org <mailto: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 <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://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_ > >> watch-3Fv-3DqHmT4ytMn4w-26list-3DPLC86T-2D6ZTP5j- > 5FHaBNdfP&d=DwICAg&c > >> =HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT- > h5LGhEW > >> H- > s_xXXup3HzvBSMRj5VE&m=kykK2jUejhafPHOrWXu0yvNk7XsXUoDYsWjFoFGHeT > g&s > >> =cBWxI4Hu1GZNWxuUZRREnZNg-cZZYbdrLHRXKsUama4&e= > >> bgxGIp22cnaWS > >> > >>> - Minutes: > >> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf > >> .org_meeting_101_materials_minutes-2D101-2Dlsr- > 2D00&d=DwICAg&c=HAkYuh > >> 63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH- > s_xXX > >> > up3HzvBSMRj5VE&m=kykK2jUejhafPHOrWXu0yvNk7XsXUoDYsWjFoFGHeTg&s= > 1UTDcj > >> zO1b-Ful7k87ItzHcvqzRveIK_m_FI9eIDLFs&e= > >> > >>> - 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mai > >> lman_listinfo_lsr&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK- > ndb3voDTXcWz > >> oCI&r=CRB2tJiQePk0cT-h5LGhEWH- > s_xXXup3HzvBSMRj5VE&m=kykK2jUejhafPHOrW > >> > Xu0yvNk7XsXUoDYsWjFoFGHeTg&s=BTZ1l1KpTxr_U3n0pZnknvuPBGxRM9ul08q > CKpaE > >> eXk&e= > >> > > > > . > > > > _______________________________________________ > Lsr mailing list > Lsr@ietf.org > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__www.ietf.org_mailman_listinfo_lsr&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0 > UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH- > s_xXXup3HzvBSMRj5VE&m=kykK2jUejhafPHOrWXu0yvNk7XsXUoDYsWjFoFGHeT > g&s=BTZ1l1KpTxr_U3n0pZnknvuPBGxRM9ul08qCKpaEeXk&e=
- [Lsr] Flooding Reduction Draft Redux Christian Hopps
- [Lsr] Moving Forward [Re: Flooding Reduction Draf… Christian Hopps
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … John E Drake
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Tony Li
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … David Allan I
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Peter Psenak
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Les Ginsberg (ginsberg)
- Re: [Lsr] Flooding Reduction Draft Redux Huaimo Chen
- Re: [Lsr] Flooding Reduction Draft Redux Christian Hopps
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Naiming Shen (naiming)
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Jeff Tantsura
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Huaimo Chen
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Aijun Wang
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Robert Raszuk
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … li zhenqiang
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Abdussalam Baryun
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … David Allan I
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Acee Lindem (acee)
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Huaimo Chen
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Huaimo Chen
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Robert Raszuk
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … tony.li
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Robert Raszuk
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Les Ginsberg (ginsberg)
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … David Allan I
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Les Ginsberg (ginsberg)
- [Lsr] 答复: Moving Forward [Re: Flooding Reduction … Lizhenbin
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Christian Hopps
- Re: [Lsr] 答复: Moving Forward [Re: Flooding Reduct… Christian Hopps
- Re: [Lsr] 答复: Moving Forward [Re: Flooding Reduct… Linda Dunbar
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Acee Lindem (acee)
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Peter Psenak
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Peter Psenak
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Robert Raszuk
- Re: [Lsr] 答复: Moving Forward [Re: Flooding Reduct… Dongjie (Jimmy)
- Re: [Lsr] 答复: Moving Forward [Re: Flooding Reduct… Huzhibo
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Huaimo Chen
- [Lsr] 回复: Re: 答复: Moving Forward [Re: Flooding Re… li zhenqiang
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Peter Psenak
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … John E Drake
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Acee Lindem (acee)
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Acee Lindem (acee)
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Huaimo Chen
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Peter Psenak
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Huaimo Chen
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Tony Li
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Huaimo Chen
- Re: [Lsr] Moving Forward [Re: Flooding Reduction … Les Ginsberg (ginsberg)