RFC 4963 on IPv4 Reassembly Errors at High Data Rates

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

        
        RFC 4963

        Title:      IPv4 Reassembly Errors at High 
                    Data Rates 
        Author:     J. Heffner, M. Mathis,
                    B. Chandler
        Status:     Informational
        Date:       July 2007
        Mailbox:    jheffnerpsc.edu, 
                    mathispsc.edu, 
                    bchandlegmail.com
        Pages:      10
        Characters: 22399
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-heffner-frag-harmful-05.txt

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

IPv4 fragmentation is not sufficiently robust for use under
some
conditions in today's Internet.  At high data rates, the
16-bit IP
identification field is not large enough to prevent
frequent
incorrectly assembled IP fragments, and the TCP and UDP
checksums are
insufficient to prevent the resulting corrupted datagrams
from being
delivered to higher protocol layers.  This note describes
some easily
reproduced experiments demonstrating the problem, and
discusses some
of the operational implications of these observations.  This
memo provides information for the Internet community.


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-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list
should
be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

        To: rfc-infoRFC-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-ManagerRFC-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-EDITORRFC-EDITOR.ORG.  Please consult RFC 2223,
Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
rfc-dist mailing list
rfc-distmailman.rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org