6 ms·
SCTP is sometimes promoted as an alternative to solve that problem. You can have multiple stream per connection so if one blocks the other ones can keep going.
by rdtsc 13y ago
SCTP is sometimes promoted as an alternative to solve that problem. You can have multiple stream per connection so if one blocks the other ones can keep going.
- lallysingh 13y agoMy thoughts exactly. Also, you can send some data reliably (e.g., a new character model) and other data unreliably on the the same SCTP association.
- scott_karana 13y agoSCTP has always looked intriguing to me, but would most backbones and ISPs pass it natively? It sounds like it would be a waste to tunnel it in UDP, which is the alternative...
- _delirium 13y agoThe poor prospects for getting widespread SCTP support was one (though not the only) justification the SPDY people cited for doing some similar things at the application-protocol level: http://www.chromium.org/spdy/spdy-whitepaper http://www.chromium.org/spdy/spdy-whitepaper
- derefr 13y agoWebRTC Data Channels are, in fact, SCTP tunnelled over UDP (or rather, over DTLS over UDP.) They work pretty well. (I'm not sure how much of the redundancy is shaved off--does anyone know if WebRTC's tries to encapsulate "normative" SCTP, or whether it uses SCTP without checksum/port information?)
- rdtsc 13y agoYeah not sure either, good question. There is also QUIC protocol also by Google, which is yet another crack at solving the problem. Wonder if those 2 groups sat down and discussed merging or re-using code.
- MichaelGG 13y agoBackbones and most ISPs are gonna route IP packets regardless of content. Until you hit a NAT or firewall and everything that's not UDP or TCP gets dropped.
- noselasd 13y agoYes they would. The real problem is your home router/gateway/modem will not - and you're normally behind a NAT, which in all likelyhood does not know anything about SCTP (SCTP also isn't very NAT friendly).
- fulafel 13y agoSctp only breaks if the ISP or user has turned on NAT. A router wouldn't break it. NAT does bad things to IP (breaks the fundamental guarantees).
- hueving 13y ago>Sctp only breaks if the ISP or user has turned on NAT. This describes 95%+ of home users. NAT may do bad things to IP, but if you are an app developer that depends on no NAT, you're product is going to have a very limited market of people that can use it.
- stplsd 13y agoOr just open multiple TCP streams (that means of course multiple TCP connections) and waste resources on additional TCP state tracking and additional recieve/send buffer allocations, etc.
- _mhp_ 13y agoAnother alternative is minion[0]. The format is TCP on the wire which avoids the NAT problems that SCTP has, but it is able to deliver some really interesting features, including multiple message streams like SCTP. [0] https://datatracker.ietf.org/doc/search/?name=minion&activedrafts=on https://datatracker.ietf.org/doc/search/?name=minion&actived...
- tankenmate 13y agoOr if SCTP firewall issues are the only thing holding you back you can use RFC 6951; SCTP over UDP. http://tools.ietf.org/html/rfc6951 http://tools.ietf.org/html/rfc6951