4 ms·
It's especially odd since WebRTC DataChannels actually use SCTP-tunneled-inside-UDP, rather than router-level SCTP datagrams.
by cjbprime 6y ago
It's especially odd since WebRTC DataChannels actually use SCTP-tunneled-inside-UDP, rather than router-level SCTP datagrams.
- rjsw 6y agoThe comments in the Firefox WebRTC code state that this is because firewalls can't do NAT of SCTP connections. I'm part way through adding this to the firewall that I use. On FreeBSD, WebRTC implementations could use the kernel stack as it implements SCTP-in-UDP (RFC6951).
- Sean-Der 6y agoFor WebRTC SCTP is over DTLS (which is over UDP) so I don't think that would work. Never done 'native SCTP' before so I don't know for sure!
- Sean-Der 6y agoI think the big piece is DTLS here. * OpenSSL was already in all the browsers, so you have a DTLS client. * Extracting the keys for SRTP gives you PFS, which is really great! This came up a lot during the SDES conversations. * I have heard that most gateways only support UDP/TCP, and other protocols aren't going to happen. That is the argument for running QUIC over UDP (vs a layer lower)