RFC 5622: Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP)
In plain English — editorial summary, not part of the RFC
This document specifies a profile for Congestion Control Identifier 4, the small-packet variant of TCP-Friendly Rate Control (TFRC), in the Datagram Congestion Control Protocol (DCCP). CCID 4 is for experimental use, and uses TFRC-SP (RFC 4828), a variant of TFRC designed for applications that send small packets. CCID 4 is considered experimental because TFRC-SP is itself experimental, and is not proposed for widespread deployment in the global Internet at this time. The goal for TFRC-SP is to achieve roughly the same bandwidth in bits per second (bps) as a TCP flow using packets of up to 1500 bytes but experiencing the same level of congestion. CCID 4 is for use for senders that send small packets and would like a TCP- friendly sending rate, possibly with Explicit Congestion Notification (ECN), while minimizing abrupt rate changes. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5622
- Published
- August 2009
- Authors
- S. Floyd; E. Kohler
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 19
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5634Quick-Start for the Datagram Congestion Control Protocol (DCCP)Current
August 2009
- RFC 5597Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control ProtocolCurrent
September 2009
- RFC 5596Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox TraversalCurrent
September 2009
- RFC 5595The Datagram Congestion Control Protocol (DCCP) Service CodesUpdated
September 2009
- RFC 5651Layered Coding Transport (LCT) Building BlockCurrent
October 2009
- RFC 5670Metering and Marking Behaviour of PCN-NodesCurrent
November 2009
- RFC 5559Pre-Congestion Notification (PCN) ArchitectureCurrent
June 2009
- RFC 5696Baseline Encoding and Transport of Pre-Congestion InformationObsoleted
November 2009
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?