Datagram Congestion Control Protocol (DCCP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 129
- Abstract
- The Datagram Congestion Control Protocol (DCCP) is a transport protocol that provides bidirectional unicast connections of congestion-controlled unreliable datagrams. DCCP is suitable for applications that transfer fairly large amounts of data and that can benefit from control over the tradeoff between timeliness and reliability. [STANDARDS-TRACK]
- Publication Date
- 2006-03-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4340- Link
- https://doi.org/10.17487/RFC4340
- Author(s)
- Eddie KohlerMark J. HandleySally Floyd
Latest version of IETF RFC 4340
Document Versions — IETF RFC 4340
-
▶ IETF RFC 4340 (2006-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- IETF RFC 5595 [Active*]
- RFC5596 — RFC5596 EXTERNAL
- IETF RFC 6335 [Active*]
- RFC6773 — RFC6773 EXTERNAL
Normative Reference(s)
- IETF RFC 793 [Superseded*]
- IETF RFC 1191 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2434 [Superseded*]
- IETF RFC 2460 [Superseded*]
- IETF RFC 3168 [Active*]
- IETF RFC 3309 [Superseded*]
- IETF RFC 3692 [Active*]
- IETF RFC 3775 [Superseded*]
- IETF RFC 3828 [Active*]
Bibliographic Reference(s)
- Bellovin, S.M. and M. Blaze, "Cryptographic Modes of Operation for the Internet", 2nd NIST Workshop on Modes of Operation, August 2001. EXTERNAL
- Morris, R.T., "A Weakness in the 4.2BSD Unix TCP/IP Software", Computer Science Technical Report 117, AT&T Bell Laboratories, Murray Hill, NJ, February 1985. EXTERNAL
- Mathis, M. and J. Heffner, "Path MTU Discovery" , Work in Progress, March 2006. EXTERNAL
- Bellovin, S.M., "Cryptography and the Internet", CRYPTO '98 (LNCS 1462), pp 46-55, August 1988. EXTERNAL
- Vanit-Anunchai, S., Billington, J., and T. Kongprakaiwoot, "Discovering Chatter and Incompleteness in the Datagram Congestion Control Protocol", FORTE 2005, pp 143-158, October 2005. EXTERNAL
- Bernstein, D.J., "SYN Cookies", http://cr.yp.to/syncookies.html , as of March 2006. EXTERNAL
- Spatscheck, O., Hansen, J.S., Hartman, J.H., and L.L. Peterson, "Optimizing TCP Forwarder Performance", IEEE/ACM Transactions on Networking 8(2):146-157, April 2000. EXTERNAL
- IETF RFC 792 [Active*]
- IETF RFC 1812 [Active*]
- IETF RFC 1948 [Superseded*]
- IETF RFC 1982 [Active*]
- IETF RFC 2018 [Active*]
- IETF RFC 2401 [Superseded*]
- IETF RFC 2463 [Superseded*]
- IETF RFC 2581 [Superseded*]
- IETF RFC 2960 [Superseded*]
- IETF RFC 3124 [Active*]
- IETF RFC 3360 [Active*]
- IETF RFC 3448 [Superseded*]
- IETF RFC 3540 [Active*]
- IETF RFC 3550 [Active*]
- IETF RFC 3611 [Active*]
- IETF RFC 3711 [Active*]
- IETF RFC 3819 [Active*]
- IETF RFC 4086 [Active*]
- IETF RFC 4341 [Active*]
- IETF RFC 4342 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4340.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4340, Datagram Congestion Control Protocol (DCCP). Available at https://doi.org/10.17487/RFC4340
Snippet:
IETF RFC 4340, Datagram Congestion Control Protocol (DCCP). Available at https://doi.org/10.17487/RFC4340
HTML (ISO 690 compliant)
Preview:
IETF RFC 4340, Datagram Congestion Control Protocol (DCCP). Available at https://doi.org/10.17487/RFC4340
Snippet:
<span class="citation"><cite>IETF RFC 4340</cite>, Datagram Congestion Control Protocol (DCCP). Available at <a href="https://doi.org/10.17487/RFC4340" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4340</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4340, Datagram Congestion Control Protocol (DCCP)
doi: 10.17487/RFC4340
url: https://doi.org/10.17487/RFC4340
doi: 10.17487/RFC4340
url: https://doi.org/10.17487/RFC4340
Snippet:
<li> <cite id="bib-rfc4340">IETF RFC 4340</cite>, Datagram Congestion Control Protocol (DCCP) <span class="doi">10.17487/RFC4340</span> </li>
Referenced By
- IETF RFC 4341 [Active*]
- IETF RFC 4342 [Active*]
- IETF RFC 4774 [Active*]
- IETF RFC 4821 [Active*]
- IETF RFC 5129 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5238 [Active*]
- IETF RFC 5348 [Active*]
- IETF RFC 5405 [Superseded*]
- IETF RFC 5595 [Active*]
- IETF RFC 6012 [Active*]
- IETF RFC 6021 [Superseded*]
- IETF RFC 6335 [Active*]
- IETF RFC 6347 [Superseded*]
- IETF RFC 6763 [Active*]
- IETF RFC 6991 [Superseded*]
- IETF RFC 8085 [Active*]
- IETF RFC 8126 [Active*]
- SMPTE ST 2022-1:2007 [Active]