[Idr] 答复: draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt - IPR Call and WG LC (7/14 to 7/28)

Lizhenbin <lizhenbin@huawei.com> Wed, 15 July 2020 02:23 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A0CAD3A0D01 for <idr@ietfa.amsl.com>; Tue, 14 Jul 2020 19:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id WpUikC5dHNvu for <idr@ietfa.amsl.com>; Tue, 14 Jul 2020 19:23:10 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (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 182483A0CFF for <idr@ietf.org>; Tue, 14 Jul 2020 19:23:10 -0700 (PDT)
Received: from lhreml745-chm.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id BC925BEE7A36C8D87213 for <idr@ietf.org>; Wed, 15 Jul 2020 03:23:07 +0100 (IST)
Received: from lhreml741-chm.china.huawei.com ( by lhreml745-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 15 Jul 2020 03:23:07 +0100
Received: from DGGEMM403-HUB.china.huawei.com ( by lhreml741-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Wed, 15 Jul 2020 03:23:07 +0100
Received: from DGGEMM532-MBX.china.huawei.com ([]) by DGGEMM403-HUB.china.huawei.com ([]) with mapi id 14.03.0487.000; Wed, 15 Jul 2020 10:23:00 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Susan Hares <shares@ndzh.com>, "'idr@ietf. org'" <idr@ietf.org>
Thread-Topic: [Idr] draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt - IPR Call and WG LC (7/14 to 7/28)
Thread-Index: AdZaFUDb991Sb6pqTfy2fVLIPFF/hAAOXXOJ
Date: Wed, 15 Jul 2020 02:23:00 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D937DA5C2@DGGEMM532-MBX.china.huawei.com>
References: <01a001d65a15$f6cb25d0$e4617170$@ndzh.com>
In-Reply-To: <01a001d65a15$f6cb25d0$e4617170$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D937DA5C2DGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/R0T3U5AT5nG8BhOGotvEBwZosfQ>
Subject: [Idr] =?gb2312?b?tPC4tDogIGRyYWZ0LWlldGYtaWRyLWJncC1scy1zYmZk?= =?gb2312?b?LWV4dGVuc2lvbnMtMDIudHh0IC0gSVBSIENhbGwgYW5kIFdHIExDICg3LzE0?= =?gb2312?b?IHRvIDcvMjgp?=
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2020 02:23:15 -0000

I support the WG LC as the co-author.

Best Regards,

Zhenbin (Robin)

发件人: Idr [idr-bounces@ietf.org] 代表 Susan Hares [shares@ndzh.com]
发送时间: 2020年7月15日 3:35
收件人: 'idr@ietf. org'
主题: [Idr] draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt - IPR Call and WG LC (7/14 to 7/28)

This begins a 2 week WG LC for draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt

You can find the draft at:

You can find the implementations reports at:

This is a rather short draft (real text about 5 pages).

Therefore, we are going to combine WG LC and IPR together.

This draft has only one implementation from Nokia.

In your comments please consider:

1) Do you feel this draft is ready for publication?

2) Should we wait for 2 implementations or publish

(as the authors request) with 1 implementations?

3) Are there any other implementations we do not know of?

(open source or vendor implementations)

4) Do you know of any deployments of this technology with

the Nokia implementation or another implementation?

Has this feature been useful?

Also, please mention support/no support in your reply.

Cheerily, Sue

(co-chair and shepherd for draft).