Skip to contentSkip to conversation

: Update Documentation

PATCH In review Arnaldo Carvalho de Melo 3 participants 3 messages Nov 20, 2006 – Dec 8, 2006

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 8/9 : Update Documentation

This patch just updates DCCP documentation a bit.

---
 Documentation/networking/dccp.txt |   23 ++++++++---------------
 1 files changed, 8 insertions(+), 15 deletions(-)
Documentation/networking/dccp.txt +8 -15
index c2328c8..1910d09 100644
@@ -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.
Signature · 1 line
1.4.2.1.g3d5c
#1 lore raw

Hi Arnaldo, Ian,

Actually, DCCP's status is Proposed Standard. FYI.

Eddie

Quoted 51 lines · Arnaldo Carvalho de Melo

This patch just updates DCCP documentation a bit.

---
 Documentation/networking/dccp.txt |   23 ++++++++---------------
 1 files changed, 8 insertions(+), 15 deletions(-)
Documentation/networking/dccp.txt +8 -15
index c2328c8..1910d09 100644
@@ -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.
#2 lore raw
In reply to Arnaldo Carvalho de Melo
Quoted 6 lines · Eddie Kohler

Hi Arnaldo, Ian,

Actually, DCCP's status is Proposed Standard. FYI.

Eddie

New patch just sent.

Sorry about the delay.

Ian

Signature · 3 lines
Web: http://wand.net.nz/~iam4
Blog: http://imcdnzl.blogspot.com
WAND Network Research Group