BLACKHOLE BGP Community for Blackholing
draft-ymbk-grow-blackholing-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2016-01-30 (latest revision 2015-07-29) | ||
| Replaced by | draft-ietf-grow-blackholing | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-grow-blackholing | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ymbk-grow-blackholing-01.txt
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
(thomas.king@de-cix.net)
Christoph Dietzel
(christoph.dietzel@de-cix.net)
Job Snijders
(job@ntt.net)
Gert Doering
(gert@space.net)
Greg Hankins
(greg.hankins@alcatel-lucent.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)