RFC 3449: TCP Performance Implications of Network Path Asymmetry
In plain English — editorial summary, not part of the RFC
This document describes TCP performance problems that arise because of asymmetric effects. These problems arise in several access networks, including bandwidth-asymmetric networks and packet radio subnetworks, for different underlying reasons. However, the end result on TCP performance is the same in both cases: performance often degrades significantly because of imperfection and variability in the ACK feedback from the receiver to the sender. The document details several mitigations to these effects, which have either been proposed or evaluated in the literature, or are currently deployed in networks. These solutions use a combination of local link- layer techniques, subnetwork, and end-to-end mechanisms, consisting of: (i) techniques to manage the channel used for the upstream bottleneck link carrying the ACKs, typically using header compression or reducing the frequency of TCP ACKs, (ii) techniques to handle this reduced ACK frequency to retain the TCP sender's acknowledgment-triggered self- clocking and (iii) techniques to schedule the data and ACK packets in the reverse direction to improve performance in the presence of two-way traffic. Each technique is described, together with known issues, and recommendations for use. A summary of the recommendations is provided at the end of the document. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3449
- Published
- December 2002
- Authors
- H. Balakrishnan; V. Padmanabhan; G. Fairhurst; M. Sooriyabandara
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 41
- Also known as
- BCP69
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2883An Extension to the Selective Acknowledgement (SACK) Option for TCPCurrent
July 2000
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- RFC 3373Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point AdjacenciesObsoleted
September 2002
- RFC 3316Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular HostsObsoleted
May 2003
- RFC 1962The PPP Compression Control Protocol (CCP)Updated
June 1996
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
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?