RFC 8312: CUBIC for Fast Long-Distance Networks
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9438.
Current version: RFC 9438 — CUBIC for Fast and Long-Distance Networks
In plain English — editorial summary, not part of the RFC
CUBIC is an extension to the current TCP standards. It differs from the current TCP standards only in the congestion control algorithm on the sender side. In particular, it uses a cubic function instead of a linear window increase function of the current TCP standards to improve scalability and stability under fast and long-distance networks. CUBIC and its predecessor algorithm have been adopted as defaults by Linux and have been used for many years. This document provides a specification of CUBIC to enable third-party implementations and to solicit community feedback through experimentation on the performance of CUBIC.
Document record
- Document ID
- RFC8312
- Published
- February 2018
- Authors
- I. Rhee; L. Xu; S. Ha; A. Zimmermann; L. Eggert; R. Scheffenegger
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 18
- Also known as
- —
- Obsoleted by:
- RFC 9438
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 8311Relaxing Restrictions on Explicit Congestion Notification (ECN) ExperimentationCurrent
January 2018
- RFC 8304Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)Current
February 2018
- RFC 8303On the Usage of Transport Features Provided by IETF Transport ProtocolsCurrent
February 2018
- RFC 8323CoAP (Constrained Application Protocol) over TCP, TLS, and WebSocketsUpdated
February 2018
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 8297An HTTP Status Code for Indicating HintsCurrent
December 2017
- RFC 8336The ORIGIN HTTP/2 FrameCurrent
March 2018
- RFC 8285A General Mechanism for RTP Header ExtensionsCurrent
October 2017
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?