[Idr] 答复: WG Adoption call for drafts for Flow Specification option 1 (RFC5575 additions (filters/actions) 3/25 to 4/8/2016

Liangqiandeng <liangqiandeng@huawei.com> Tue, 05 April 2016 10:06 UTC

Return-Path: <liangqiandeng@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 D568712D1A0 for <idr@ietfa.amsl.com>; Tue, 5 Apr 2016 03:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 suyYvwgQ3f-5 for <idr@ietfa.amsl.com>; Tue, 5 Apr 2016 03:06:33 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CFE412D10B for <idr@ietf.org>; Tue, 5 Apr 2016 03:06:31 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLP13779; Tue, 05 Apr 2016 10:06:29 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 5 Apr 2016 11:06:19 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.56]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Tue, 5 Apr 2016 18:06:12 +0800
From: Liangqiandeng <liangqiandeng@huawei.com>
To: Susan Hares <shares@ndzh.com>, "'Steven Cheung (stecheun)'" <stecheun@cisco.com>
Thread-Topic: [Idr] WG Adoption call for drafts for Flow Specification option 1 (RFC5575 additions (filters/actions) 3/25 to 4/8/2016
Thread-Index: AdGGpJY5wzIcQ0EdQtuQOi1AWSw1WgEvHxWAAEPbLoD//6hGAP/6SJkQ
Date: Tue, 05 Apr 2016 10:06:12 +0000
Message-ID: <FCA9153F864C2646BE37F183391FCADD01745454@nkgeml513-mbx.china.huawei.com>
References: <000401d186a5$38fac760$aaf05620$@ndzh.com> <D322B1D3.11D83%mohamirz@cisco.com> <D32471FF.6CDC0%stecheun@cisco.com> <002f01d18c87$b51e4af0$1f5ae0d0$@ndzh.com>
In-Reply-To: <002f01d18c87$b51e4af0$1f5ae0d0$@ndzh.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.113.180]
Content-Type: multipart/alternative; boundary="_000_FCA9153F864C2646BE37F183391FCADD01745454nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.57038E25.01E1, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.56, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9e4ed0f3cbfa145a8bee645674b384ad
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/Bqxog60AoWfn8eSV5qmTcQhfc-o>
Cc: "'idr@ietf. org'" <idr@ietf.org>
Subject: [Idr] 答复: WG Adoption call for drafts for Flow Specification option 1 (RFC5575 additions (filters/actions) 3/25 to 4/8/2016
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 05 Apr 2016 10:06:36 -0000

Hi Sue, John,

I support adoption of followings, and I would discuss more for them.
https://datatracker.ietf.org/doc/draft-eddy-idr-flowspec-packet-rate/
https://datatracker.ietf.org/doc/draft-hao-idr-flowspec-nvo3/
https://datatracker.ietf.org/doc/draft-liang-idr-bgp-flowspec-label/
https://datatracker.ietf.org/doc/draft-yong-idr-flowspec-mpls-match/
https://datatracker.ietf.org/doc/draft-litkowski-idr-flowspec-interfaceset/
https://datatracker.ietf.org/doc/draft-hao-idr-flowspec-redirect-tunnel/
https://datatracker.ietf.org/doc/draft-li-idr-flowspec-redirect-generalized-sid/
https://datatracker.ietf.org/doc/draft-vandevelde-idr-flowspec-path-redirect/

Regards,
Qiandeng

·¢¼þÈË: Idr [mailto:idr-bounces@ietf.org] ´ú±í Susan Hares
·¢ËÍʱ¼ä: 2016Äê4ÔÂ2ÈÕ 10:31
ÊÕ¼þÈË: 'Steven Cheung (stecheun)'
³­ËÍ: 'idr@ietf. org'
Ö÷Ìâ: Re: [Idr] WG Adoption call for drafts for Flow Specification option 1 (RFC5575 additions (filters/actions) 3/25 to 4/8/2016

Steven:

Can you provide some insight into why you consider the
https://datatracker.ietf.org/doc/draft-vandevelde-idr-flowspec-path-redirect/

specific enough to consider for option one while others posting on this list do not consider it specific enough?

Sue

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Steven Cheung (stecheun)
Sent: Friday, April 01, 2016 9:45 PM
To: Susan Hares
Cc: 'idr@ietf. org'
Subject: Re: [Idr] WG Adoption call for drafts for Flow Specification option 1 (RFC5575 additions (filters/actions) 3/25 to 4/8/2016

Hi, Sue, John,

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

Thanks.
-Steven

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Friday, March 25, 2016 at 7:47 AM
To: "'idr@ietf. org'" <idr@ietf.org<mailto:idr@ietf.org>>
Subject: [Idr] WG Adoption call for drafts for Flow Specification option 1 (RFC5575 additions (filters/actions) 3/25 to 4/8/2016

IDR WG:

This begins a 2 week WG Call (3/25 to 4/8/2016) for the set of drafts to be considered in RFC5575 additions. These options are filters, actions or critical security additions.  The flow specification work has been a part of the interims since IETF 94
https://www.ietf.org/proceedings/interim/2016/02/08/idr/proceedings.html
https://www.ietf.org/proceedings/interim/2016/03/07/idr/proceedings.html

There will be a brief flow specification presentation at IETF 95, and the email list has select to start with option 1 ¨C extending RFC5575.  We also will be gathering details on the SDN/NFV use case for option 2 (new NLRI and Wide Communities support).

This is a group call for the drafts to be considered in the flow specification work.  For each of the drafts you wish to be considered Option 1, please indicate:


1)      If this option is valuable for the DDoS deployments or another critical deployments,

2)      Do you feel this draft is useful, but not ready for adoption,

3)      Do you feel this draft is a good start for this work.

The drafts to consider are:
https://datatracker.ietf.org/doc/draft-eddy-idr-flowspec-packet-rate/
https://datatracker.ietf.org/doc/draft-hao-idr-flowspec-nvo3/
https://datatracker.ietf.org/doc/draft-hao-idr-flowspec-redirect-tunnel/
https://datatracker.ietf.org/doc/draft-li-idr-flowspec-redirect-generalized-sid/
https://datatracker.ietf.org/doc/draft-liang-idr-bgp-flowspec-label/
https://datatracker.ietf.org/doc/draft-litkowski-idr-flowspec-interfaceset/
https://datatracker.ietf.org/doc/draft-vandevelde-idr-flowspec-path-redirect/
https://datatracker.ietf.org/doc/draft-yong-idr-flowspec-mpls-match/

And for the ordering of these filters and actions drafts ¨C the Option 1 section out of this
https://datatracker.ietf.org/doc/draft-hares-idr-flowspec-combo/
(A revised draft with just Option 1 will be posted)

Sue Hares and John Scudder