RFC 4341: Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control
In plain English — editorial summary, not part of the RFC
This document contains the profile for Congestion Control Identifier 2 (CCID 2), TCP-like Congestion Control, in the Datagram Congestion Control Protocol (DCCP). CCID 2 should be used by senders who would like to take advantage of the available bandwidth in an environment with rapidly changing conditions, and who are able to adapt to the abrupt changes in the congestion window typical of TCP's Additive Increase Multiplicative Decrease (AIMD) congestion control. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4341
- Published
- March 2006
- Authors
- S. Floyd; E. Kohler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 20
- Also known as
- —
- Updated by:
- RFC 8311
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 4340Datagram Congestion Control Protocol (DCCP)Updated
March 2006
- RFC 4342Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)Updated
April 2006
- RFC 4850Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node ArchitectureObsoleted
April 2007
- RFC 3720Internet Small Computer Systems Interface (iSCSI)Obsoleted
April 2004
- RFC 5238Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP)Updated
May 2008
- RFC 3158RTP Testing StrategiesCurrent
August 2001
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 4336Problem Statement for the Datagram Congestion Control Protocol (DCCP)Current
March 2006
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?