RFC 3155: End-to-end Performance Implications of Links with Errors
In plain English — editorial summary, not part of the RFC
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 specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3155
- Published
- August 2001
- Authors
- S. Dawkins; G. Montenegro; M. Kojo; V. Magret; N. Vaidya
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 16
- Also known as
- BCP50
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3135Performance Enhancing Proxies Intended to Mitigate Link-Related DegradationsCurrent
June 2001
- RFC 1835Architecture of the WHOIS++ serviceCurrent
August 1995
- RFC 1834Whois and Network Information Lookup Service, Whois++Current
August 1995
- RFC 2963A Rate Adaptive Shaper for Differentiated ServicesCurrent
October 2000
- RFC 2923TCP Problems with Path MTU DiscoveryCurrent
September 2000
- RFC 2884Performance Evaluation of Explicit Congestion Notification (ECN) in IP NetworksCurrent
July 2000
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- RFC 2757Long Thin NetworksCurrent
January 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?