Consider using `sctp-rs` crate?

[gabhijit]

@nplrkn :

This is an interesting project. I was looking at 'sctp' implementation in your code. In fact it was the same problem that I had faced, that there was no usable SCTP implementation in the Rust world, hence I started developing sctp-rs crate, which provides nice Rust APIs using Rust data structures and only using libc. The crate is modeled on RFC6458 (and not exactly aligned with webrtc-sctp style APIs). Also, it tries to be like Listener, TcpStream like structures which the users are used in the Rust world.

If you are considering refactoring - I would definitely suggest taking a look at this particular crate. This crate does not depend on any SCTP library being present and only makes use of libc calls internally.

Let me know what are your thoughts, I may send a couple of PRs to integrate that.

Here's the link to the project https://github.com/gabhijit/ellora

[nplrkn]

Hi @gabhijit , that would be great and I would gladly integrate a PR from you. It would be nice to have a clean API rather than the one I kludged together quickly,

My main priorities for the supported function:

• actually used today

  • async
  • non blocking I/O
  • error messages (can't bind, can't connect)
  • heartbeat and no delay sockopts

• might want to integrate in next year or so (...my progress is slow!)

  • ability to set and receive stream ID
  • back pressure.

One interesting point I ran into is error handling follow async connect. My code in SctpAssocation::establish() implements this: https://cr.yp.to/docs/connect.html .

[gabhijit]

@nplrkn : Sorry this got missed somehow. Sure will consider it when I find some free cycles!