UDP and congestion control
TCP is good, good for nearly everything. It’s a general purpose abstraction for networking applications. But TCP is bad for one thing: it’s general. If you have some special need, setsockopt(2) can help you. But really, it dosen’t help much. What if you have customized need for congestion control? The need for different congestion control algorithm is the main reason that we implement our protocol ontop of UDP. I was a little bit shocked that during the 4.2 merge window of Linux, TCP too got a new congestion control algorithm that’s a little bit similar to the one I used in my protocol - that is, based on the change rate of RTT, rather than based on a packet lost. ...