* [PATCH 8/9] [DCCP]: Update Documentation
@ 2006-11-20 20:57 Arnaldo Carvalho de Melo
2006-11-22 4:29 ` Eddie Kohler
2006-12-08 1:26 ` Ian McDonald
0 siblings, 2 replies; 3+ messages in thread
From: Arnaldo Carvalho de Melo @ 2006-11-20 20:57 UTC (permalink / raw)
To: dccp
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>
---
Documentation/networking/dccp.txt | 23 ++++++++---------------
1 files changed, 8 insertions(+), 15 deletions(-)
diff --git a/Documentation/networking/dccp.txt b/Documentation/networking/dccp.txt
index c2328c8..1910d09 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.
--
1.4.2.1.g3d5c
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 8/9] [DCCP]: Update Documentation
2006-11-20 20:57 [PATCH 8/9] [DCCP]: Update Documentation Arnaldo Carvalho de Melo
@ 2006-11-22 4:29 ` Eddie Kohler
2006-12-08 1:26 ` Ian McDonald
1 sibling, 0 replies; 3+ messages in thread
From: Eddie Kohler @ 2006-11-22 4:29 UTC (permalink / raw)
To: dccp
Hi Arnaldo, Ian,
Actually, DCCP's status is Proposed Standard. FYI.
Eddie
Arnaldo Carvalho de Melo wrote:
> 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>
> ---
> Documentation/networking/dccp.txt | 23 ++++++++---------------
> 1 files changed, 8 insertions(+), 15 deletions(-)
>
> diff --git a/Documentation/networking/dccp.txt b/Documentation/networking/dccp.txt
> index c2328c8..1910d09 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 8/9] [DCCP]: Update Documentation
2006-11-20 20:57 [PATCH 8/9] [DCCP]: Update Documentation Arnaldo Carvalho de Melo
2006-11-22 4:29 ` Eddie Kohler
@ 2006-12-08 1:26 ` Ian McDonald
1 sibling, 0 replies; 3+ messages in thread
From: Ian McDonald @ 2006-12-08 1:26 UTC (permalink / raw)
To: dccp
On 11/22/06, Eddie Kohler <kohler@cs.ucla.edu> wrote:
> Hi Arnaldo, Ian,
>
> Actually, DCCP's status is Proposed Standard. FYI.
>
> Eddie
>
New patch just sent.
Sorry about the delay.
Ian
--
Web: http://wand.net.nz/~iam4
Blog: http://imcdnzl.blogspot.com
WAND Network Research Group
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-12-08 1:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-20 20:57 [PATCH 8/9] [DCCP]: Update Documentation Arnaldo Carvalho de Melo
2006-11-22 4:29 ` Eddie Kohler
2006-12-08 1:26 ` Ian McDonald
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox