summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorIan McDonald <ian.mcdonald@jandi.co.nz>2006-11-20 18:42:45 -0200
committerDavid S. Miller <davem@sunset.davemloft.net>2006-12-02 21:24:40 -0800
commitddfe10b82455a5a524055fc606d1f1562d388dc8 (patch)
tree7e8ab2fc61890646457c7263c221c2249052bba5 /Documentation
parente1b7441e803442828780a6d6d792643f79d5665b (diff)
downloadlinux-3.10-ddfe10b82455a5a524055fc606d1f1562d388dc8.tar.gz
linux-3.10-ddfe10b82455a5a524055fc606d1f1562d388dc8.tar.bz2
linux-3.10-ddfe10b82455a5a524055fc606d1f1562d388dc8.zip
[DCCP]: Update Documentation
This patch just updates DCCP documentation a bit. Signed-off-by: Ian McDonald <ian.mcdonald@jandi.co.nz> Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/networking/dccp.txt23
1 files changed, 8 insertions, 15 deletions
diff --git a/Documentation/networking/dccp.txt b/Documentation/networking/dccp.txt
index c2328c862e9..1910d097a0a 100644
--- a/Documentation/networking/dccp.txt
+++ b/Documentation/networking/dccp.txt
@@ -19,21 +19,17 @@ for real time and multimedia traffic.
It has a base protocol and pluggable congestion control IDs (CCIDs).
-It is at draft RFC status and the homepage for DCCP as a protocol is at:
- http://www.icir.org/kohler/dcp/
+It is at experimental RFC status and the homepage for DCCP as a protocol is at:
+ http://www.read.cs.ucla.edu/dccp/
Missing features
================
The DCCP implementation does not currently have all the features that are in
-the draft RFC.
+the RFC.
-In particular the following are missing:
-- CCID2 support
-- feature negotiation
-
-When testing against other implementations it appears that elapsed time
-options are not coded compliant to the specification.
+The known bugs are at:
+ http://linux-net.osdl.org/index.php/TODO#DCCP
Socket options
==============
@@ -107,9 +103,6 @@ seq_window = 100
Notes
=====
-SELinux does not yet have support for DCCP. You will need to turn it off or
-else you will get EACCES.
-
-DCCP does not travel through NAT successfully at present. This is because
-the checksum covers the psuedo-header as per TCP and UDP. It should be
-relatively trivial to add Linux NAT support for DCCP.
+DCCP does not travel through NAT successfully at present on many boxes. This is
+because the checksum covers the psuedo-header as per TCP and UDP. Linux NAT
+support for DCCP has been added.