RFC 2525 on TCP Implementation Problems
RFC Editor <rfc-ed@ISI.EDU> Wed, 10 March 1999 00:25 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22084 for ietf-123-outbound.10@ietf.org; Tue, 9 Mar 1999 19:25:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22008 for <all-ietf@ietf.org>; Tue, 9 Mar 1999 19:19:30 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA06173; Tue, 9 Mar 1999 16:19:28 -0800 (PST)
Message-Id: <199903100019.QAA06173@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2525 on TCP Implementation Problems
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 09 Mar 1999 16:19:27 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2525: Title: Known TCP Implementation Problems Author(s): V. Paxson, M Allman, S. Dawson, W. Fenner, J. Griner, I. Heavens, K. Lahey, J. Semke, B. Volz Status: Informational Date: March 1999 Mailbox: vern@ee.lbl.gov, mallman@lerc.nasa.gov, sdawson@eecs.umich.edu, fenner@parc.xerox.com, jgriner@lerc.nasa.gov, ian@spider.com, kml@nas.nasa.gov, semke@psc.edu, volz@process.com Pages: 61 Characters: 137201 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-tcpimpl-prob-05.txt URL: ftp://ftp.isi.edu/in-notes/rfc2525.txt This memo catalogs a number of known TCP implementation problems. The goal in doing so is to improve conditions in the existing Internet by enhancing the quality of current TCP/IP implementations. It is hoped that both performance and correctness issues can be resolved by making implementors aware of the problems and their solutions. In the long term, it is hoped that this will provide a reduction in unnecessary traffic on the network, the rate of connection failures due to protocol errors, and load on network servers due to time spent processing both unsuccessful connections and retransmitted data. This will help to ensure the stability of the global Internet. This document is a product of the TCP Implementation Working Group of the IETF. 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.echo 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. Joyce K. Reynolds and Alegre Ramos USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2525 on TCP Implementation Problems RFC Editor