[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 07:07 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 B261C3A07E5 for <idr@ietfa.amsl.com>; Wed, 15 Jul 2020 00:07: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 3MX9V0bd6zBg for <idr@ietfa.amsl.com>; Wed, 15 Jul 2020 00:07:13 -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 544433A07E7 for <idr@ietf.org>; Wed, 15 Jul 2020 00:07:13 -0700 (PDT)
Received: from lhreml722-chm.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 4C6D759E0DD76108C3AE for <idr@ietf.org>; Wed, 15 Jul 2020 08:07:11 +0100 (IST)
Received: from lhreml722-chm.china.huawei.com ( by lhreml722-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 08:07:11 +0100
Received: from DGGEMM405-HUB.china.huawei.com ( by lhreml722-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 08:07:10 +0100
Received: from DGGEMM532-MBX.china.huawei.com ([]) by DGGEMM405-HUB.china.huawei.com ([]) with mapi id 14.03.0487.000; Wed, 15 Jul 2020 15:07:06 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "idr@ietf. org" <idr@ietf.org>, Susan Hares <shares@ndzh.com>
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/hP//udUAgAEITp4=
Date: Wed, 15 Jul 2020 07:07:05 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D937DBE26@DGGEMM532-MBX.china.huawei.com>
References: <01a001d65a15$f6cb25d0$e4617170$@ndzh.com>, <9060d515-ad96-4a51-80e5-1e70a4565b94@Spark>
In-Reply-To: <9060d515-ad96-4a51-80e5-1e70a4565b94@Spark>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D937DBE26DGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3s9p_INgeJB8mTn7-8UmiWXQx1Y>
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 07:07:15 -0000

Hi All,

I support the WG LC of the draft as the co-author.  I am not aware of any IPR related with the draft.

Best Regards,

Zhenbin (Robin)

On Jul 14, 2020, 12:36 PM -0700, Susan Hares <shares@ndzh.com>om>, wrote:
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).

Idr mailing list