Not sure what aspect your question refers to, but let me try two angles:
- SCTP does not run over UDP, so it does not address the design constraint of having a protocol that does. This design constraint triggered this whole discussion.
- SCTP is significantly more complicated than TCP in its implementation and its performance is generally the same, except in circumstances involving head-of-line blocking. (If you're interested, I can point you to some papers I've been involved with that explore this aspect in much greater quantitative detail.)
That said, it has long been noted that SCTP will have trouble getting traction in the consumer and enterprise Internet space unless it (also) runs over UDP, as there seem to be few NATs that know how to handle SCTP and thus it is effectively unusable by a fair fraction of the Internet user population.
Also, "converting" SCTP to use UDP is likely to be relatively easy, and similar to the mechanism proposed in the TCP-over-UDP draft. Tunneling is another approach, with a different set of trade-offs.
Also, the goal is to design RELOAD so that it could indeed use SCTP as one of its transports in the future if there's demand for it.
Henning On Apr 13, 2009, at 9:30 AM, Sumit Garg wrote:
Advantages as compared to SCTP??
_______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
