RFC 4987: TCP SYN Flooding Attacks and Common Mitigations
In plain English — editorial summary, not part of the RFC
This document describes TCP SYN flooding attacks, which have been well-known to the community for several years. Various countermeasures against these attacks, and the trade-offs of each, are described. This document archives explanations of the attack and common defense techniques for the benefit of TCP implementers and administrators of TCP servers or networks, but does not make any standards-level recommendations. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4987
- Published
- August 2007
- Authors
- W. Eddy
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 9175Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token ProcessingCurrent
February 2022
- RFC 5358Preventing Use of Recursive Nameservers in Reflector AttacksCurrent
October 2008
- RFC 6178Label Edge Router Forwarding of IPv4 Option PacketsCurrent
March 2011
- RFC 3704Ingress Filtering for Multihomed NetworksUpdated
March 2004
- RFC 6952Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
May 2013
- RFC 2827Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingUpdated
May 2000
- RFC 8019Protecting Internet Key Exchange Protocol Version 2 (IKEv2) Implementations from Distributed Denial-of-Service AttacksCurrent
November 2016
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?