RFC 4732: Internet Denial-of-Service Considerations
In plain English — editorial summary, not part of the RFC
This document provides an overview of possible avenues for denial-of-service (DoS) attack on Internet systems. The aim is to encourage protocol designers and network engineers towards designs that are more robust. We discuss partial solutions that reduce the effectiveness of attacks, and how some solutions might inadvertently open up alternative vulnerabilities. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4732
- Published
- December 2006
- Authors
- M. Handley; E. Rescorla; IAB
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 38
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3631Security Mechanisms for the InternetCurrent
December 2003
- RFC 4987TCP SYN Flooding Attacks and Common MitigationsCurrent
August 2007
- RFC 5358Preventing Use of Recursive Nameservers in Reflector AttacksCurrent
October 2008
- RFC 3882Configuring BGP to Block Denial-of-Service AttacksCurrent
October 2004
- RFC 3704Ingress Filtering for Multihomed NetworksUpdated
March 2004
- RFC 6178Label Edge Router Forwarding of IPv4 Option PacketsCurrent
March 2011
- RFC 2827Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingUpdated
May 2000
- RFC 6952Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
May 2013
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?