Applying BGP flowspec rules on a specific interface set
draft-ietf-idr-flowspec-interfaceset-05
Inter-Domain Routing S. Litkowski
Internet-Draft Individual
Intended status: Standards Track A. Simpson
Expires: May 21, 2020 Nokia
K. Patel
Arrcus, Inc
J. Haas
Juniper Networks
L. Yong
Huawei
November 18, 2019
Applying BGP flowspec rules on a specific interface set
draft-ietf-idr-flowspec-interfaceset-05
Abstract
The BGP Flow Specification (flowspec) Network Layer Reachability
Information (BGP NLRI) extension (draft-ietf-idr-rfc5575bis) 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 allow
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", "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.
Litkowski, et al. Expires May 21, 2020 [Page 1]
Internet-Draft flowspec-interfaceset November 2019
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 May 21, 2020.
Copyright Notice
Copyright (c) 2019 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
(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. Use case . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Interface specific filtering using BGP flowspec . . . . . . . 3
3. Interface-set extended community . . . . . . . . . . . . . . 5
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
Show full document text