RFC 6937: Proportional Rate Reduction for TCP
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9937.
Current version: RFC 9937 — Proportional Rate Reduction (PRR)
In plain English — editorial summary, not part of the RFC
This document describes an experimental Proportional Rate Reduction (PRR) algorithm as an alternative to the widely deployed Fast Recovery and Rate-Halving algorithms. These algorithms determine the amount of data sent by TCP during loss recovery. PRR minimizes excess window adjustments, and the actual window size at the end of recovery will be as close as possible to the ssthresh, as determined by the congestion control algorithm.
Document record
- Document ID
- RFC6937
- Published
- May 2013
- Authors
- M. Mathis; N. Dukkipati; Y. Cheng
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 16
- Also known as
- —
- Obsoleted by:
- RFC 9937
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 6928Increasing TCP's Initial WindowCurrent
April 2013
- RFC 6951UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host CommunicationUpdated
May 2013
- RFC 6904Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)Current
April 2013
- RFC 6994Shared Use of Experimental TCP OptionsCurrent
August 2013
- RFC 7007Update to Remove DVI4 from the Recommended Codecs for the RTP Profile for Audio and Video Conferences with Minimal Control (RTP/AVP)Current
August 2013
- RFC 7022Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)Current
September 2013
- RFC 7053SACK-IMMEDIATELY Extension for the Stream Control Transmission ProtocolObsoleted
November 2013
- RFC 6792Guidelines for Use of the RTP Monitoring FrameworkCurrent
November 2012
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?