Re: [Idr] 答复: 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019)

"Susan Hares" <shares@ndzh.com> Sat, 26 October 2019 14:29 UTC

Return-Path: <shares@ndzh.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 C42D0120046 for <idr@ietfa.amsl.com>; Sat, 26 Oct 2019 07:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.347
X-Spam-Level: *
X-Spam-Status: No, score=1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 eTZGjV5y2kNa for <idr@ietfa.amsl.com>; Sat, 26 Oct 2019 07:29:50 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14E32120024 for <idr@ietf.org>; Sat, 26 Oct 2019 07:29:49 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=166.170.20.155;
From: "Susan Hares" <shares@ndzh.com>
To: "'Wuhong \(rainbow\)'" <rainbow.wu@huawei.com>, "'Dongjie \(Jimmy\)'" <jie.dong@huawei.com>, "'idr wg'" <idr@ietf.org>, "'Haoweiguo'" <haoweiguo@huawei.com>
References: <015d01d582c4$388e04d0$a9aa0e70$@ndzh.com> <76CD132C3ADEF848BD84D028D243C927CD2DA691@NKGEML515-MBS.china.huawei.com> <E236C200C630B6438A92F433DECFB8EE9D9C823C@nkgeml513-mbs.china.huawei.com> <707c331ff77243f4af6e1da26d2a3b77@huawei.com> <17B081F80871264FAFBAAEDBCD87AF89BE83BF60@dggemm511-mbs.china.huawei.com>
In-Reply-To: <17B081F80871264FAFBAAEDBCD87AF89BE83BF60@dggemm511-mbs.china.huawei.com>
Date: Sat, 26 Oct 2019 10:29:36 -0400
Message-ID: <00bb01d58c09$cb86c8a0$629459e0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BC_01D58BE8.44772470"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLU+VkAtFReJj7nWCeYrGDVWw8d8wJP0I79AY8pbSoCs6ARQgFg1IIzpS6FMhA=
Content-Language: en-us
X-Antivirus: AVG (VPS 191023-2, 10/23/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/zhvI8lWTLxO2O9OVV6dFsYYnNbc>
Subject: Re: [Idr] =?gb2312?b?tPC4tDogILTwuLQ6ICBkcmFmdC1saS1pZHItZmxvd3Nw?= =?gb2312?b?ZWMtcnBkLTA1LnR4dCAtIFdHIEFkb3B0aW9uIGNhbGwgKDEwLzE0IHRvIDEw?= =?gb2312?b?LzI4LzIwMTkp?=
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: Sat, 26 Oct 2019 14:29:52 -0000

Rainbow:

 

This is extremely important feedback for me as the working group chair.
Thank you for sending me this feedback.

 

Cheerily, Susan Hares

 

From: Wuhong (rainbow) [mailto:rainbow.wu@huawei.com] 
Sent: Saturday, October 26, 2019 4:54 AM
To: Dongjie (Jimmy); Susan Hares; 'idr wg'; Haoweiguo
Subject: 答复: [Idr] 答复: 答复: draft-li-idr-flowspec-rpd-05.txt - WG
Adoption call (10/14 to 10/28/2019)

 

Hi,

We conducted innovation pilots and detailed in-depth technical exchanges
with users in some provinces in China. Customers recognized this technology
choice, which avoids conflicts with the configuration of existing routing
policies and avoids frequent changes to the configuration on the router.

I support the adoption of this document.

 

Thanks,

Rainbow 

 

 

发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Haoweiguo
发送时间: 2019年10月26日 16:23
收件人: Wenhuizhi <wenhuizhi@huawei.com>om>; Dongjie (Jimmy)
<jie.dong@huawei.com>om>; Susan Hares <shares@ndzh.com>om>; 'idr wg'
<idr@ietf.org>
主题: [Idr] 答复: 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call
(10/14 to 10/28/2019)

 

Hi,

I have read the latest draft and support the adoption of the document.

 

Thanks,

Jason

 

发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Wenhuizhi
发送时间: 26 uMfumfu 2019 04:20 PM
收件人: Dongjie (Jimmy) <jie.dong@huawei.com>om>; Susan Hares
<shares@ndzh.com>om>; 'idr wg' <idr@ietf.org>
主题: [Idr] 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14
to 10/28/2019)

 

Hi,

 

I think this draft provides a very good way to distribute routing policies.
In particular, when routing policy is already exist in the live network
configuration, the traditional method is very easy to bring wrong and
unnecessary impacts, the approach in this draft could well avoid this
situation. Thus I support the adoption of this document.

 

Best Wishes

 

Wen

 

发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Dongjie (Jimmy)
发送时间: 2019年10月26日 14:40
收件人: Susan Hares <shares@ndzh.com>om>; 'idr wg' <idr@ietf.org>
主题: Re: [Idr] draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14
to 10/28/2019)

 

Hi, 

 

I’ve read the latest version of this draft and think it is a good starting
point for the distribution of routing policies using BGP. Thus I support the
adoption of this document. 

 

Best regards,

Jie

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, October 15, 2019 3:19 AM
To: 'idr wg' <idr@ietf.org>
Subject: [Idr] draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to
10/28/2019)

 

This begins a 2 week WG adoption call for draft-li-idr-flowspec-rpd-05.txt 

(10/14 to 10/28/2019).  You can access the draft at: 

 

https://datatracker.ietf.org/doc/draft-li-idr-flowspec-rpd/

 

In your discussion regarding this draft consider if:

 

1)      Passing extended policy in BGP  is useful,

2)      Passing policy in wide community atom is a technical sound
mechanism,

3)      A deployment need exists for this technology. 

 

 

Susan Hares

Co-chair and shepherd