From: Daniel Borkmann <dborkman@redhat.com>
To: linux-sctp@vger.kernel.org
Subject: Re: SCTP Compliance
Date: Thu, 01 Jan 2015 13:23:04 +0000 [thread overview]
Message-ID: <54A54A38.7000402@redhat.com> (raw)
Hi Peter,
On 12/15/2014 10:26 PM, Butler, Peter wrote:
> I am looking for a formal LKSCTP compliance statement. Is there one?
You may want to try out [1] for a partial answer to your question.
The test cases are mostly related to RFC4960 itself, though. Other
than that, RFC3758 is not yet implemented, the rest certainly has
some form of implementation in the stack, but a formal 100%-compliance
statement wrt the RFC, I cannot tell/make right now.
Thanks,
Daniel
> Is LKSCTP 100% compliant with the following?
>
> RFC 2960 - SCTP (obsoleted by RFC 4960)
> RFC 3309 - SCTP Checksum Change (obsoleted by RFC 4960)
> RFC 3758 - SCTP Partial Reliability Extension
> RFC 3873 - SCTP MIB
> RFC 4460 - SCTP Errata and Issues
> RFC 4895 - Authenticated Chunks for SCTP
> RFC 4960 - SCTP
> RFC 5061 - SCTP Dynamic Address Reconfiguration
> RFC 5062 - Security Attacks Against SCTP
[1] http://networktest.sourceforge.net/overview.html
next reply other threads:[~2015-01-01 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 13:23 Daniel Borkmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-15 21:26 SCTP Compliance Butler, Peter
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=54A54A38.7000402@redhat.com \
--to=dborkman@redhat.com \
--cc=linux-sctp@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.