IETF Logo Mail Archive

[Idr] 答复: WG LC for draft-ietf-idr-flowspec-l2vpn-15.txt (6/24 - 7/8)

Haoweiguo <haoweiguo@huawei.com> Wed, 01 July 2020 06:34 UTC

Return-Path: <haoweiguo@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 01A723A084B; Tue, 30 Jun 2020 23:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 GI41OoPLIwNu; Tue, 30 Jun 2020 23:34:09 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 4B99D3A084A; Tue, 30 Jun 2020 23:34:09 -0700 (PDT)
Received: from lhreml745-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 0C4E65C4A96DFE2CBC0A; Wed, 1 Jul 2020 07:34:08 +0100 (IST)
Received: from nkgeml706-chm.china.huawei.com (10.98.57.153) by lhreml745-chm.china.huawei.com (10.201.108.195) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 1 Jul 2020 07:34:07 +0100
Received: from nkgeml706-chm.china.huawei.com (10.98.57.153) by nkgeml706-chm.china.huawei.com (10.98.57.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 1 Jul 2020 14:34:05 +0800
Received: from nkgeml706-chm.china.huawei.com ([10.98.57.153]) by nkgeml706-chm.china.huawei.com ([10.98.57.153]) with mapi id 15.01.1913.007; Wed, 1 Jul 2020 14:34:05 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: Donald Eastlake <d3e3e3@gmail.com>, Susan Hares <shares@ndzh.com>
CC: "idr@ietf. org" <idr@ietf.org>, "draft-ietf-idr-flowspec-l2vpn@ietf.org" <draft-ietf-idr-flowspec-l2vpn@ietf.org>
Thread-Topic: WG LC for draft-ietf-idr-flowspec-l2vpn-15.txt (6/24 - 7/8)
Thread-Index: AdZKirvVBoavu7paTVaTwDYe2TARRQEjteUAABX9hEA=
Date: Wed, 01 Jul 2020 06:34:05 +0000
Message-ID: <cbc95a9e2a71474890498a6a99e19fcd@huawei.com>
References: <005501d64a8a$e3e7a640$abb6f2c0$@ndzh.com> <CAF4+nEHvb1t6JSCn=aFEFaX8hwoo_b3pp7pLvrZPKNOjK--HiA@mail.gmail.com>
In-Reply-To: <CAF4+nEHvb1t6JSCn=aFEFaX8hwoo_b3pp7pLvrZPKNOjK--HiA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.81.160]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/rHY6hHU56jPgBKl3M-0z3VHtFIM>
Subject: [Idr] 答复: WG LC for draft-ietf-idr-flowspec-l2vpn-15.txt (6/24 - 7/8)
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, 01 Jul 2020 06:34:11 -0000

Hi,
I also support this draft as a co-author.

Thanks,
Jason

-----邮件原件-----
发件人: Donald Eastlake [mailto:d3e3e3@gmail.com] 
发送时间: 2020年7月1日 12:04
收件人: Susan Hares <shares@ndzh.com>
抄送: idr@ietf. org <idr@ietf.org>; draft-ietf-idr-flowspec-l2vpn@ietf.org
主题: Re: WG LC for draft-ietf-idr-flowspec-l2vpn-15.txt (6/24 - 7/8)

Hi,

I support this draft as a co-author.

On Wed, Jun 24, 2020 at 8:52 PM Susan Hares <shares@ndzh.com> wrote:
> This begins a 2 week WG LC for draft-ietf-idr-flowspec-l2vpn-15.txt
>
> You can obtain the draft at:
> https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-l2vpn/
>
> There is IPR filing on this draft which can be found at:
> https://datatracker.ietf.org/ipr/4142/
>
> This draft does not have 2 implementation so it will be held for 2 implementations.
>
>
> In reviewing the draft please consider:
>
> 1) Should this functionality be included in RFC5575bis, or should it 
> wait for Flow Specification v2?

This draft is consistent with and extends the approved rfc5575bis draft. I do not think it needs to wait for flowspec2.

> 2) Do you think this technology is need by BGP deployments?

Yes based on uses described in the draft.

> 3) Do you think this draft technology is ready for implementation?
> 4) Do you think the draft is clear and ready for publication?

I believe the draft is ready for publication and implementation.

> Cheerily, Susan Hares

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA  d3e3e3@gmail.com

v2.23.0 | Report a Bug | By Email