End-to-end Performance Implications of Links with Errors
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3155.
|Authors||Gabriel Montenegro , Markku Kojo , Nitin Vaidya , Vincent Magret , Spencer Dawkins|
|Last updated||2013-03-02 (Latest revision 2001-06-12)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|IESG||IESG state||RFC 3155 (Best Current Practice)|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. BCP 50 RFC 3155 Title: End-to-end Performance Implications of Links with Errors Author(s): S. Dawkins, G. Montenegro, M. Kojo, V. Magret, N. Vaidya Status: Best Current Practice Date: August 2001 Mailbox: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Pages: 15 Characters: 36388 SeeAlso: BCP 50 I-D Tag: draft-ietf-pilc-error-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3155.txt This document discusses the specific TCP mechanisms that are problematic in environments with high uncorrected error rates, and discusses what can be done to mitigate the problems without introducing intermediate devices into the connection. This document is a product of the Performance Implications of Link Characteristics Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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.