RFC 6323: Sender RTT Estimate Option for the Datagram Congestion Control Protocol (DCCP)
In plain English — editorial summary, not part of the RFC
This document specifies an update to the round-trip time (RTT) estimation algorithm used for TFRC (TCP-Friendly Rate Control) congestion control by the Datagram Congestion Control Protocol (DCCP). It updates specifications for the CCID-3 and CCID-4 Congestion Control IDs of DCCP. The update addresses parameter-estimation problems occurring with TFRC-based DCCP congestion control. It uses a recommendation made in the original TFRC specification to avoid the inherent problems of receiver-based RTT sampling, by utilising higher-accuracy RTT samples already available at the sender. It is integrated into the feature set of DCCP as an end-to-end negotiable extension. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6323
- Published
- July 2011
- Authors
- G. Renker; G. Fairhurst
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- 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 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 3448TCP Friendly Rate Control (TFRC): Protocol SpecificationObsoleted
January 2003
- RFC 9897Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple AddressesCurrent
January 2026
- RFC 6330RaptorQ Forward Error Correction Scheme for Object DeliveryCurrent
August 2011
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?