Re: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]

"Wanghaibo (Rainsword)" <rainsword.wang@huawei.com> Thu, 28 November 2019 06:24 UTC

Return-Path: <rainsword.wang@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 F30D4120BE3 for <idr@ietfa.amsl.com>; Wed, 27 Nov 2019 22:24:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 YESOSRm0LrR1 for <idr@ietfa.amsl.com>; Wed, 27 Nov 2019 22:24:30 -0800 (PST)
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 527A012022D for <idr@ietf.org>; Wed, 27 Nov 2019 22:24:30 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 55684381D6B2A35E915D for <idr@ietf.org>; Thu, 28 Nov 2019 06:24:28 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 28 Nov 2019 06:24:27 +0000
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0439.000; Thu, 28 Nov 2019 14:24:25 +0800
From: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]
Thread-Index: AdWd0gRnmm6Aw4Y9ShOHyzWN65U36QH4juaQ
Date: Thu, 28 Nov 2019 06:24:24 +0000
Message-ID: <1E61161D6E31D849BEA887261DB609348C9F8255@nkgeml514-mbx.china.huawei.com>
References: <016501d59dd2$e5458850$afd098f0$@ndzh.com>
In-Reply-To: <016501d59dd2$e5458850$afd098f0$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.110.113.35]
Content-Type: multipart/alternative; boundary="_000_1E61161D6E31D849BEA887261DB609348C9F8255nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LFRLUMxkRXaT1d7CLjDHpmeyMZg>
Subject: Re: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]
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, 28 Nov 2019 06:24:32 -0000

Hi Sue & WG,

I support the publication of this document.

1) Yes
2) Yes, it's useful for adjust traffic
3) Yes.
4) Yes

Thanks,
Shunwan


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, November 18, 2019 1:42 PM
To: idr@ietf.org
Subject: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]

This begins a 2 week WG Last call on draft-idr-flowspec-path-redirect-10.txt from [11/17/2019 to 12/2/2019].

You can obtain the draft at:

https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-path-redirect/

Consider in your review whether this draft:


1)      Is compatible with draft-ietf-rfc5575bis-17.txt?

2)      Whether the draft is useful for deployments of flow specification

3)      Is this technology ready for deployment?

4)      Is the write-up of this technology in draft-ietf-idr-flowspec-path-redirect clearly written and ready for publication?

Thank you for considering this draft.

Cheerily, Susan Hares