Just to make sure I understand this: - Google has been spearheading a protocol called 'QUIC' - It bypasses tradition TCP by using UDP to create it's own versi

Just to make sure I understand this: - Google has been spearheading a protocol called 'QUIC' - It bypasses tradition TCP by using UDP to create it's own version of TCP but encrypts the data it sends - However it could be (is?) sending a bit and header that can make tracking the message path easier. I would guess if that is true then and would not effect the performance the bit and header should be removed. I don't see what the fuss is about. Can't two different implementations exist along side each other and the public will choose the better one? Correction: I misread the article and thought though spin bit was for an encryption key. Let this be a lesson to everyone: if you are going to comment at 2 am in the morning reread your article.