[Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
Lizhenbin <lizhenbin@huawei.com> Mon, 11 February 2019 15:20 UTC
Return-Path: <lizhenbin@huawei.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 80EA51271FF; Mon, 11 Feb 2019 07:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 3yT2ame7LGcp; Mon, 11 Feb 2019 07:20:32 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 E5C8A126F72; Mon, 11 Feb 2019 07:20:31 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 1C79E82A8CD0416C62EF; Mon, 11 Feb 2019 15:20:30 +0000 (GMT)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 11 Feb 2019 15:20:29 +0000
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 11 Feb 2019 15:20:29 +0000
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Mon, 11 Feb 2019 15:20:29 +0000
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.46]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0415.000; Mon, 11 Feb 2019 23:19:55 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Christian Hopps <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
CC: "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>
Thread-Topic: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
Thread-Index: AQHUwfc8NHUXH6LnbEahUQVnq9r5R6XasnA3
Date: Mon, 11 Feb 2019 15:19:54 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F540587@DGGEMM532-MBX.china.huawei.com>
References: <sa6lg2md2ok.fsf@chopps.org>
In-Reply-To: <sa6lg2md2ok.fsf@chopps.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.160.57]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/eRahjYUxpRGn4NYlqyINYQBN8Rc>
Subject: [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 15:20:34 -0000
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? 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? 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