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

"Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com> Thu, 14 February 2019 06:33 UTC

Return-Path: <guyunan@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 46C6F128B14; Wed, 13 Feb 2019 22:33:26 -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 7MUA3AZ0-p3r; Wed, 13 Feb 2019 22:33:24 -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 6E136128766; Wed, 13 Feb 2019 22:33:24 -0800 (PST)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 99069D4E1C3ED9A75FFD; Thu, 14 Feb 2019 06:33:22 +0000 (GMT)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 14 Feb 2019 06:33:22 +0000
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.249]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0415.000; Thu, 14 Feb 2019 14:33:14 +0800
From: "Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, '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: AQHUxA5W/ku9n4BG9E20pv5+ZZhAWKXe1Z5Q
Date: Thu, 14 Feb 2019 06:33:14 +0000
Message-ID: <C01B0098369B2D4391851938DA6700B713465882@DGGEML532-MBX.china.huawei.com>
References: <sa6lg2md2ok.fsf@chopps.org> <008d01d4c40e$3e66d5a0$bb3480e0$@org.cn>
In-Reply-To: <008d01d4c40e$3e66d5a0$bb3480e0$@org.cn>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.184.132]
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/TDknAlZKyNgG4tki1MqeO28b7YU>
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: Thu, 14 Feb 2019 06:33:26 -0000

Supports for the adoption of two drafts at the same time +1


BR,

Yunan


-----Original Message-----
From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Aijun Wang
Sent: Thursday, February 14, 2019 10:38 AM
To: 'Christian Hopps' <chopps@chopps.org>; lsr@ietf.org
Cc: lsr-chairs@ietf.org; lsr-ads@ietf.org
Subject: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

Hi, Christian:

Supports for the adoption of two drafts at the same time, in which
one(draft-li-lsr-dynamic-flooding-02) focuses on the centralized mode and the other(draft-cc-lsr-flooding-reduction-01) focuses on the distributed mode.

The centralized mode for is one straightforward way to realize the flooding reduction, and I admire Tony Li give his solution first. But from the consideration of solution robustness, the distributed mode may be more promising.
My consideration for distributed mode is that it should not cover only the algorithm, more contents need to be standardized in future. Huaimo has one good start point for distributed mode, and he also gives abundant thoughts for the centralized mode that the current version of
draft-li-lsr-dynamic-flooding-02 has not covered yet.

Proposal for the name of two drafts may be draft-ietf-lsr-flooding-reduction-centralized-mode and draft-ietf-lsr-flooding-reduction-distributed-mode.


Best Regards.

Aijun Wang
Network R&D and Operation Support Department China Telecom Corporation Limited Beijing Research Institute,Beijing, China.

-----邮件原件-----
发件人: Christian Hopps [mailto:chopps@chopps.org]
发送时间: 2019年2月11日 18:45
收件人: 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 mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr