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

Tony Li <tony1athome@gmail.com> Fri, 01 February 2019 15:46 UTC

Return-Path: <tony1athome@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 2DA64130E2F for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 07:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 FOSlZVRRTEme for <lsr@ietfa.amsl.com>; Fri, 1 Feb 2019 07:46:15 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 35388130E00 for <lsr@ietf.org>; Fri, 1 Feb 2019 07:46:15 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id b7so3384987pfi.8 for <lsr@ietf.org>; Fri, 01 Feb 2019 07:46:15 -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=+WhepeM7OfxSS+leZhepDccdY7xTfHuTK3aU1DF995k=; b=G9xt/pqQqxwnqPMcqYI5hzhCX7A8aYHcW2QNkpgG8AWZU9/VHX0C8W8eFyiSaMz6lM MF1Ke6HfPFc+NXguT6R80fVYy5X28HYz/YdPk6SXxJayFZWcQs0WQOB6e+JBJ1H277aU hIBo20JDLXJ5q6QPHO85ctoNhtxh7AMuBfp3K/N3lrckbD8YmCSjQ9oCUI0ekRbESM6H +d5Sw/LAkftYrV3v+SqDA1TI5Yc6b+hIfnPvCVi8PkchhZXyBWvT72mDwGMceN5/cQ8V lbFHoU8ultQ2Vf10JKN2xg/DOey4AJKtc70kYQc5r0tinFCiDNFhNVQbpvG6/vVz/+WW JnbA==
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=+WhepeM7OfxSS+leZhepDccdY7xTfHuTK3aU1DF995k=; b=AyNSJcjEMnwYoR/SUfXQnPxE8X8wXQZ+CYuut2XAdN2Y4VeVaZ7Q7KKC7y6h72Up+Y V0V8BBuI7eqR7jhMwhxbhhsE6vMjCQSMluUnXtpgQ1VcIUhHkeQoo7c6lgo5Gfe1lMvs s80Ve7mRA6i1tImDUlJ7xv/DY/tNW6rEbV6etEW49+lSISYfP7KZv5NvSmoKev6ppD96 FqaHmyJOcCHNebXAx5mNGSxAASLS/UhJmhMIRfNKJRKbhjkDtFEmSnYXnCkdtMLwLAPo +XcOtri0B0WYETwm8FxTJEtDA6T77wqq+0LzGf/0DI9mmjzMGEs5CVl9u52YP5o5I8lw 7uvA==
X-Gm-Message-State: AJcUukfqoOMKbhg4lf2PJDXM72mSCCJD638zOr12dxNFBFk+6+EVoDzZ CzDFqj06p+Kh3T564I+NNFM=
X-Google-Smtp-Source: ALg8bN7iuUq8udRzn+vdMURLAqD8m/bw2k+ipAUYQODyMOdtDFVuWC3q63W3s40Co2k/L4TjL9/TUQ==
X-Received: by 2002:a62:fb07:: with SMTP id x7mr39584762pfm.71.1549035974622; Fri, 01 Feb 2019 07:46:14 -0800 (PST)
Received: from [192.168.1.8] (c-73-158-115-137.hsd1.ca.comcast.net. [73.158.115.137]) by smtp.gmail.com with ESMTPSA id g87sm5419712pfe.43.2019.02.01.07.46.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Feb 2019 07:46:14 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Tony Li <tony1athome@gmail.com>
In-Reply-To: <BYAPR05MB502910AA32E9BDB958AA8B3BC7920@BYAPR05MB5029.namprd05.prod.outlook.com>
Date: Fri, 1 Feb 2019 07:46:12 -0800
Cc: Christian Hopps <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CD5C590-5AD0-4B99-8081-7FC1310172A8@gmail.com>
References: <sa65zu31zqk.fsf@chopps.org> <sa64l9n1yqy.fsf@chopps.org> <BYAPR05MB502910AA32E9BDB958AA8B3BC7920@BYAPR05MB5029.namprd05.prod.outlook.com>
To: John E Drake <jdrake@juniper.net>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/MSrOOEdI3zFx_wUtb4SGU7EYMxI>
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:46:18 -0000

+1

Tony


> On Feb 1, 2019, at 5:18 AM, John E Drake <jdrake@juniper.net>; wrote:
> 
> Chris & Acee,
> 
> This looks fine to me.
> 
> Yours Irrespectively,
> 
> John
> 
>> -----Original Message-----
>> From: Lsr <lsr-bounces@ietf.org>; On Behalf Of Christian Hopps
>> Sent: Friday, February 1, 2019 7: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