How not to get a protocol implementation merged [LWN.net]

How not to get a protocol implementation merged

Posted Jan 20, 2011 10:22 UTC (Thu) by renox (subscriber, #23785)
In reply to: How not to get a protocol implementation merged by job
Parent article: How not to get a protocol implementation merged

Well I'm not an expert but SCTP has an initial handshake which require at least one roundtrip before sending data, so the connection initiation isn't low latency..

I wonder why they did it this way?
Me I would have authorised the initiation of the connection (INIT) with a data filed with the possibility of the server (INIT ACK) replying that it dropped the data (either to simplify its implementation or because it is overloaded in case a cracker try to spoof IPs) thus requiring the client to re-send the data.
With this simple design, you have low-latency(*) and security..

*: only if the server isn't overloaded though.

(Log in to post comments)