Applying BGP flowspec rules on a specific interface set
draft-ietf-idr-flowspec-interfaceset-03
Routing Area Working Group S. Litkowski
Internet-Draft Orange
Intended status: Standards Track A. Simpson
Expires: September 12, 2017 Nokia
K. Patel
Arrcus, Inc
J. Haas
Juniper Networks
L. Yong
Huawei
March 11, 2017
Applying BGP flowspec rules on a specific interface set
draft-ietf-idr-flowspec-interfaceset-03
Abstract
BGP flowspec 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 flowspec 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 flowspec ([RFC5575]) introduces the
notion of flow specification (which describes the matching criterion)
and traffic filtering actions. The flow specification is encoded as
part of the NLRI while the traffic filtering actions are encoded as
extended communities. The combination of a flow specification and
one or more actions is known as a flow specification rule. [RFC5575]
does not detail where the flow specification rules need to be
applied.
Besides the flow specification and traffic filtering actions, this
document introduces the notion of traffic filtering scope in order to
drive where a particular rule must be applied. In particular, this
document introduces the "interface-set" traffic filtering scope that
could be used in parallel of traffic filtering actions (marking,
rate-limiting ...). The purpose of this extension is to inform
remote routers about groups of interfaces where the rule must be
applied.
Litkowski, et al. Expires September 12, 2017 [Page 1]
Internet-Draft flowspec-interfaceset March 2017
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].
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 September 12, 2017.
Copyright Notice
Copyright (c) 2017 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.
Litkowski, et al. Expires September 12, 2017 [Page 2]
Internet-Draft flowspec-interfaceset March 2017
Show full document text