Why was SCTP selected for WebRTC’s data channel? (2014)

Re:Why was SCTP selected for WebRTC’s data channel? (2014) by richardwhiuk on Wednesday December 25, 2019 @05:25PM (#21880825)

SCTP has been used in professional settings for telecoms for at least a decade.

The kernel implementation in Linux is stable and has been for many versions.

There are gotchas: - Cloud support for SCTP is poor. Azure has no support for SCTP on its load balancers. - Kubernetes support is similarly poor - SCTP support is beta and behind a feature gate.

[ Parent | on HN ]

Re:Why was SCTP selected for WebRTC’s data channel? (2014) by Sean-Der on Wednesday December 25, 2019 @05:34PM (#21880854)

Have you done SCTP over the public internet?

I haven't tried it myself, but always heard the only way to make it work was encapsulated in UDP.

[ Parent | on HN ]

Re:Why was SCTP selected for WebRTC’s data channel? (2014) by gmueckl on Wednesday December 25, 2019 @08:34PM (#21881529)

A lot of providers will filter out SCTP at the boundaries, especially for consumers. I know of providers that only whitelist TCP and UDP on their gateways.

[ Parent | on HN ]

Re:Why was SCTP selected for WebRTC’s data channel? (2014) by rjsw on Wednesday December 25, 2019 @05:46PM (#21880919)

Probably down to whether routers can do NAT for SCTP, I'm part way through adding support for it in the firewall that I use.

Routing SCTP over IPv6 should be easier.

[ Parent | on HN ]