> SCTP was never intended to be a TCP replacement or a basis for TCP or whatever Ivan Pepelnjak thinks it to be. It is a separate protocol which is designed to

> SCTP was never intended to be a TCP replacement or a basis for TCP or whatever Ivan Pepelnjak thinks it to be. It is a separate protocol which is designed to provide a different set of features to a different set of applications. I don't think that's what Ivan means at all. He's simply saying that applications that now are using TCP are not easily adopted to SCTP, even if SCTP would have been a better fit. I agree with you though, at the point SCTP was at a usable protocol the internet was already solidly invested in TCP and there was no going back. Not for software reasons but because there is also a lot of hardware infrastructure that's simply built to only support TCP and UDP, always making SCTP a second class citizen.