RFC 3448: TCP Friendly Rate Control (TFRC): Protocol Specification
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5348.
Current version: RFC 5348 — TCP Friendly Rate Control (TFRC): Protocol Specification
In plain English — editorial summary, not part of the RFC
This document specifies TCP-Friendly Rate Control (TFRC). TFRC is a congestion control mechanism for unicast flows operating in a best- effort Internet environment. It is reasonably fair when competing for bandwidth with TCP flows, but has a much lower variation of throughput over time compared with TCP, making it more suitable for applications such as telephony or streaming media where a relatively smooth sending rate is of importance. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3448
- Published
- January 2003
- Authors
- M. Handley; S. Floyd; J. Padhye; J. Widmer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 24
- Also known as
- —
- Obsoleted by:
- RFC 5348
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3742Limited Slow-Start for TCP with Large Congestion WindowsCurrent
March 2004
- RFC 3450Asynchronous Layered Coding (ALC) Protocol InstantiationObsoleted
December 2002
- RFC 3513Internet Protocol Version 6 (IPv6) Addressing ArchitectureObsoleted
April 2003
- RFC 3561Ad hoc On-Demand Distance Vector (AODV) RoutingCurrent
July 2003
- RFC 3292General Switch Management Protocol (GSMP) V3Current
June 2002
- RFC 3265Session Initiation Protocol (SIP)-Specific Event NotificationObsoleted
July 2002
- RFC 3264An Offer/Answer Model with Session Description Protocol (SDP)Updated
July 2002
- RFC 3263Session Initiation Protocol (SIP): Locating SIP ServersUpdated
July 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?