RFC 3481: TCP over Second (2.5G) and Third (3G) Generation Wireless Networks
In plain English — editorial summary, not part of the RFC
This document describes a profile for optimizing TCP to adapt so that it handles paths including second (2.5G) and third (3G) generation wireless networks. It describes the relevant characteristics of 2.5G and 3G networks, and specific features of example deployments of such networks. It then recommends TCP algorithm choices for nodes known to be starting or ending on such paths, and it also discusses open issues. The configuration options recommended in this document are commonly found in modern TCP stacks, and are widely available standards-track mechanisms that the community considers safe for use on the general Internet. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3481
- Published
- February 2003
- Authors
- H. Inamura; G. Montenegro; R. Ludwig; A. Gurtov; F. Khafizov
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 26
- Also known as
- BCP71
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 3936Procedures for Modifying the Resource reSerVation Protocol (RSVP)Current
October 2004
- RFC 3489STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)Obsoleted
March 2003
- RFC 3453The Use of Forward Error Correction (FEC) in Reliable MulticastCurrent
December 2002
- RFC 3452Forward Error Correction (FEC) Building BlockObsoleted
December 2002
- RFC 3451Layered Coding Transport (LCT) Building BlockObsoleted
December 2002
- RFC 3450Asynchronous Layered Coding (ALC) Protocol InstantiationObsoleted
December 2002
- RFC 3449TCP Performance Implications of Network Path AsymmetryCurrent
December 2002
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?