IETF Logo Mail Archive

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

"Mohammed Mirza (mohamirz)" <mohamirz@cisco.com> Thu, 31 March 2016 18:22 UTC

Return-Path: <mohamirz@cisco.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 93D5812D710 for <idr@ietfa.amsl.com>; Thu, 31 Mar 2016 11:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 bythu729RmBx for <idr@ietfa.amsl.com>; Thu, 31 Mar 2016 11:22:10 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B691112D0F4 for <idr@ietf.org>; Thu, 31 Mar 2016 11:22:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14106; q=dns/txt; s=iport; t=1459448529; x=1460658129; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Sc3TTDL/mRJ9wkTCeG61g00Rf9mizHtmxheJ5esrrXY=; b=Ss8UTDES1zeLwzPxQaJzTcwSJJBtqyJwC+7Ffi5fwZtAJyhouOksxw+m nMgI8WXQMWPjCZtYm6TKGHATOFsK8xT6FCGZqj6Ruhy4dnU4i9hkOkGsI a1NfsUDek43B24H/hFFv5f8E1SN3lmyqNYTHeOkpeYM7XjoK/25rubbpK Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DQAQBuaf1W/xbLJq1dgmiBH30GhT+1UQENgXEjhBOBVwKBexQBAQEBAQEBZSeEQQEBAQQdEFwCAQgOAwMBAiQEBzIUCQgBAQQBEhSIEw7CbgEBAQEBAQEBAQEBAQEBAQEBAQEBAREEhh6ERoE3glcRAT4NhSkFjX+JcwGFcogVgWaETYhajxQBHgEBQoIEDQwVgTVsAYc4Nn4BAQE
X-IronPort-AV: E=Sophos;i="5.24,423,1454976000"; d="scan'208,217";a="676463004"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Mar 2016 18:22:07 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u2VIM6Sf028044 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 31 Mar 2016 18:22:07 GMT
Received: from xch-rtp-019.cisco.com (64.101.220.159) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 31 Mar 2016 14:22:05 -0400
Received: from xch-rtp-019.cisco.com ([64.101.220.159]) by XCH-RTP-019.cisco.com ([64.101.220.159]) with mapi id 15.00.1104.009; Thu, 31 Mar 2016 14:22:05 -0400
From: "Mohammed Mirza (mohamirz)" <mohamirz@cisco.com>
To: Susan Hares <shares@ndzh.com>, "'idr@ietf. org'" <idr@ietf.org>
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: AdGGpJY5wzIcQ0EdQtuQOi1AWSw1WgEvHxWA
Date: Thu, 31 Mar 2016 18:22:05 +0000
Message-ID: <D322B1D3.11D83%mohamirz@cisco.com>
References: <000401d186a5$38fac760$aaf05620$@ndzh.com>
In-Reply-To: <000401d186a5$38fac760$aaf05620$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.9.151119
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.56.226]
Content-Type: multipart/alternative; boundary="_000_D322B1D311D83mohamirzciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/2D--xgRhfISVhCnQunKfXyKOV6E>
Subject: Re: [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: Thu, 31 Mar 2016 18:22:12 -0000

Hi, Sue, John,

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

I support the above draft that proposes use of a newly defined BGP extended Indirection_ID community. This new ext-comm looks like a good alternate to the "redirect-to-VRF" action for redirecting traffic towards an alternate destination and thus facilitating policy-based forwarding defined in flow-spec standard RFC5575.

Thanks,
Mohammed



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 - 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-li-idr-flowspec-redirect-generalized-sid/>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 - 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

v2.23.0 | Report a Bug | By Email