4 ms·

I think SCTP was a very good choice. Writing a SCTP implementation for Pion WebRTC[0] was really enjoyable. The SCTP RFC is well written and easily available [

I think SCTP was a very good choice. Writing a SCTP implementation for Pion WebRTC[0] was really enjoyable. The SCTP RFC is well written and easily available [1]. Once you learn all the chunk types things start to fall into place. SCTP is also battle tested and we know what flaws it has. I am pessimistic about alternatives * New protocols/changes are spread across multiple drafts, and they are abandoned once they land in browsers. Most of the time these changes are already going to happen and these drafts are just a way to notify the general public it is happening. So it ends up being 'the implementation is the spec', and things are brittle. SCTP doesn't break like that. * WebRTC is still very difficult to use. For large dev teams/corporations it is a solved problem, but I really wish there was more excitement/emphasis around lowering the barrier to entry. It is a really powerful technology, but it seems like we just keep getting half-baked things out the door and then moving on. [0] https://github.com/pion/webrtc https://github.com/pion/webrtc [1] https://tools.ietf.org/html/rfc4960 https://tools.ietf.org/html/rfc4960

zamadatix 7y ago
RFC490 was simply a "rollup" of SCTP at that point with minor corrections not some protocol with immaculate birth where the initial RFC gets you up to date with the protocol. It also features a large set of errata and about a dozen feature extension RFCs that have come out since (as well as an RFC on security attacks found against SCTP that one definitely should to read before writing an implementation). I'm also not familiar with any recent protocol added to browsers that has been abandoned from a standards perspective in the way you describe. Websockets and what were known as SPDY & Quic have more standards activity than ever before. Are you referring to the barrier to use WebRTC or the barrier to make your own implementation?
krasin 7y ago
Hey Sean-Der, thank you for writing Pion! In my opinion, it's the cleanest and easiest to use WebRTC implementation.
giongto35 7y ago
Hi Sean, I read some article about SCTP but I still keep wondering what the best usecase for SCTP is. Can you give some examples?

zamadatix 7y ago

RFC490 was simply a "rollup" of SCTP at that point with minor corrections not some protocol with immaculate birth where the initial RFC gets you up to date with the protocol. It also features a large set of errata and about a dozen feature extension RFCs that have come out since (as well as an RFC on security attacks found against SCTP that one definitely should to read before writing an implementation). I'm also not familiar with any recent protocol added to browsers that has been abandoned from a standards perspective in the way you describe. Websockets and what were known as SPDY & Quic have more standards activity than ever before. Are you referring to the barrier to use WebRTC or the barrier to make your own implementation?

krasin 7y ago

Hey Sean-Der, thank you for writing Pion! In my opinion, it's the cleanest and easiest to use WebRTC implementation.

giongto35 7y ago

Hi Sean, I read some article about SCTP but I still keep wondering what the best usecase for SCTP is. Can you give some examples?