Re: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

Christian Hopps <chopps@chopps.org> Sun, 24 February 2019 23:14 UTC

Return-Path: <chopps@chopps.org>
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 BDA0212D84D; Sun, 24 Feb 2019 15:14:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 CPir3LGv0xm8; Sun, 24 Feb 2019 15:14:14 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id AB30D12D84C; Sun, 24 Feb 2019 15:14:14 -0800 (PST)
Received: from tops.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPS id C120E604D2; Sun, 24 Feb 2019 18:14:13 -0500 (EST)
References: <sa6lg2md2ok.fsf@chopps.org> <SN6PR11MB284553735B2351FB584BE792C17F0@SN6PR11MB2845.namprd11.prod.outlook.com> <5316A0AB3C851246A7CA5758973207D463B5858A@sjceml521-mbx.china.huawei.com> <420ed1b5-d849-99cc-bcb0-d159783e4de2@cisco.com>
User-agent: mu4e 1.1.0; emacs 26.1
From: Christian Hopps <chopps@chopps.org>
To: Peter Psenak <ppsenak@cisco.com>
Cc: Huaimo Chen <huaimo.chen@huawei.com>, Christian Hopps <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>
In-reply-to: <420ed1b5-d849-99cc-bcb0-d159783e4de2@cisco.com>
Date: Sun, 24 Feb 2019 18:14:12 -0500
Message-ID: <sa6pnrglqyj.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/KntQTDat97lr5MNiuGdK-hRdypE>
Subject: Re: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
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, 24 Feb 2019 23:14:17 -0000

Peter Psenak <ppsenak@cisco.com> writes:

> Huaimo,
>
> On 24/02/2019 06:34 , Huaimo Chen wrote:
>>
>> In addition, for signaling the distributed solution/mode or the
>> centralized solution/mode, a user/operator needs to configure or select
>> a solution/mode on a node via CLI or other approach first. Which node
>> should the user/operator use to configure/select a mode?  If the
>> user/operator can only use the leader node in the area to configure,
>> then it is neither convenient nor reasonable. The leader node in the
>> area is dynamically generated. But in the distributed mode/solution,
>> there is no leader selection (i.e., no leader should be generated).
>
> there is an area leader in both modes. In distributed mode the area leader is
> the one that advertises the algorithm that is used by all nodes that
> participates in dynamic flooding.

I'd like to suggest that as this point is discussed we are careful to not try and replace the standard configuration mechanisms.

Thanks,
Chris.

> regards,
> Peter
>
>>
>>
>>
>> draft-cc-lsr-flooding-reduction-01 contains solutions for some of the
>> above issues, which should be merged based on technical merits.
>>
>>
>>
>> Best Regards,
>>
>> Huaimo
>>
>>
>>
>> -----Original Message-----
>>
>> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Christian Hopps
>>
>> Sent: 11 February 2019 16:15
>>
>> To: lsr@ietf.org
>>
>> Cc: lsr-chairs@ietf.org; lsr-ads@ietf.org; chopps@chopps.org
>>
>> Subject: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 +
>> IPR poll.
>>
>>
>>
>>
>>
>> Hi Folks,
>>
>>
>>
>> We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.
>>
>>
>>
>> The aim of this document is to describe the problem space and
>> standardize a way to signal dynamic flooding information. It does not
>> standardize any specific algorithm for flooding topology creation.
>>
>>
>>
>> Authors please respond indicating if you are aware of any IPR related to
>> this work.
>>
>>
>>
>> We also have another draft (draft-cc-lsr-flooding-reduction-01) that
>> started as a distributed flooding topology algorithm and morphed into
>> that plus competing ideas on signaling of flooding topology information.
>> The intent after adoption of draft-li-lsr-dynamic-flooding-02 is
>> two-fold. One, the WG can discuss adding any signaling ideas from this
>> work to the adopted signaling draft (with proper attribution given as
>> appropriate), and two, for the authors of
>> draft-cc-lsr-flooding-reduction-01 to publish a new document without the
>> signaling portion and instead focus on their flooding topology
>> algorithm. This new focused document can be considered in parallel along
>> with the other algorithm work that has been proposed.
>>
>>
>>
>> Flooding topology creation is seen as a hard problem for which we don't
>> expect a one-size-fits-all solution. Taking the steps outlined above
>> will help us move forward on the solutions.
>>
>>
>>
>> Thanks,
>>
>> Chris & Acee.
>>
>> LSR WG Chairs.
>>
>>
>>
>> _______________________________________________
>>
>> Lsr mailing list
>>
>> Lsr@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/lsr
>>
>>
>>
>> _______________________________________________
>> Lsr mailing list
>> Lsr@ietf.org
>> https://www.ietf.org/mailman/listinfo/lsr
>>