In computer networking, the Datagram Congestion Control Protocol (DCCP) is a message-oriented transport layer protocol. DCCP implements reliable connection setup, teardown, Explicit Congestion Notification (ECN), congestion control, and feature negotiation. The IETF published DCCP as, a proposed standard, in March 2006. provides an introduction.
DCCP provides a way to gain access to congestion-control mechanisms without having to implement them at the application layer. It allows for flow-based semantics like in Transmission Control Protocol (TCP), but does not provide reliable in-order delivery. Sequenced delivery within multiple streams as in the Stream Control Transmission Protocol (SCTP) is not available in DCCP. A DCCP connection contains acknowledgment traffic as well as data traffic. Acknowledgments inform a sender whether its packets have arrived, and whether they were marked by Explicit Congestion Notification (ECN). Acknowledgements are transmitted as reliably as the congestion control mechanism in use requires, possibly completely reliably.
DCCP has the option for very long (48-bit) sequence numbers corresponding to a packet ID, rather than a byte ID as in TCP. The long length of the sequence numbers aims to guard against "some blind attacks, such as the injection of DCCP-Resets into the connection".[1]
DCCP is useful for applications with timing constraints on the delivery of data. Such applications include streaming media, multiplayer online games and Internet telephony. In such applications, old messages quickly become useless, so that getting new messages is preferred to resending lost messages. such applications have often either settled for TCP or used User Datagram Protocol (UDP) and implemented their own congestion-control mechanisms, or have no congestion control at all. While being useful for these applications, DCCP can also serve as a general congestion-control mechanism for UDP-based applications, by adding, as needed, mechanisms for reliable or in-order delivery on top of UDP/DCCP. In this context, DCCP allows the use of different, but generally TCP-friendly congestion-control mechanisms.
The following operating systems implement DCCP:
Userspace library:
The DCCP generic header takes different forms depending on the value of X, the Extended Sequence Numbers bit. If X is one, the Sequence Number field is 48 bits long, and the generic header takes 16 bytes, as follows.
| Offsets | Octet | 0 | 1 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Octet | Bit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | |
| 0 | 0 | Source port | ||||||||||||||||
| 2 | 16 | Destination port | ||||||||||||||||
| 4 | 32 | Data Offset | CCVal | CsCov | ||||||||||||||
| 6 | 48 | Checksum | ||||||||||||||||
| 8 | 64 | Res | Type | X=1 | Reserved | |||||||||||||
| 10 | 80 | Sequence Number (high bits) | ||||||||||||||||
| 12 | 96 | Sequence Number | ||||||||||||||||
| 14 | 112 | Sequence Number (low bits) | ||||||||||||||||
If X is zero, only the low 24 bits of the Sequence Number are transmitted, and the generic header is 12 bytes long.
| Offsets | Octet | 0 | 1 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Octet | Bit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | |
| 0 | 0 | Source port | ||||||||||||||||
| 2 | 16 | Destination port | ||||||||||||||||
| 4 | 32 | Data Offset | CCVal | CsCov | ||||||||||||||
| 6 | 48 | Checksum | ||||||||||||||||
| 8 | 64 | Res | Type | X=0 | Sequence Number (high) | |||||||||||||
| 10 | 80 | Sequence Number (low bits) | ||||||||||||||||
Similarly to the extension of TCP protocol by multipath capability (MPTCP) also for DCCP the multipath feature is under discussion at IETF [6] correspondingly denoted as MP-DCCP. First implementations have already been developed, tested, and presented in a collaborative approach between operators and academia [7] and are available as an open source solution.