RFC 5033: Specifying New Congestion Control Algorithms
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9743.
Current version: RFC 9743 — Specifying New Congestion Control Algorithms
In plain English — editorial summary, not part of the RFC
The IETF's standard congestion control schemes have been widely shown to be inadequate for various environments (e.g., high-speed networks). Recent research has yielded many alternate congestion control schemes that significantly differ from the IETF's congestion control principles. Using these new congestion control schemes in the global Internet has possible ramifications to both the traffic using the new congestion control and to traffic using the currently standardized congestion control. Therefore, the IETF must proceed with caution when dealing with alternate congestion control proposals. The goal of this document is to provide guidance for considering alternate congestion control algorithms within the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5033
- Published
- August 2007
- Authors
- S. Floyd; M. Allman
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 9743
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 5061Stream Control Transmission Protocol (SCTP) Dynamic Address ReconfigurationCurrent
September 2007
- RFC 5062Security Attacks Found Against the Stream Control Transmission Protocol (SCTP) and Current CountermeasuresCurrent
September 2007
- RFC 4987TCP SYN Flooding Attacks and Common MitigationsCurrent
August 2007
- RFC 5097MIB for the UDP-Lite protocolCurrent
January 2008
- RFC 4960Stream Control Transmission ProtocolObsoleted
September 2007
- RFC 4953Defending TCP Against Spoofing AttacksCurrent
July 2007
- RFC 5127Aggregation of Diffserv Service ClassesCurrent
February 2008
- RFC 5129Explicit Congestion Marking in MPLSUpdated
January 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?