Applying BGP flowspec rules on a specific interface set
draft-litkowski-idr-flowspec-interfaceset-03

Document Type Replaced Internet-Draft (idr WG)
Last updated 2016-03-25 (latest revision 2015-12-08)
Replaced by draft-ietf-idr-flowspec-interfaceset
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-idr-flowspec-interfaceset
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-litkowski-idr-flowspec-interfaceset-03.txt

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.

Authors

Stephane Litkowski (stephane.litkowski@orange.com)
Adam Simpson (adam.simpson@alcatel-lucent.com)
Keyur Patel (keyupate@cisco.com)
Jeffrey Haas (jhaas@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)