[Idr] Forwarded on behalf of co-author Weiguo//FW: WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology only (2/4/2020 to 2/18/2020).
Liyizhou <liyizhou@huawei.com> Thu, 18 February 2021 11:06 UTC
Return-Path: <liyizhou@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 29AE03A105D for <idr@ietfa.amsl.com>; Thu, 18 Feb 2021 03:06:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 PZPoPa7QNsjB for <idr@ietfa.amsl.com>; Thu, 18 Feb 2021 03:05:59 -0800 (PST)
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 275B93A105C for <idr@ietf.Org>; Thu, 18 Feb 2021 03:05:59 -0800 (PST)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DhBXV59j1z67q3q for <idr@ietf.Org>; Thu, 18 Feb 2021 18:58:50 +0800 (CST)
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 18 Feb 2021 12:05:50 +0100
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by nkgeml705-chm.china.huawei.com (10.98.57.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 18 Feb 2021 19:05:47 +0800
Received: from nkgeml707-chm.china.huawei.com ([10.98.57.157]) by nkgeml707-chm.china.huawei.com ([10.98.57.157]) with mapi id 15.01.2106.006; Thu, 18 Feb 2021 19:05:47 +0800
From: Liyizhou <liyizhou@huawei.com>
To: "idr@ietf.Org" <idr@ietf.Org>
Thread-Topic: Forwarded on behalf of co-author Weiguo//FW: [Idr] WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology only (2/4/2020 to 2/18/2020).
Thread-Index: AdcF5cWpgTZoF7BpS9uzNM8rFugsJA==
Date: Thu, 18 Feb 2021 11:05:47 +0000
Message-ID: <c6577376c7b8470383c464e5d1a7fea4@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.98.176]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0OweAvqX8mm3au0OND9YMHq6sGI>
Subject: [Idr] Forwarded on behalf of co-author Weiguo//FW: WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology only (2/4/2020 to 2/18/2020).
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, 18 Feb 2021 11:06:01 -0000
Hi all, Please see the forwarded message. Yizhou -----Original Message----- From: Haoweiguo Sent: Thursday, February 18, 2021 12:06 PM To: Liyizhou <liyizhou@huawei.com> Subject: 答复: [Idr] WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology only (2/4/2020 to 2/18/2020). Hi Yizhou, Due to my limited email privilege, would you please to forward my following response to the IDR WG? Thanks, Weiguo Dear All, I agree with Donald’s answer for the 4 questions listed below. I also think the new Geneve protocol(RFC 8926) could conveniently be extended in a new version of this draft. As a co-author, I support progressing this draft to its publication as Standard RFC. Thanks, Weiguo -----邮件原件----- 发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Donald Eastlake 发送时间: 2021年2月13日 4:07 收件人: Greg Mirsky <gregimirsky@gmail.com> 抄送: idr wg <idr@ietf.org>; Susan Hares <shares@ndzh.com> 主题: Re: [Idr] WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology only (2/4/2020 to 2/18/2020). On Fri, Feb 12, 2021 at 2:35 PM Greg Mirsky <gregimirsky@gmail.com> wrote: > Dear All, > I've reviewed the draft. I find it well-written and proposing a good practical solution to the very common case in L3 overlay networks. I particularly appreciate the coverage of several tunneling protocols that the draft provides. I've noticed that Geneve protocol (RFC 8926) is not listed. As a non-blocking comment, perhaps the case for Geneve can be added to the document. > In conclusion, I support progressing this document to its publication as Standard RFC. Hi Greg, Thanks for your support. Adding Geneve encapsulation to this draft seems reasonable and I believe it would be easy to do. Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com > Regards, > Greg > > On Thu, Feb 4, 2021 at 7:52 AM Susan Hares <shares@ndzh.com> wrote: >> >> Greetings: >> >> >> >> This begins a modified draft-ietf-idr-flowspec-nvo3-12.txt. >> >> >> >> It is a modified WG LC because: >> >> 1) the WG still has to discussion where we make the cutoff for >> flow-specification v2, >> >> 2) there are no implementation for this WG LC >> >> >> >> This WG LC should examine the following things: >> >> >> >> 1.) Does WG to standardize this technology with >> >> the IPR Statement (which appeared in 5/8/2020 after a modification of the draft)? >> >> >> >> 2) Is this approach to flow-specification for tunnels ready for standardization? >> >> >> >> 3) Would this technology inter-work with tunnels created by >> >> draft-ietf-idr-tunnel-encap-22.txt? >> >> >> >> 4) Should this technology wait for a flow-specification v2? >> >> >> >> Cheerily, Sue >> >> >> >> _______________________________________________ >> Idr mailing list >> Idr@ietf.org >> https://www.ietf.org/mailman/listinfo/idr > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr