RFC 3882: Configuring BGP to Block Denial-of-Service Attacks
In plain English — editorial summary, not part of the RFC
This document describes an operational technique that uses BGP communities to remotely trigger black-holing of a particular destination network to block denial-of-service attacks. Black-holing can be applied on a selection of routers rather than all BGP-speaking routers in the network. The document also describes a sinkhole tunnel technique using BGP communities and tunnels to pull traffic into a sinkhole router for analysis. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3882
- Published
- October 2004
- Authors
- D. Turk
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3704Ingress Filtering for Multihomed NetworksUpdated
March 2004
- RFC 4098Terminology for Benchmarking BGP Device Convergence in the Control PlaneCurrent
June 2005
- RFC 3631Security Mechanisms for the InternetCurrent
December 2003
- RFC 3562Key Management Considerations for the TCP MD5 Signature OptionCurrent
July 2003
- RFC 4264BGP WedgiesCurrent
November 2005
- RFC 4272BGP Security Vulnerabilities AnalysisCurrent
January 2006
- RFC 4273Definitions of Managed Objects for BGP-4Current
January 2006
- RFC 4274BGP-4 Protocol AnalysisCurrent
January 2006
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?