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

"chenhuan6@chinatelecom.cn" <chenhuan6@chinatelecom.cn> Mon, 21 October 2019 15:54 UTC

Return-Path: <chenhuan6@chinatelecom.cn>
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 3ABFA1200CE for <idr@ietfa.amsl.com>; Mon, 21 Oct 2019 08:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 owBkbBqSOaNG for <idr@ietfa.amsl.com>; Mon, 21 Oct 2019 08:54:49 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.223]) by ietfa.amsl.com (Postfix) with ESMTP id 79CE5120044 for <idr@ietf.org>; Mon, 21 Oct 2019 08:54:48 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.92:4155.1432555301
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-119.130.200.83?logid-050173B2D1C649C5968E63FFEE292EFD (unknown [172.18.0.92]) by chinatelecom.cn (HERMES) with SMTP id 517DC280079; Mon, 21 Oct 2019 23:54:41 +0800 (CST)
X-189-SAVE-TO-SEND: 44093218@chinatelecom.cn
Received: from ([172.18.0.92]) by App0021 with ESMTP id 050173B2D1C649C5968E63FFEE292EFD for shares@ndzh.com; Mon Oct 21 23:54:43 2019
X-Transaction-ID: 050173B2D1C649C5968E63FFEE292EFD
X-filter-score: filter<0>
X-Real-From: chenhuan6@chinatelecom.cn
X-Receive-IP: 172.18.0.92
X-MEDUSA-Status: 0
Date: Mon, 21 Oct 2019 23:54:41 +0800
From: "chenhuan6@chinatelecom.cn" <chenhuan6@chinatelecom.cn>
To: "Susan Hares" <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
References: <015d01d582c4$388e04d0$a9aa0e70$@ndzh.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.12.322[cn]
Mime-Version: 1.0
Message-ID: <2019102123534077053549@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart272431822446_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ysj39EJ4ySTGc6b1uNd9CC0YCdU>
Subject: Re: [Idr] draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/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: Mon, 21 Oct 2019 15:54:53 -0000

Support the adoption. 
RPD gives us a new technical way to manage and depoy the BGP policy.
And then we can done dynamic policy basing on  the servcie agreement and data from telemetry.


Best Regards,
Huanan Chen


From: Susan Hares
Date: 2019-10-15 03:18
To: 'idr wg'
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