RFC 2914: Congestion Control Principles
In plain English — editorial summary, not part of the RFC
The goal of this document is to explain the need for congestion control in the Internet, and to discuss what constitutes correct congestion control. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2914
- Published
- September 2000
- Authors
- S. Floyd
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 17
- Also known as
- BCP41
- Updated by:
- RFC 7141
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 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 3102Realm Specific IP: FrameworkCurrent
October 2001
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
- RFC 1932IP over ATM: A Framework DocumentCurrent
April 1996
- RFC 1890RTP Profile for Audio and Video Conferences with Minimal ControlObsoleted
January 1996
- RFC 1889RTP: A Transport Protocol for Real-Time ApplicationsObsoleted
January 1996
- RFC 5197On the Applicability of Various Multimedia Internet KEYing (MIKEY) Modes and ExtensionsCurrent
June 2008
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?