Commit ddfe10b8 authored by Ian McDonald's avatar Ian McDonald Committed by David S. Miller

[DCCP]: Update Documentation

This patch just updates DCCP documentation a bit.
Signed-off-by: default avatarIan McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: default avatarArnaldo Carvalho de Melo <acme@mandriva.com>
parent e1b7441e
...@@ -19,21 +19,17 @@ for real time and multimedia traffic. ...@@ -19,21 +19,17 @@ for real time and multimedia traffic.
It has a base protocol and pluggable congestion control IDs (CCIDs). 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: It is at experimental RFC status and the homepage for DCCP as a protocol is at:
http://www.icir.org/kohler/dcp/ http://www.read.cs.ucla.edu/dccp/
Missing features Missing features
================ ================
The DCCP implementation does not currently have all the features that are in The DCCP implementation does not currently have all the features that are in
the draft RFC. the RFC.
In particular the following are missing: The known bugs are at:
- CCID2 support http://linux-net.osdl.org/index.php/TODO#DCCP
- feature negotiation
When testing against other implementations it appears that elapsed time
options are not coded compliant to the specification.
Socket options Socket options
============== ==============
...@@ -107,9 +103,6 @@ seq_window = 100 ...@@ -107,9 +103,6 @@ seq_window = 100
Notes Notes
===== =====
SELinux does not yet have support for DCCP. You will need to turn it off or DCCP does not travel through NAT successfully at present on many boxes. This is
else you will get EACCES. because the checksum covers the psuedo-header as per TCP and UDP. Linux NAT
support for DCCP has been added.
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.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment