In my opinion, any discussion of protocols, framing, generally anything to do
with messaging, is at least a secondary, indeed application layer, concern, to
the transport layer. It will only serve to distract from the primary goal of
maturing the library.
Perhaps start a repo such as nng/sctp, for instance, through which you may
further document the intricacies.
HTH
Michael Powell
On July 19, 2017 5:52:10 AM EDT, Eduardo Morras <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
I start a new thread about sctp in nanomsg, I hope to clarify some sctp
concepts.
FreeBSD and Linux has native kernel sctp support, other systems
(Windows) need a userland library; don't know current status on OSX. It
can work over UDP (sctp packets inside udp) in some systems too.
SCTP has two modes,
a) one-to-one similar to tcp developed to easy convert
tcp programs to sctp. It doesn't support all sctp
features but it's the easiest path to test/convert to/use sctp.
b) one-to-many with full sctp features, needs a new transport
implementation.
We (I, me) can begin with a) and start develop b), but as I said
before, I
prefer to do so AFTER test and bug fixing (implementation and logical
bugs) current nng master.
--- ---
Eduardo Morras <emorrasg@xxxxxxxx>
