Re: [Idr] I-D Action: draft-ietf-idr-flowspec-interfaceset-01.txt

Hi IDR,

This is a new version of the interface-set flowspec extension.

As there was some misinterpretation of what the interface-set is (it is not a match (as not part of NLRI) and it is not an action), we defined the notion of traffic filtering scope. Interface-set would be the first traffic filtering scope defined, and nothing prevents to create new ones if required.

Best Regards,

Stephane

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Wednesday, June 08, 2016 15:26
To: i-d-announce@ietf.org
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-flowspec-interfaceset-01.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
	Filename        : draft-ietf-idr-flowspec-interfaceset-01.txt
	Pages           : 14
	Date            : 2016-06-08

Abstract:
   BGP Flow-spec 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 Flow-spec 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 Flow-spec ([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
   applied.

   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
   applied.

   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:
https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-interfaceset/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-flowspec-interfaceset-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-flowspec-interfaceset-01

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:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.