blob: 74563b38ffd90cdd59a48619fb7a7b46f6ec798a [file] [log] [blame]
Ian McDonald98069ff2005-11-10 13:04:33 -08001DCCP protocol
2============
3
Ian McDonald98069ff2005-11-10 13:04:33 -08004
5Contents
6========
7
8- Introduction
9- Missing features
10- Socket options
11- Notes
12
13Introduction
14============
15
16Datagram Congestion Control Protocol (DCCP) is an unreliable, connection
17based protocol designed to solve issues present in UDP and TCP particularly
18for real time and multimedia traffic.
19
20It has a base protocol and pluggable congestion control IDs (CCIDs).
21
22It is at draft RFC status and the homepage for DCCP as a protocol is at:
23 http://www.icir.org/kohler/dcp/
24
25Missing features
26================
27
28The DCCP implementation does not currently have all the features that are in
29the draft RFC.
30
31In particular the following are missing:
32- CCID2 support
33- feature negotiation
34
35When testing against other implementations it appears that elapsed time
36options are not coded compliant to the specification.
37
38Socket options
39==============
40
41DCCP_SOCKOPT_PACKET_SIZE is used for CCID3 to set default packet size for
42calculations.
43
Gerrit Renker00e4d112006-09-22 09:33:58 +010044DCCP_SOCKOPT_SERVICE sets the service. The specification mandates use of
45service codes (RFC 4340, sec. 8.1.2); if this socket option is not set,
46the socket will fall back to 0 (which means that no meaningful service code
47is present). Connecting sockets set at most one service option; for
48listening sockets, multiple service codes can be specified.
Ian McDonald98069ff2005-11-10 13:04:33 -080049
50Notes
51=====
52
53SELinux does not yet have support for DCCP. You will need to turn it off or
54else you will get EACCES.
55
56DCCP does not travel through NAT successfully at present. This is because
57the checksum covers the psuedo-header as per TCP and UDP. It should be
58relatively trivial to add Linux NAT support for DCCP.