BLACKHOLE BGP Community for Blackholing
draft-ietf-grow-blackholing-00
Network Working Group T. King
Internet-Draft C. Dietzel
Intended status: Standards Track DE-CIX Management GmbH
Expires: May 12, 2016 J. Snijders
NTT
G. Doering
SpaceNet AG
G. Hankins
Alcatel-Lucent
November 9, 2015
BLACKHOLE BGP Community for Blackholing
draft-ietf-grow-blackholing-00
Abstract
This document describes the use of a well-known Border Gateway
Protocol (BGP) community for blackholing at IP networks and Internet
Exchange Points (IXP). This well-known advisory transitive BGP
community, namely BLACKHOLE, allows an origin AS to specify that a
neighboring IP network or IXP should blackhole a specific IP prefix.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
be interpreted as described in [RFC2119] only when they appear in all
upper case. They may also appear in lower or mixed case as English
words, without normative meaning.
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 May 12, 2016.
King, et al. Expires May 12, 2016 [Page 1]
Internet-Draft BLACKHOLE BGP Community for Blackholing November 2015
Copyright Notice
Copyright (c) 2015 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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. BLACKHOLE Attribute . . . . . . . . . . . . . . . . . . . . . 3
3. Operational Recommendations . . . . . . . . . . . . . . . . . 3
3.1. IP Prefix Announcements with BLACKHOLE Community Attached 3
3.2. Local Scope of Blackholes . . . . . . . . . . . . . . . . 3
3.3. Accepting Blackholed IP Prefixes . . . . . . . . . . . . 4
3.4. IXPs: Peering at Route Servers . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 6
6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
The network infrastructure has been getting hammered by DDoS attacks
for years. In order to block DDoS attacks, IP networks have offered
BGP blackholing to neighboring networks (iBGP scenarios [RFC3882] and
RTBH filtering [RFC5635]), much like some IXPs have recently started
to do.
DDoS attacks targeting a certain IP network may cause congestion of
links used to connect to other networks. In order to limit the
impact of such a scenario on legitimate traffic, IP networks and IXPs
adopted a mechanism called BGP blackholing. A network that wants to
trigger blackholing needs to understand the triggering mechanism
adopted by its neighboring IP networks and IXPs. Different IP
networks and IXPs provide different BGP mechanisms to trigger
Show full document text