← Back to context

Comment by senshan

4 months ago

Seems like a fool's errand. The cited RFC8684 starts from the wrong premise:

> TCP/IP communication is currently restricted to a single path per connection, yet multiple paths often exist between peers.

In reality, IP modules of all the hosts and routers can load-balance over a set of all available interfaces, as long as global routing information is available.

It is very rare that a single TCP connection will be load-balanced over multiple interfaces, since that would frequently cause out-of-order delivery, which sucks quite a lot if the receiver isn't prepared for it.

  • Isn't every TCP implementation required to deal with receiving packages out-of-order? That is one of the abstraction TCP provides.

    • Yes, but not performantly so. In particular, out-of-order delivery is likely to be seen as packet loss, signalling TCP to reduce the transfer speed in one way or the other.