News for hackers. Stuff that matters.
Re:What went wrong: SCTP (2009) by acdha on Thursday July 02, 2015 @03:02PM (#9820895)
The big problem is that that promotion really needs to be aimed at a highly specific community: operating system and network equipment vendors.

The original article was written 6 years ago and wasn't a novel position at the time. It's hard to say anything's changed since then because app developers are still blocked waiting on mainstream middle-box support and I don't see that really happening without some sort of pressure on the vendors.

Re:What went wrong: SCTP (2009) by ftigeot on Thursday July 02, 2015 @03:23PM (#9821017)
Relevant Operating System community news here: https://news.ycombinator.com/item?id=9797932

SCTP support has just been removed from DragonFly. The code had been present for 15 years (inherited from FreeBSD) and in these 15 years there wasn't even a single known user.

If there really are people using it it's effectively in a very very small niche and they will have to do everything themselves. There is no way generic operating system developers can work on this protocol.

Re:What went wrong: SCTP (2009) by acdha on Thursday July 02, 2015 @03:41PM (#9821126)
The only way I see this cycle changing is if someone ships a real application which uses SCTP to provide significant benefits to users. If deploying SCTP improved performance or reliability for video-chat, a popular game, etc. there'd be a more compelling reason to go to e.g. Cisco, NetGear, etc. and ask them to ship kernel-level code with likely security impact to everything they sell.

WebRTC is the most obvious candidate for this but maybe one of the HTTP2-over-SCTP experiments will go well enough that someone will ship it in a real browser and start the process of saying “Web users get n% performance improvements if SCTP is implemented”. That certainly seems like a rather long game to play, however.