BGP Flowspec Capability Bits
draft-haas-flowspec-capability-bits-00

Document Type Active Internet-Draft (individual)
Author Jeffrey Haas 
Last updated 2021-02-21
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Inter-Domain Routing                                             J. Haas
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                       February 22, 2021
Expires: August 26, 2021

                      BGP Flowspec Capability Bits
                 draft-haas-flowspec-capability-bits-00

Abstract

   BGP Flowspec (RFC 5575) provides the ability to filter traffic using
   various matching components.  The NLRI format currently defined does
   not permit incremental deployment of new BGP Flowspec components.
   This draft defines a new BGP Capability to permit incremental
   deployment of such new Flowspec component types.

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 BCP 14 [RFC2119]
   [RFC8174] when, and only when, they appear in all capitals, as shown
   here.

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 https://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 August 26, 2021.

Copyright Notice

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

Haas                     Expires August 26, 2021                [Page 1]
Internet-Draft          flowspec-capability-bits           February 2021

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  BGP Flowspec Capability Bits  . . . . . . . . . . . . . . . .   3
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Restricting BGP Flowspec Components in a Deployment . . . . .   5
   5.  BGP Flowspec Implications for Filtered NLRI . . . . . . . . .   5
   6.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
     10.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Appendix A.  Encoding of the Bit-String . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   BGP Flowspec [RFC5575] provides a mechanism to distribute traffic
   flow spcifications into BGP.  One general purpose of these flow
   specifications is for the distribution of firewall rules to receiving
   routers, particularly for mitigating distributed denial of service
   (DDoS) attacks.  The flow specification rules are encoded as BGP NLRI
   [RFC4271].

   The matching components of a flow specification NLRI is a serialized
   set of optional components.  The components are documented in
   [RFC5575], Section 4.  [I-D.ietf-idr-flow-spec-v6] defines
   IPv6-specific components.  The full set of Flowspec component types
   is maintained in an IANA registry located at the IANA Flow Spec
   Component Types registry [1].

   Work is currently ongoing to address deficiencies in [RFC5575] in
   [I-D.ietf-idr-rfc5575bis].  In particular, unknown component types
   require treatment as a malformed NLRI ([I-D.ietf-idr-rfc5575bis],
   Section 4.1).  This is due to the lack of a mandatory length element

Haas                     Expires August 26, 2021                [Page 2]
Internet-Draft          flowspec-capability-bits           February 2021

   for the components in the NLRI.  Without such a length, it is not
   possible to determine how to properly decode unknown components in
Show full document text