4 ms·

I'm in favor of Dragonfly removing SCTP. It was okay on paper but never saw adoption and was basically doomed after most firewalls were configured to block it--

I'm in favor of Dragonfly removing SCTP. It was okay on paper but never saw adoption and was basically doomed after most firewalls were configured to block it--this is why people are building their own transports on top of UDP these days. It would almost be impossible to launch a new IP magic protocol number now. I dig the other stuff that Dragonfly is doing too. I've been a longtime BSD fan and I like that there is a strong-willed counterpoint to FreeBSD with a different architectural philosophy. The pressure pushes FreeBSD forward faster than if Dragonfly wasn't around.

muppetman 11y ago
SCTP is very much alive and kicking. In fact I have just been debugging an issue with it before reading this post. It's used between Mobile Network Elements, especially in the 4G Space, as the transport that DIAMETER sit on top of. So I agree it's niche, but it's far from a failure.
- nocarrier 11y ago
  It's cool to hear someone using it, but it's still doomed to be relegated to use inside private networks versus being used as a general use internet transport protocol, which was the point I was making.
  - muppetman 11y ago
    Ahh, yes. I agree, there's very little SCTP used in public networks.
    - quink 11y ago
      NAT being the big reason. Ironically now more than ever before is the time for NAT to disappear as IPv6 is deployed.
mariuz 11y ago
I agree with SCTP removal http://blog.ipspace.net/2009/08/what-went-wrong-sctp.html http://blog.ipspace.net/2009/08/what-went-wrong-sctp.html SCTP it's not so adopted as TCP replacement for a few reasons http://stackoverflow.com/a/20290710/66242 http://stackoverflow.com/a/20290710/66242