>"In fact, if you had paid attention, you'd seen that Google already has not just plans, but it's own implementation, to replace TCP: https://en.wikipedia.org/w

>"In fact, if you had paid attention, you'd seen that Google already has not just plans, but it's own implementation, to replace TCP: https://en.wikipedia.org/wiki/QUIC" https://en.wikipedia.org/wiki/QUIC" What you have just demonstrated is that you don't understand networking or networking terminology. "TCP/IP" is used to refer to the entire suite of protocols.[1] Part of that suite iS UDP. The U in QUIC is for UDP. QUIC uses UDP. And both UDP and QUIC are IETF standards.[1]. There is nothing proprietary about an an open standard is there? And what protocols use QUIC? HTTP and TLS also IETF standards. Oh and QUIC falls back to TCP too. And the decision to put QUIC on top of UDP rather than on top of IP was due to problems with middle boxes(see SCTP.) Is had nothing to do with trying to create a "proprietary pipe." >"Carriers have had special deals with companies like Facebook, (and of course with their own owned content delivery subsidiaries), since forever.." Yeah that special deal is called "zero rating" and it's where FB gives a ton of cash to the incumbent PTT in developing countries. Any carrier is happy to do this for you if you pay them enough cash. This has nothing to do with a carrier operating special networking gear for FB. FB builds and operates their own CDN and previously used Akami which is not owned by a carrier. [1] https://tools.ietf.org/html/rfc1180 https://tools.ietf.org/html/rfc1180 [2] https://datatracker.ietf.org/wg/quic/about/ https://datatracker.ietf.org/wg/quic/about/