3 ms·
it is unfortunate that tcp and ip are as interlocked as they are, by which I mean, there is no way to keep your tcp connection while swapping out the underlying
by somat 2y ago
it is unfortunate that tcp and ip are as interlocked as they are, by which I mean, there is no way to keep your tcp connection while swapping out the underlying ip addresses.
This is not actually a real problem, we do just fine without it, it can be solved at higher or lower layers. But it would have been nice to have.
- kijin 2y agoYeah, it would have been nice to have, but that's all. Instead of requiring IPv6, the internet has evolved in a direction that tolerates disconnects and reduces its own IPv4 address consumption. It will probably work fine for the next 20 years at least. In the 19th century, New Yorkers worried that the city would soon be buried in horse shit because of increasing demand for transportation. The horse shit apocalypse never materialized, because transportation evolved in a way that stopped relying on horses. Now we have a different problem, of course.
- throw0101c 2y ago> it is unfortunate that tcp and ip are as interlocked as they are, by which I mean, there is no way to keep your tcp connection while swapping out the underlying ip addresses. Multipath/homing, with different IP addresses, exists with TCP and SCTP: * https://en.wikipedia.org/wiki/Multipath_TCP https://en.wikipedia.org/wiki/Multipath_TCP * https://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol#Multihoming https://en.wikipedia.org/wiki/Stream_Control_Transmission_Pr...
- toast0 2y agoMPTCP addresses this, Apple uses it (or used it, I haven't looked in a long time), and there's some way to enable it for applications on their OSes, but you also need to make it work on a server OS... I don't think it's been merged into anything but patches are around.