[Idr] [internet-drafts@ietf.org: I-D Action: draft-ietf-idr-flowspec-interfaceset-03.txt]

Jeffrey Haas <jhaas@pfrc.org> Tue, 14 March 2017 19:02 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1D44A1299D2 for <idr@ietfa.amsl.com>; Tue, 14 Mar 2017 12:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xwePK45EvSqi for <idr@ietfa.amsl.com>; Tue, 14 Mar 2017 12:02:20 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org []) by ietfa.amsl.com (Postfix) with ESMTP id EEF9E1314BE for <idr@ietf.org>; Tue, 14 Mar 2017 12:01:38 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 244241E33B; Tue, 14 Mar 2017 15:02:16 -0400 (EDT)
Date: Tue, 14 Mar 2017 15:02:15 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: idr@ietf.org
Message-ID: <20170314190215.GA12864@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/IEZZzJpec-JziWnP6d5kiTgBStE>
Subject: [Idr] [internet-drafts@ietf.org: I-D Action: draft-ietf-idr-flowspec-interfaceset-03.txt]
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Mar 2017 19:02:23 -0000

Note that the only change in -03 was to update the IANA considerations so
that the proposal could proceed with first come, first serve extended
community allocation from IANA.  

The authors intend to address the points Geoff Huston raised as part of
early routing directorate review in the next revision.  No protocol changes
are expected to result from that update.

-- Jeff

----- Forwarded message from internet-drafts@ietf.org -----

Date: Sat, 11 Mar 2017 07:17:07 -0800
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-flowspec-interfaceset-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : Applying BGP flowspec rules on a specific interface set
        Authors         : Stephane Litkowski
                          Adam Simpson
                          Keyur Patel
                          Jeff Haas
                          Lucy Yong
	Filename        : draft-ietf-idr-flowspec-interfaceset-03.txt
	Pages           : 15
	Date            : 2017-03-11

   BGP flowspec is an extension to BGP that allows for the dissemination
   of traffic flow specification rules.  The primary application of this
   extension is DDoS mitigation where the flowspec rules are applied in
   most cases to all peering routers of the network.

   This document will present another use case of BGP flowspec where
   flow specifications are used to maintain some access control lists at
   network boundary.  BGP flowspec is a very efficient distributing
   machinery that can help in saving OPEX while deploying/updating ACLs.
   This new application requires flow specification rules to be applied
   only on a specific subset of interfaces and in a specific direction.

   The current specification of BGP flowspec ([RFC5575]) introduces the
   notion of flow specification (which describes the matching criterion)
   and traffic filtering actions.  The flow specification is encoded as
   part of the NLRI while the traffic filtering actions are encoded as
   extended communities.  The combination of a flow specification and
   one or more actions is known as a flow specification rule.  [RFC5575]
   does not detail where the flow specification rules need to be

   Besides the flow specification and traffic filtering actions, this
   document introduces the notion of traffic filtering scope in order to
   drive where a particular rule must be applied.  In particular, this
   document introduces the "interface-set" traffic filtering scope that
   could be used in parallel of traffic filtering actions (marking,
   rate-limiting ...).  The purpose of this extension is to inform
   remote routers about groups of interfaces where the rule must be

   This extension can also be used in a DDoS mitigation context where a
   provider wants to apply the filtering only on specific peers.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

Idr mailing list

----- End forwarded message -----