From: Vlad Yasevich <vyasevich@gmail.com> To: David Laight <David.Laight@ACULAB.COM>, 'Geir Ola Vaagland' <geirola@gmail.com>, "netdev@vger.kernel.org" <netdev@vger.kernel.org> Cc: "linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org> Subject: Re: [PATCH net-next 0/6] A step closer to RFC 6458 compliancy Date: Tue, 17 Jun 2014 14:42:24 -0400 [thread overview] Message-ID: <53A08C10.70103@gmail.com> (raw) In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1725DEC9@AcuExch.aculab.com> On 06/17/2014 11:36 AM, David Laight wrote: > From: Of Geir Ola Vaagland >> These patches are part of my master thesis project. I have been searching for discrepancies between >> the socket API specificiation in RFC 6458 and the current Linux SCTP implementation. The following >> patches are my humble attempts at getting somewhat closer to compliancy. > > I've just been reading RFC 6458 - HTF did it get past the editors and > then published in its current form? > Lots of the structures have implied padding. > There is an embedded 'struct sockaddr_storage' in the middle of > one structure. In some OS this should never actually be instantiated. This particular horse has been beaten to death already. It has been around for so long that we couldn't really change it anymore. I've argued the padding issue, but the editor stance is that it's implementation dependent. -vlad > > Maybe the interface could have been changed in 2001, but not in 2011. > > David > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-sctp" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevich@gmail.com> To: David Laight <David.Laight@ACULAB.COM>, 'Geir Ola Vaagland' <geirola@gmail.com>, "netdev@vger.kernel.org" <netdev@vger.kernel.org> Cc: "linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org> Subject: Re: [PATCH net-next 0/6] A step closer to RFC 6458 compliancy Date: Tue, 17 Jun 2014 18:42:24 +0000 [thread overview] Message-ID: <53A08C10.70103@gmail.com> (raw) In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1725DEC9@AcuExch.aculab.com> On 06/17/2014 11:36 AM, David Laight wrote: > From: Of Geir Ola Vaagland >> These patches are part of my master thesis project. I have been searching for discrepancies between >> the socket API specificiation in RFC 6458 and the current Linux SCTP implementation. The following >> patches are my humble attempts at getting somewhat closer to compliancy. > > I've just been reading RFC 6458 - HTF did it get past the editors and > then published in its current form? > Lots of the structures have implied padding. > There is an embedded 'struct sockaddr_storage' in the middle of > one structure. In some OS this should never actually be instantiated. This particular horse has been beaten to death already. It has been around for so long that we couldn't really change it anymore. I've argued the padding issue, but the editor stance is that it's implementation dependent. -vlad > > Maybe the interface could have been changed in 2001, but not in 2011. > > David > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-sctp" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
next prev parent reply other threads:[~2014-06-17 18:42 UTC|newest] Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-17 15:01 [PATCH net-next 0/6] A step closer to RFC 6458 compliancy Geir Ola Vaagland 2014-06-17 15:01 ` Geir Ola Vaagland 2014-06-17 15:01 ` [PATCH net-next 1/6] Support for SCTP_RECVRCVINFO socket option Geir Ola Vaagland 2014-06-17 15:01 ` Geir Ola Vaagland 2014-06-18 23:30 ` David Miller 2014-06-18 23:30 ` David Miller 2014-06-17 15:01 ` [PATCH net-next 2/6] Support for SCTP_RCVINFO ancillary data Geir Ola Vaagland 2014-06-17 15:01 ` Geir Ola Vaagland 2014-06-18 23:30 ` David Miller 2014-06-18 23:30 ` David Miller 2014-06-17 15:01 ` [PATCH net-next 3/6] Support for SCTP_SNDINFO " Geir Ola Vaagland 2014-06-17 15:01 ` Geir Ola Vaagland 2014-06-17 15:01 ` [PATCH net-next 4/6] Support for SCTP_NXTINFO socket option Geir Ola Vaagland 2014-06-17 15:01 ` Geir Ola Vaagland 2014-06-17 15:01 ` [PATCH net-next 5/6] Support for receiving SCTP_NXTINFO ancillary data Geir Ola Vaagland 2014-06-17 15:01 ` Geir Ola Vaagland 2014-06-17 15:01 ` [PATCH net-next 6/6] Support for SCTP_DEFAULT_SNDINFO socket option Geir Ola Vaagland 2014-06-17 15:01 ` Geir Ola Vaagland 2014-06-18 23:33 ` David Miller 2014-06-18 23:33 ` David Miller 2014-06-17 15:14 ` [PATCH net-next 0/6] A step closer to RFC 6458 compliancy David Laight 2014-06-17 15:36 ` David Laight 2014-06-17 18:42 ` Vlad Yasevich [this message] 2014-06-17 18:42 ` Vlad Yasevich 2014-06-18 8:42 ` David Laight 2014-06-18 12:43 ` Michael Tuexen 2014-06-18 12:43 ` Michael Tuexen 2014-06-18 13:16 ` David Laight 2014-06-18 13:24 ` Michael Tuexen 2014-06-18 13:24 ` Michael Tuexen 2014-06-18 13:25 ` Vlad Yasevich 2014-06-18 13:25 ` Vlad Yasevich 2014-06-18 13:29 ` Michael Tuexen 2014-06-18 13:29 ` Michael Tuexen 2014-06-18 13:53 ` David Laight -- strict thread matches above, loose matches on Subject: below -- 2014-06-17 11:57 Geir Ola Vaagland 2014-06-17 11:57 ` Geir Ola Vaagland 2014-06-17 11:57 ` [PATCH net-next 1/6] Support for SCTP_RECVRCVINFO socket option Geir Ola Vaagland 2014-06-17 11:57 ` Geir Ola Vaagland 2014-06-17 12:35 ` David Laight 2014-06-17 12:35 ` David Laight 2014-06-17 13:57 ` Vlad Yasevich 2014-06-17 13:57 ` Vlad Yasevich 2014-06-17 11:57 ` [PATCH net-next 2/6] Support for SCTP_RCVINFO ancillary data Geir Ola Vaagland 2014-06-17 11:57 ` Geir Ola Vaagland 2014-06-17 12:36 ` David Laight 2014-06-17 14:07 ` Vlad Yasevich 2014-06-17 14:07 ` Vlad Yasevich 2014-06-17 11:57 ` [PATCH net-next 3/6] Support for SCTP_SNDINFO " Geir Ola Vaagland 2014-06-17 11:57 ` Geir Ola Vaagland 2014-06-17 12:38 ` David Laight 2014-06-17 14:29 ` Vlad Yasevich 2014-06-17 14:29 ` Vlad Yasevich 2014-06-17 14:42 ` David Laight 2014-06-17 11:57 ` [PATCH net-next 4/6] Support for SCTP_NXTINFO socket option Geir Ola Vaagland 2014-06-17 11:57 ` Geir Ola Vaagland 2014-06-17 11:57 ` [PATCH net-next 5/6] Support for receiving SCTP_NXTINFO ancillary data Geir Ola Vaagland 2014-06-17 11:57 ` Geir Ola Vaagland 2014-06-17 11:57 ` [PATCH net-next 6/6] Support for SCTP_DEFAULT_SNDINFO socket option Geir Ola Vaagland 2014-06-17 11:57 ` Geir Ola Vaagland 2014-06-17 12:32 ` [PATCH net-next 0/6] A step closer to RFC 6458 compliancy David Laight 2014-06-17 13:40 ` Vlad Yasevich 2014-06-17 13:40 ` Vlad Yasevich
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=53A08C10.70103@gmail.com \ --to=vyasevich@gmail.com \ --cc=David.Laight@ACULAB.COM \ --cc=geirola@gmail.com \ --cc=linux-sctp@vger.kernel.org \ --cc=netdev@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: linkBe 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.