[rfc-dist] RFC 4987 on TCP SYN Flooding Attacks and Common Mitigations

[rfc-editor@rfc-editor.org]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4987

        Title:      TCP SYN Flooding Attacks and 
                    Common Mitigations 
        Author:     W. Eddy
        Status:     Informational
        Date:       August 2007
        Mailbox:    weddy at grc.nasa.gov
        Pages:      19
        Characters: 48753
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tcpm-syn-flood-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4987.txt

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.

This document is a product of the TCP Maintenance and Minor Extensions
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...