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

"Yangfan (IP Standard)" <shirley.yangfan@huawei.com> Mon, 23 August 2021 11:02 UTC

Return-Path: <shirley.yangfan@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 4C85A3A08CC; Mon, 23 Aug 2021 04:02:23 -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 s2CB0UPIj8_K; Mon, 23 Aug 2021 04:02:17 -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 890873A08C6; Mon, 23 Aug 2021 04:02:17 -0700 (PDT)
Received: from fraeml706-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GtTn81Ldpz67bjw; Mon, 23 Aug 2021 19:01:00 +0800 (CST)
Received: from kwepeml500003.china.huawei.com (7.221.188.182) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Mon, 23 Aug 2021 13:02:13 +0200
Received: from kwepeml500003.china.huawei.com (7.221.188.182) by kwepeml500003.china.huawei.com (7.221.188.182) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Mon, 23 Aug 2021 19:02:11 +0800
Received: from kwepeml500003.china.huawei.com ([7.221.188.182]) by kwepeml500003.china.huawei.com ([7.221.188.182]) with mapi id 15.01.2308.008; Mon, 23 Aug 2021 19:02:11 +0800
From: "Yangfan (IP Standard)" <shirley.yangfan@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/C0DGrlTPWyZq9XeRllcQYCtHiA
Date: Mon, 23 Aug 2021 11:02:11 +0000
Message-ID: <8da06387f3af47129be63bfcb0e6542a@huawei.com>
References: <022201d77fe3$eb9ba9b0$c2d2fd10$@ndzh.com>
In-Reply-To: <022201d77fe3$eb9ba9b0$c2d2fd10$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.115]
Content-Type: multipart/alternative; boundary="_000_8da06387f3af47129be63bfcb0e6542ahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/IIruj5IgnfRci8fhhVED5E2KWP0>
Subject: Re: [Idr] WG adoption call - draft-li-idr-flowspec-srv6-05,txt
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: Mon, 23 Aug 2021 11:02:24 -0000

Hi IDR,

This draft is useful and important to develop BGP Flow Spec V2, so I support the adoption of this draft. Thanks.

Best,
Fan


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Saturday, July 24, 2021 12:58 AM
To: idr@ietf.org; draft-li-idr-flowspec-srv6@ietf.org
Subject: [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