RFC 4963 on IPv4 Reassembly Errors at High Data Rates
rfc-editor@rfc-editor.org Fri, 27 July 2007 21:35 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEXTL-0003gJ-PR; Fri, 27 Jul 2007 17:35:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEXTK-0003gC-0s for ietf-announce@ietf.org; Fri, 27 Jul 2007 17:35:42 -0400
Received: from bosco.isi.edu ([128.9.168.207]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEXTJ-0007uj-JA for ietf-announce@ietf.org; Fri, 27 Jul 2007 17:35:41 -0400
Received: by bosco.isi.edu (Postfix, from userid 70) id DE22BDAC1B; Fri, 27 Jul 2007 14:33:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070727213330.DE22BDAC1B@bosco.isi.edu>
Date: Fri, 27 Jul 2007 14:33:30 -0700
X-Spam-Score: -14.3 (--------------)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4963 on IPv4 Reassembly Errors at High Data Rates
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
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: jheffner@psc.edu,
mathis@psc.edu,
bchandle@gmail.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-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@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@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@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce