BGP Flow Specification Packet-Rate Action
draft-ietf-idr-flowspec-packet-rate-01

Document Type Active Internet-Draft (idr WG)
Last updated 2016-12-02
Replaces draft-eddy-idr-flowspec-packet-rate
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
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)
Inter-Domain Routing (IDR)                                       W. Eddy
Internet-Draft                                                 J. Dailey
Intended status: Standards Track                                G. Clark
Expires: June 5, 2017                                        MTI Systems
                                                        December 2, 2016

               BGP Flow Specification Packet-Rate Action
                 draft-ietf-idr-flowspec-packet-rate-01

Abstract

   This document defines a new type of traffic filtering action for the
   BGP flow specification.  The new packet-rate action allows specifying
   a rate-limit in number of packets per second.  This is intended to be
   used in combatting some types of denial of service attacks where the
   packet rate is more important than the raw bitrate of the attack
   traffic.

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 June 5, 2017.

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

Eddy, et al.              Expires June 5, 2017                  [Page 1]
Internet-Draft         Flowspec Packet-Rate Action         December 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Packet Rate Action  . . . . . . . . . . . . . . . . . . . . .   2
   3.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The existing BGP flow specification [RFC5575] standard supports
   traffic-rate limits conveyed in bytes per second.  In some cases, it
   may be easier, faster, or more relevant to perform accounting and
   decision-making based on quantities of packets per second.  It is
   desirable to specify rate limits in terms of the number of packets
   per second, and not just the number of bytes per second.

   As an example use case, there are several types of denial of service
   attacks that do not require large amounts of bandwidth, but operate
   based on a cadence of packets over time.  TCP SYN flooding attacks
   are one well-known example [RFC4987], along with common packet-rate
   limits applied to ICMP messages and packets to unknown UDP ports.

1.1.  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 RFC 2119 [RFC2119].

2.  Packet Rate Action

   The traffic filtering actions pertaining to a matched flow
   specification are indicated using BGP extended communities [RFC7153].
   Particular extended community values are defined in RFC 5575 for a
   number of possible actions.  New types of actions can be defined
   using additional extended community values.  The value 0x8006 has
   been defined as the "traffic-rate" action, and specifies a rate-limit
Show full document text