Subject: [Idr] FW: I-D Action: draft-litkowski-idr-flowspec-interfaceset-03.txt

From: <[email-masked]>
Date: Tue, 8 Dec 2015 15:01:34 +0000

Hi IDR folks,

Please find below an update of the interface-set extension draft for BGP Flowspec.
The major changes are :
- call for using a Route Target instead of a generic extended community to allow constrained route distribution.
- add considerations about using ADD PATH when the same filter need to be applied with different actions on different interface-sets.

Please provide your feedback.

Best Regards,

Stephane

-----Original Message-----
From: I-D-Announce [mailto:[email-masked]] On Behalf Of [email-masked]
Sent: Tuesday, December 08, 2015 15:57
To: [email-masked]
Subject: I-D Action: draft-litkowski-idr-flowspec-interfaceset-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

        Title           : Applying BGP flowspec rules on a specific interface set
        Authors         : Stephane Litkowski
                          Adam Simpson
                          Keyur Patel
                          Jeff Haas
	Filename        : draft-litkowski-idr-flowspec-interfaceset-03.txt
	Pages           : 13
	Date            : 2015-12-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 does not detail where the
   flow specification rules need to be applied.

   This document presents a new interface-set flowspec action that will
   be used in complement of other actions (marking, rate-limiting ...).
   The purpose of this extension is to inform remote routers on where to
   apply the flow specification.

   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-litkowski-idr-flowspec-interfaceset/

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

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

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/

_______________________________________________
I-D-Announce mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_________________________________________________________________________________________________________________________

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,
France Telecom - 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 authorization.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange shall not be liable if this message was modified, changed or falsified.
Thank you.