[Idr] 答复: WG adoption call - draft-li-idr-flowspec-srv6-05,txt

"Lilei (Lily)" <lily.lilei@huawei.com> Thu, 05 August 2021 07:27 UTC

Return-Path: <lily.lilei@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6C3C3A1357; Thu, 5 Aug 2021 00:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 f5pn8DqD-3CO; Thu, 5 Aug 2021 00:27:39 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 275933A1356; Thu, 5 Aug 2021 00:27:39 -0700 (PDT)
Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GgKtw422Hz6GBng; Thu, 5 Aug 2021 15:27:20 +0800 (CST)
Received: from dggeme756-chm.china.huawei.com (10.3.19.102) by fraeml707-chm.china.huawei.com (10.206.15.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Thu, 5 Aug 2021 09:27:36 +0200
Received: from dggeme756-chm.china.huawei.com (10.3.19.102) by dggeme756-chm.china.huawei.com (10.3.19.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Thu, 5 Aug 2021 15:27:34 +0800
Received: from dggeme756-chm.china.huawei.com ([10.6.80.68]) by dggeme756-chm.china.huawei.com ([10.6.80.68]) with mapi id 15.01.2176.012; Thu, 5 Aug 2021 15:27:34 +0800
From: "Lilei (Lily)" <lily.lilei@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>, "draft-li-idr-flowspec-srv6@ietf.org" <draft-li-idr-flowspec-srv6@ietf.org>
Thread-Topic: [Idr] WG adoption call - draft-li-idr-flowspec-srv6-05,txt
Thread-Index: Add/4sY1y/C0DGrlTPWyZq9XeRllcQJ6BLWQ
Date: Thu, 5 Aug 2021 07:27:34 +0000
Message-ID: <f82e3c3b917f4f5889357084b059b717@huawei.com>
References: <022201d77fe3$eb9ba9b0$c2d2fd10$@ndzh.com>
In-Reply-To: <022201d77fe3$eb9ba9b0$c2d2fd10$@ndzh.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.141]
Content-Type: multipart/alternative; boundary="_000_f82e3c3b917f4f5889357084b059b717huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/s5B4-BZ6XPce66wLMK343F0ecRM>
Subject: [Idr] =?gb2312?b?tPC4tDogIFdHIGFkb3B0aW9uIGNhbGwgIC0gICBkcmFm?= =?gb2312?b?dC1saS1pZHItZmxvd3NwZWMtc3J2Ni0wNSx0eHQ=?=
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: Thu, 05 Aug 2021 07:27:44 -0000

Support adoption and I'm not aware of any IPR that applies to the draft


Best Regards,
Lei Li

发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares
发送时间: 2021年7月24日 0:58
收件人: idr@ietf.org; draft-li-idr-flowspec-srv6@ietf.org
主题: [Idr] WG adoption call - draft-li-idr-flowspec-srv6-05,txt

This begins a 2 week WG adoption call for draft-li-idr-flowspec-srv6-05.txt.

I am missing 3 IPR statements (Zhenbin Li , Lei Li , and Lei Liu).
These authors should send in their IPR statements in response to this call.

This draft is targeted for the V2 version of flow specification.
Flow specification v2 draft will be discussed at an interim on 9/13/2021.

If it is adopted, it will be developed as part of the v2 set of drafts.

Please consider if:

1) if this draft is useful for networks,
2) if you wish to adopt this draft prior to adopting flow specification v2.

Cheerily, Susan Hares