Re: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
Christian Hopps <chopps@chopps.org> Mon, 11 February 2019 18:15 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 DD18E130E9D; Mon, 11 Feb 2019 10:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 PbXrZHa1jriX; Mon, 11 Feb 2019 10:15:29 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id DEA6F1271FF; Mon, 11 Feb 2019 10:15:28 -0800 (PST)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 1EBEA60427; Mon, 11 Feb 2019 13:15:27 -0500 (EST)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <0FFC492B-14BC-464A-BEB3-D04FB74DAF03@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_4DE1D93A-181C-411D-84D2-5D61C90D3DE0"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 11 Feb 2019 13:15:26 -0500
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F540587@DGGEMM532-MBX.china.huawei.com>
Cc: 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>
To: Lizhenbin <lizhenbin@huawei.com>
References: <sa6lg2md2ok.fsf@chopps.org> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F540587@DGGEMM532-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/NjFost_DTgDAPVqYLgIRI00f7O8>
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: Mon, 11 Feb 2019 18:15:31 -0000
> On Feb 11, 2019, at 10:19 AM, Lizhenbin <lizhenbin@huawei.com> wrote: > > Hi Chris, > 1. I have doubt about "The aim of this document is to describe the problem space and standardize a way to signal dynamic flooding information.". Does the aim mean the draft describes the problem space and standardize the way for the centralized solution or mean the draft will standardize the way used for both the centralized solutions and the distributed solutions? It does not standardize any algorithms. For a centralized algorithm (unspecified) use one has to distribute the flooding topology it does specify this. It also supplies the means to signal what distributed algorithm is in use (a value). > 2. I explained in the previous mail the distributed solution includes more than the algorithms defined in the draft-cc-lsr-flooding-reduction-00 and the overlapped signallings defined in the draft-cc-lsr-flooding-reduction-00/draft-li-dynamic-flooding-03. For example, it may define the standardized procedures for the distributed solutions. If there is such part, is it defined by draft-li-lsr-dynamic-flooding-02 or draft-cc-lsr-flooding-reduction? How a distributed algorithm decides to implement itself is up to that algorithm. This is not part of the signaled information. Again, the only thing that I am aware of in draft-li-dynamic-flooding in regards to distributed algorithms is what's required for us to use them as they get defined in the future, i.e., a way to signal which one is in use. Thanks, Chris. > > I hope you could clarify the above issues firstly for the adoption. > > > Thanks & Regards, > Zhenbin (Robin) > > > > > ________________________________________ > 发件人: Lsr [lsr-bounces@ietf.org] 代表 Christian Hopps [chopps@chopps.org] > 发送时间: 2019年2月11日 18:44 > 收件人: lsr@ietf.org > 抄送: lsr-chairs@ietf.org; lsr-ads@ietf.org; chopps@chopps.org > 主题: [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] WG Adoption Call for draft-li-lsr-dynamic-f… Christian Hopps
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Acee Lindem (acee)
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… tony.li
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Robert Raszuk
- [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynam… Lizhenbin
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Edward
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Christian Hopps
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… David Allan I
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… steve ulrich
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Peter Psenak
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Naiming Shen (naiming)
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Les Ginsberg (ginsberg)
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Jeff Tantsura
- [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynam… Aijun Wang
- Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-d… Lizhenbin
- Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-d… Guyunan (Yunan Gu, IP Technology Research Dept. NW)
- Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-d… Huzhibo
- [Lsr] 答复: 答复: WG Adoption Call for draft-li-lsr-d… Dongjie (Jimmy)
- Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-d… Yangang
- Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-d… Christian Hopps
- Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-d… John E Drake
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… LEI LIU
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Mankamana Mishra (mankamis)
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Ketan Talaulikar (ketant)
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… sridhar santhanam
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Huaimo Chen
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Peter Psenak
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Christian Hopps
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Sri
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Tony Li
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Christian Hopps
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Huaimo Chen
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Tony Li
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Huaimo Chen
- Re: [Lsr] WG Adoption Call for draft-li-lsr-dynam… Christian Hopps
- [Lsr] Multiple failures in Dynamic Flooding tony.li
- Re: [Lsr] Multiple failures in Dynamic Flooding Les Ginsberg (ginsberg)
- Re: [Lsr] Multiple failures in Dynamic Flooding Huaimo Chen
- Re: [Lsr] Multiple failures in Dynamic Flooding Peter Psenak
- Re: [Lsr] Multiple failures in Dynamic Flooding tony.li