RFC 3150: End-to-end Performance Implications of Slow Links
In plain English — editorial summary, not part of the RFC
This document makes performance-related recommendations for users of network paths that traverse "very low bit-rate" links. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3150
- Published
- July 2001
- Authors
- S. Dawkins; G. Montenegro; M. Kojo; V. Magret
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 17
- Also known as
- BCP48
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 3135Performance Enhancing Proxies Intended to Mitigate Link-Related DegradationsCurrent
June 2001
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
- RFC 2887The Reliable Multicast Design Space for Bulk Data TransferCurrent
August 2000
- RFC 3489STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)Obsoleted
March 2003
- RFC 2722Traffic Flow Measurement: ArchitectureCurrent
October 1999
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 2064Traffic Flow Measurement: Meter MIBObsoleted
January 1997
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?