linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sonia bhattacharya <soniaruby1@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Regarding kernel SCTP module compliance to 4960
Date: Tue, 04 Aug 2020 02:40:51 +0000	[thread overview]
Message-ID: <CAMyZL9o14WtFT5+MfS4qWOpzSHLiX21vSLn0795Z-_mi4hGLyQ@mail.gmail.com> (raw)
In-Reply-To: <CAMyZL9pE+343HvMHuci=+2aKS4HrtuL2GJ2oVwxw7PfL7=doKQ@mail.gmail.com>

Hi Marcelo,

We are using Ubuntu 18.04 with the following kernel version.
esi14-vm-23u:~$ uname -r
5.0.0-23-generic

Just to confirm, the modinfo sctp shows the following:
esi14-vm-23u:~$ modinfo sctp
filename:       /lib/modules/5.0.0-23-generic/kernel/net/sctp/sctp.ko
license:        GPL
description:    Support for the SCTP protocol (RFC2960)
author:         Linux Kernel SCTP developers <linux-sctp@vger.kernel.org>
alias:          net-pf-10-proto-132
alias:          net-pf-2-proto-132
srcversion:     5CD1A15EE663D4E98EAC641
depends:        libcrc32c
retpoline:      Y
intree:         Y
name:           sctp
vermagic:       5.0.0-23-generic SMP mod_unload
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4
parm:           no_checksums:Disable checksums computing and verification (bool)

Kindly confirm that this is compliant to 4960 already. If that is the
case, then it would be great if atleast the description in modinfo
shows 4960.


Regards,
Sonia


On Mon, Aug 3, 2020 at 11:12 PM Marcelo Ricardo Leitner
<marcelo.leitner@gmail.com> wrote:
>
> On Mon, Aug 03, 2020 at 03:53:35PM +0530, sonia bhattacharya wrote:
> > Hi Team,
> >
> >
> >
> > Is there a plan to upgrade the linux SCTP kernel module to be
> > compliant to RFC 4960?
> >
> > Right now, it is compliant to RFC 2960.
> >
> >
> > description:    Support for the SCTP protocol (RFC2960)
>
> Hi Sonia,
>
> There are several references to old RFCs throughout the code, just
> because they weren't updated to the newer versions. But in regards to
> your question, Linux SCTP kernel code is compliant to RFC4960 already.
> If you notice anything particular missing, it's a bug. :-)
>
> Thanks,
> Marcelo

      parent reply	other threads:[~2020-08-04  2:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 10:35 Regarding kernel SCTP module compliance to 4960 sonia bhattacharya
2020-08-03 17:42 ` Marcelo Ricardo Leitner
2020-08-04  2:40 ` sonia bhattacharya [this message]

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=CAMyZL9o14WtFT5+MfS4qWOpzSHLiX21vSLn0795Z-_mi4hGLyQ@mail.gmail.com \
    --to=soniaruby1@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).