Problem Statement for the Datagram Congestion Control Protocol (DCCP)

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 22
Abstract: This document describes for the historical record the motivation behind the Datagram Congestion Control Protocol (DCCP), an unreliable transport protocol incorporating end-to-end congestion control. DCCP implements a congestion-controlled, unreliable flow of datagrams for use by applications such as streaming media or on-line games. This memo provides information for the Internet community.
Publication Date: 2006-03-01
Status Note: Informational
DOI: 10.17487/RFC4336
Link: https://doi.org/10.17487/RFC4336
Author(s): Sally Floyd
Mark J. Handley
Eddie Kohler

Latest version of IETF RFC 4336

Document Versions — IETF RFC 4336

▶ IETF RFC 4336 (2006-03-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

Padhye, J. and S. Floyd, "Identifying the TCP Behavior of Web Servers", SIGCOMM 2001. EXTERNAL
Requirements for Unicast Transport/Sessions (RUTS) BOF, Dec. 7, 1998. URL " http://www.ietf.org/proceedings/98dec/43rd-ietf- 98dec-142.html ". EXTERNAL
Floyd, S. and K. Fall, "Promoting the Use of End-to- End Congestion Control in the Internet", IEEE/ACM Transactions on Networking, August 1999. EXTERNAL
Balakrishnan, H., Rahul, H., and S. Seshan, "An Integrated Congestion Management Architecture for Internet Hosts", SIGCOMM, Sept. 1999. EXTERNAL
IETF RFC 2309 [Superseded*]
IETF RFC 2326 [Superseded*]
IETF RFC 2525 [Active*]
IETF RFC 2914 [Active*]
IETF RFC 2960 [Superseded*]
IETF RFC 3124 [Active*]
IETF RFC 3168 [Active*]
IETF RFC 3261 [Active*]
IETF RFC 3448 [Superseded*]
IETF RFC 3540 [Active*]
IETF RFC 3714 [Active*]
IETF RFC 3758 [Active*]
IETF RFC 4340 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4336.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 4336, Problem Statement for the Datagram Congestion Control Protocol (DCCP). Available at https://doi.org/10.17487/RFC4336

Snippet:

IETF RFC 4336, Problem Statement for the Datagram Congestion Control Protocol (DCCP). Available at https://doi.org/10.17487/RFC4336

HTML (ISO 690 compliant)

Preview:

IETF RFC 4336, Problem Statement for the Datagram Congestion Control Protocol (DCCP). Available at https://doi.org/10.17487/RFC4336

Snippet:

<span class="citation"><cite>IETF RFC 4336</cite>, Problem Statement for the Datagram Congestion Control Protocol (DCCP). Available at <a href="https://doi.org/10.17487/RFC4336" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4336</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 4336, Problem Statement for the Datagram Congestion Control Protocol (DCCP)
doi: 10.17487/RFC4336
url: https://doi.org/10.17487/RFC4336

Snippet:

<li>
<cite id="bib-rfc4336">IETF RFC 4336</cite>, Problem Statement for the Datagram Congestion Control Protocol (DCCP)
<span class="doi">10.17487/RFC4336</span>
</li>

Referenced By

IETF draft-bormann-core-congestion-control-02 [Active*]
IETF RFC 5783 [Active*]