Applying BGP flowspec rules on a specific interface set
draft-ietf-idr-flowspec-interfaceset-00

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2016-06-06 (latest revision 2016-05-19)
Replaces draft-litkowski-idr-flowspec-interfaceset
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Routing Area Working Group                                  S. Litkowski
Internet-Draft                                                    Orange
Intended status: Standards Track                              A. Simpson
Expires: November 19, 2016                                Alcatel Lucent
                                                                K. Patel
                                                                   Cisco
                                                                 J. Haas
                                                        Juniper Networks
                                                            May 18, 2016

        Applying BGP flowspec rules on a specific interface set
                draft-ietf-idr-flowspec-interfaceset-00

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Litkowski, et al.       Expires November 19, 2016               [Page 1]
Internet-Draft            flowspec-interfaceset                 May 2016

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 19, 2016.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Use case  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Specific filtering for DDoS . . . . . . . . . . . . . . .   3
     1.2.  ACL maintenance . . . . . . . . . . . . . . . . . . . . .   4
   2.  Collaborative filtering and managing filter direction . . . .   5
   3.  Interface specific filtering using BGP flowspec . . . . . . .   6
   4.  Interface-set extended community  . . . . . . . . . . . . . .   7
   5.  Interaction with permanent traffic actions  . . . . . . . . .   8
     5.1.  Interaction with interface ACLs . . . . . . . . . . . . .   9
     5.2.  Interaction with flow collection  . . . . . . . . . . . .  10
   6.  Scaling of per interface rules  . . . . . . . . . . . . . . .  10
   7.  Deployment considerations . . . . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12

Litkowski, et al.       Expires November 19, 2016               [Page 2]
Show full document text