RFC 6666: A Discard Prefix for IPv6
In plain English — editorial summary, not part of the RFC
Remote triggered black hole filtering describes a method of mitigating the effects of denial-of-service attacks by selectively discarding traffic based on source or destination address. Remote triggered black hole routing describes a method of selectively re- routing traffic into a sinkhole router (for further analysis) based on destination address. This document updates the "IPv6 Special Purpose Address Registry" by explaining why a unique IPv6 prefix should be formally assigned by IANA for the purpose of facilitating IPv6 remote triggered black hole filtering and routing. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6666
- Published
- August 2012
- Authors
- N. Hilliard; D. Freedman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5635Remote Triggered Black Hole Filtering with Unicast Reverse Path Forwarding (uRPF)Current
August 2009
- RFC 7999BLACKHOLE CommunityCurrent
October 2016
- RFC 6673Round-Trip Packet Loss MetricsCurrent
August 2012
- RFC 6676Multicast Addresses for DocumentationCurrent
August 2012
- RFC 6645IP Flow Information Accounting and Export Benchmarking MethodologyCurrent
July 2012
- RFC 6643Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG ModulesCurrent
July 2012
- RFC 6632An Overview of the IETF Network Management StandardsCurrent
June 2012
- RFC 6703Reporting IP Network Performance Metrics: Different Points of ViewCurrent
August 2012
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?