BLACKHOLE BGP Community for Blackholing
draft-ymbk-grow-blackholing-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Thomas King , Christoph Dietzel , Job Snijders , Gert Döring, Greg Hankins | ||
| Last updated | 2016-01-30 (Latest revision 2015-07-29) | ||
| Replaced by | draft-ietf-grow-blackholing | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-grow-blackholing | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Thomas King
Christoph Dietzel
Job Snijders
Gert Döring
Greg Hankins
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)