3 ms·
We will have to abandon TCP eventually. We can't keep using the same protocol for 100 years. We should think about the next generation stack, what we would idea
by throwaway787544 4y ago
We will have to abandon TCP eventually. We can't keep using the same protocol for 100 years. We should think about the next generation stack, what we would ideally like to solve, and not just tiny little incremental changes that preserve legacy design quirks. But sadly it's in the hands of industry rather than researchers and practitioners.
- oaiey 4y agoWhy? IPv6 enabled the address range. In the TCP space alternatives exists (UDP/Quick). I do not believe TCP will be replaced. The only thing which surely will be replaced are the routing exchange protocols like BGP with all the shenanigans happening there. If you believe in space colonialism then there will be some kind of message oriented layer on top to deal with the latencies (think universal SMTP or something).
- throwaway787544 4y agoThere's a lot of limitations within those protocols that just make things unnecessarily difficult and limit functionality. Port numbers and the lack of logical service names, lack of routing across disparate unroutable routes, lack of carrying forward/back diagnosis of network segments, etc. HTTP as an additional transport protocol is a shitty hack that people use to work around some of those issues but more remain.
- oaiey 4y agoMakes all sense but not enough to migrate away from TCP. Half of the things can be also solved by higher level services (and lower than HTTP).