RFC 7999: BLACKHOLE Community
In plain English — editorial summary, not part of the RFC
This document describes the use of a well-known Border Gateway Protocol (BGP) community for destination-based blackholing in IP networks. This well-known advisory transitive BGP community named "BLACKHOLE" allows an origin Autonomous System (AS) to specify that a neighboring network should discard any traffic destined towards the tagged IP prefix.
Document record
- Document ID
- RFC7999
- Published
- October 2016
- Authors
- T. King; C. Dietzel; J. Snijders; G. Doering; G. Hankins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6666A Discard Prefix for IPv6Current
August 2012
- RFC 5635Remote Triggered Black Hole Filtering with Unicast Reverse Path Forwarding (uRPF)Current
August 2009
- RFC 8307Well-Known URIs for the WebSocket ProtocolCurrent
January 2018
- RFC 7611BGP ACCEPT_OWN Community AttributeCurrent
August 2015
- RFC 8020NXDOMAIN: There Really Is Nothing UnderneathCurrent
November 2016
- RFC 8022A YANG Data Model for Routing ManagementObsoleted
November 2016
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 7971Application-Layer Traffic Optimization (ALTO) Deployment ConsiderationsCurrent
October 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?