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

Document Type Active Internet-Draft (idr WG)
Last updated 2018-06-30
Replaces draft-litkowski-idr-flowspec-interfaceset
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Reviews
Stream WG state WG Document
Other - see Comment Log
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Inter-Domain Routing                                        S. Litkowski
Internet-Draft                                                    Orange
Intended status: Standards Track                              A. Simpson
Expires: December 30, 2018                                         Nokia
                                                                K. Patel
                                                             Arrcus, Inc
                                                                 J. Haas
                                                        Juniper Networks
                                                                 L. Yong
                                                                  Huawei
                                                           June 28, 2018

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

Abstract

   The BGP Flow Specification (flowspec) Network Layer Reachability
   Information (BGP NLRI) extension ([RFC5575]) is used to distribute
   traffic flow specifications into BGP.  The primary application of
   this extension is the distribution of traffic filtering policies for
   the mitigation of distributed denial of service (DDoS) attacks.

   By default, flow specification filters are applied on all forwarding
   interfaces that are enabled for use by the BGP flowspec extension.  A
   network operator may wish to apply a given filter selectively to a
   subset of interfaces based on an internal classification scheme.
   Examples of this include "all customer interfaces", "all peer
   interfaces", "all transit interfaces", etc.

   This document defines BGP Extended Communities ([RFC4360]) that
   permit such filters to be selectively applied to sets of forwarding
   interfaces sharing a common group identifier.  The BGP Extended
   Communities carrying this group identifier are referred to as the BGP
   Flowspec "interface-set" Extended Communities.

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

Status of This Memo

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

Litkowski, et al.       Expires December 30, 2018               [Page 1]
Internet-Draft            flowspec-interfaceset                June 2018

   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 December 30, 2018.

Copyright Notice

   Copyright (c) 2018 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
   2.  Interface specific filtering using BGP flowspec . . . . . . .   3
   3.  Interface-set extended community  . . . . . . . . . . . . . .   4
   4.  Scaling of per-interface rules  . . . . . . . . . . . . . . .   6
   5.  Deployment Considerations . . . . . . . . . . . . . . . . . .   6
     5.1.  Add-Paths . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Inter-domain Considerations . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  FlowSpec Transitive Extended Communities  . . . . . . . .   7
     8.2.  FlowSpec Non-Transitive Extended Communities  . . . . . .   7
     8.3.  FlowSpec interface-set Extended Community . . . . . . . .   8
     8.4.  Allocation Advice to IANA . . . . . . . . . . . . . . . .   8
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

Show full document text