IETF Logo Mail Archive

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

"Wangyali(Yali,Data Communication Standards and Patents Dept)" <wangyali11@huawei.com> Tue, 24 August 2021 10:23 UTC

Return-Path: <wangyali11@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 A44E53A1F7B; Tue, 24 Aug 2021 03:23:44 -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 mKizzWuR_PhU; Tue, 24 Aug 2021 03:23: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 898933A1F72; Tue, 24 Aug 2021 03:23:39 -0700 (PDT)
Received: from fraeml743-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Gv4t31lPgz67ZHk; Tue, 24 Aug 2021 18:22:19 +0800 (CST)
Received: from dggpeml500023.china.huawei.com (7.185.36.114) by fraeml743-chm.china.huawei.com (10.206.15.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Tue, 24 Aug 2021 12:23:35 +0200
Received: from dggpeml500024.china.huawei.com (7.185.36.10) by dggpeml500023.china.huawei.com (7.185.36.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Tue, 24 Aug 2021 18:23:33 +0800
Received: from dggpeml500024.china.huawei.com ([7.185.36.10]) by dggpeml500024.china.huawei.com ([7.185.36.10]) with mapi id 15.01.2176.012; Tue, 24 Aug 2021 18:23:33 +0800
From: "Wangyali(Yali,Data Communication Standards and Patents Dept)" <wangyali11@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/C0DGrlTPWyZq9XeRllcQY70m+Q
Date: Tue, 24 Aug 2021 10:23:33 +0000
Message-ID: <4c0a78b49f72401bb3ac08e74a4f2c3b@huawei.com>
References: <022201d77fe3$eb9ba9b0$c2d2fd10$@ndzh.com>
In-Reply-To: <022201d77fe3$eb9ba9b0$c2d2fd10$@ndzh.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.136]
Content-Type: multipart/alternative; boundary="_000_4c0a78b49f72401bb3ac08e74a4f2c3bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/YASDggZJVRm6N1VOn4j7x9xslAc>
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: Tue, 24 Aug 2021 10:23:45 -0000

Hi WG,

I support the adoption of this draft.

Thanks,
Yali

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

v2.23.0 | Report a Bug | By Email