From: Eddie Kohler <kohler@cs.ucla.edu>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 8/9] [DCCP]: Update Documentation
Date: Wed, 22 Nov 2006 04:29:59 +0000 [thread overview]
Message-ID: <4563D247.6090508@cs.ucla.edu> (raw)
In-Reply-To: <20061120205748.GI5246@mandriva.com>
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.
next prev parent reply other threads:[~2006-11-22 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 20:57 [PATCH 8/9] [DCCP]: Update Documentation Arnaldo Carvalho de Melo
2006-11-22 4:29 ` Eddie Kohler [this message]
2006-12-08 1:26 ` Ian McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4563D247.6090508@cs.ucla.edu \
--to=kohler@cs.ucla.edu \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.