Introduction¶

Datagram Congestion Control Protocol (DCCP) is an unreliable, connectionoriented protocol designed to solve issues present in UDP and TCP, particularlyfor real-time and multimedia (streaming) traffic.It divides into a base protocol (RFC 4340) and pluggable congestion controlmodules called CCIDs. Like pluggable TCP congestion control, at least one CCIDneeds to be enabled in order for the protocol to function properly. In the Linuximplementation, this is the TCP-like CCID2 (RFC 4341). Additional CCIDs, such asthe TCP-friendly CCID3 (RFC 4342), are optional.For a brief introduction to CCIDs and suggestions for choosing a CCID to matchgiven applications, see section 10 of RFC 4340.

It has a base protocol and pluggable congestion control IDs (CCIDs).

DCCP is a Proposed Standard (RFC 2026), and the homepage for DCCP as a protocolis athttp://www.ietf.org/html.charters/dccp-charter.html

Missing features¶

The Linux DCCP implementation does not currently support all the features that arespecified in RFCs 4340…42.

The known bugs are at:

http://www.linuxfoundation.org/collaborate/workgroups/networking/todo#DCCP

For more up-to-date versions of the DCCP implementation, please consider usingthe experimental DCCP test tree; instructions for checking this out are on:http://www.linuxfoundation.org/collaborate/workgroups/networking/dccp_testing#Experimental_DCCP_source_tree

Socket options¶

DCCP_SOCKOPT_QPOLICY_ID sets the dequeuing policy for outgoing packets. It takesa policy ID as argument and can only be set before the connection (i.e. changesduring an established connection are not supported). Currently, two policies aredefined: the “simple” policy (DCCPQ_POLICY_SIMPLE), which does nothing special,and a priority-based variant (DCCPQ_POLICY_PRIO). The latter allows to pass anu32 priority value as ancillary data to sendmsg(), where higher numbers indicatea higher packet priority (similar to SO_PRIORITY). This ancillary data needs tobe formatted using a cmsg(3) message header filled in as follows:

cmsg->cmsg_level = SOL_DCCP;cmsg->cmsg_type  = DCCP_SCM_PRIORITY;cmsg->cmsg_len   = CMSG_LEN(sizeof(uint32_t));  /* or CMSG_LEN(4) */

DCCP_SOCKOPT_QPOLICY_TXQLEN sets the maximum length of the output queue. A zerovalue is always interpreted as unbounded queue length. If different from zero,the interpretation of this parameter depends on the current dequeuing policy(see above): the “simple” policy will enforce a fixed queue size by returningEAGAIN, whereas the “prio” policy enforces a fixed queue length by dropping thelowest-priority packet first. The default value for this parameter isinitialised from /proc/sys/net/dccp/default/tx_qlen.

DCCP_SOCKOPT_SERVICE sets the service. The specification mandates use ofservice codes (RFC 4340, sec. 8.1.2); if this socket option is not set,the socket will fall back to 0 (which means that no meaningful service codeis present). On active sockets this is set before connect(); specifying morethan one code has no effect (all subsequent service codes are ignored). Thecase is different for passive sockets, where multiple service codes (up to 32)can be set before calling bind().

DCCP_SOCKOPT_GET_CUR_MPS is read-only and retrieves the current maximum packetsize (application payload size) in bytes, see RFC 4340, section 14.

DCCP_SOCKOPT_AVAILABLE_CCIDS is also read-only and returns the list of CCIDssupported by the endpoint. The option value is an array of type uint8_t whosesize is passed as option length. The minimum array size is 4 elements, thevalue returned in the optlen argument always reflects the true number ofbuilt-in CCIDs.

DCCP_SOCKOPT_CCID is write-only and sets both the TX and RX CCIDs at the sametime, combining the operation of the next two socket options. This option ispreferable over the latter two, since often applications will use the sametype of CCID for both directions; and mixed use of CCIDs is not currently wellunderstood. This socket option takes as argument at least one uint8_t value, oran array of uint8_t values, which must match available CCIDS (see above). CCIDsmust be registered on the socket before calling connect() or listen().

DCCP_SOCKOPT_TX_CCID is read/write. It returns the current CCID (if set) or setsthe preference list for the TX CCID, using the same format as DCCP_SOCKOPT_CCID.Please note that the getsockopt argument type here isint, not uint8_t.

DCCP_SOCKOPT_RX_CCID is analogous to DCCP_SOCKOPT_TX_CCID, but for the RX CCID.

DCCP_SOCKOPT_SERVER_TIMEWAIT enables the server (listening socket) to holdtimewait state when closing the connection (RFC 4340, 8.3). The usual case isthat the closing server sends a CloseReq, whereupon the client holds timewaitstate. When this boolean socket option is on, the server sends a Close insteadand will enter TIMEWAIT. This option must be set after accept() returns.

DCCP_SOCKOPT_SEND_CSCOV and DCCP_SOCKOPT_RECV_CSCOV are used for setting thepartial checksum coverage (RFC 4340, sec. 9.2). The default is that checksumsalways cover the entire packet and that only fully covered application data isaccepted by the receiver. Hence, when using this feature on the sender, it mustbe enabled at the receiver, too with suitable choice of CsCov.

DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the

range 0..15 are acceptable. The default setting is 0 (full coverage),values between 1..15 indicate partial coverage.

DCCP_SOCKOPT_RECV_CSCOV is for the receiver and has a different meaning: it

sets a threshold, where again values 0..15 are acceptable. The defaultof 0 means that all packets with a partial coverage will be discarded.Values in the range 1..15 indicate that packets with minimally such acoverage value are also acceptable. The higher the number, the morerestrictive this setting (see [RFC 4340, sec. 9.2.1]). Partial coveragesettings are inherited to the child socket after accept().

The following two options apply to CCID 3 exclusively and are getsockopt()-only.In either case, a TFRC info struct (defined in <linux/tfrc.h>) is returned.

DCCP_SOCKOPT_CCID_RX_INFO

Returns astructtfrc_rx_info in optval; the buffer for optval andoptlen must be set to at least sizeof(struct tfrc_rx_info).

DCCP_SOCKOPT_CCID_TX_INFO

Returns astructtfrc_tx_info in optval; the buffer for optval andoptlen must be set to at least sizeof(struct tfrc_tx_info).

On unidirectional connections it is useful to close the unused half-connectionvia shutdown (SHUT_WR or SHUT_RD): this will reduce per-packet processing costs.

Sysctl variables¶

Several DCCP default parameters can be managed by the following sysctls(sysctl net.dccp.default or /proc/sys/net/dccp/default):

request_retries

The number of active connection initiation retries (the number ofRequests minus one) before timing out. In addition, it also governsthe behaviour of the other, passive side: this variable also setsthe number of times DCCP repeats sending a Response when the initialhandshake does not progress from RESPOND to OPEN (i.e. when no Ackis received after the initial Request). This value should be greaterthan 0, suggested is less than 10. Analogue of tcp_syn_retries.

retries1

How often a DCCP Response is retransmitted until the listening DCCPside considers its connecting peer dead. Analogue of tcp_retries1.

retries2

The number of times a general DCCP packet is retransmitted. This hasimportance for retransmitted acknowledgments and feature negotiation,data packets are never retransmitted. Analogue of tcp_retries2.

tx_ccid = 2

Default CCID for the sender-receiver half-connection. Depending on thechoice of CCID, the Send Ack Vector feature is enabled automatically.

rx_ccid = 2

Default CCID for the receiver-sender half-connection; see tx_ccid.

seq_window = 100

The initial sequence window (sec. 7.5.2) of the sender. This influencesthe local ackno validity and the remote seqno validity windows (7.5.1).Values in the range Wmin = 32 (RFC 4340, 7.5.2) up to 2^32-1 can be set.

tx_qlen = 5

The size of the transmit buffer in packets. A value of 0 correspondsto an unbounded transmit buffer.

sync_ratelimit = 125 ms

The timeout between subsequent DCCP-Sync packets sent in response tosequence-invalid packets on the same socket (RFC 4340, 7.5.4). The unitof this parameter is milliseconds; a value of 0 disables rate-limiting.

IOCTLS¶

FIONREAD

Works as in udp(7): returns in theint argument pointer the size ofthe next pending datagram in bytes, or 0 when no datagram is pending.

SIOCOUTQ

Returns the number of unsent data bytes in the socket send queue asintinto the buffer specified by the argument pointer.

Other tunables¶

Per-route rto_min support

CCID-2 supports the RTAX_RTO_MIN per-route setting for the minimum valueof the RTO timer. This setting can be modified via the ‘rto_min’ optionof iproute2; for example:

> ip route change 10.0.0.0/24   rto_min 250j dev wlan0> ip route add    10.0.0.254/32 rto_min 800j dev wlan0> ip route show dev wlan0

CCID-3 also supports the rto_min setting: it is used to define the lowerbound for the expiry of the nofeedback timer. This can be useful on LANswith very low RTTs (e.g., loopback, Gbit ethernet).

Notes¶

DCCP does not travel through NAT successfully at present on many boxes. This isbecause the checksum covers the pseudo-header as per TCP and UDP. Linux NATsupport for DCCP has been added.