> Im gonna feel really bad breaking the QUIC / HTTP/3 news. Cuz google totally wrote the new transport layer. They wrote the last one too (SPDY HTTP/2.)
This would presumably be news to everybody involved.
Google's QUIC ("GQUIC") isn't very close to the IETF QUIC standard under development. The IETF went with TLS 1.3 as the cryptographic foundation (which didn't exist when Google built GQUIC) and most the details have changed considerably. You can definitely see a family resemblance, but for Google this was a proof of concept hack and for the QUIC WG they're building what is probably a successor to TCP. It's the difference between a five year old's doodle of a house and the plans you need to submit to get someone to approve it and then build the house.
The chairs are currently not Google employees (they work at Fastly and NetApp) and the editors on the main transport draft aren't Google either (Mozilla and Fastly). There are Google people in the room (such as Adam Langley of course) but there are people from the other browsers too.
This would presumably be news to everybody involved.
Google's QUIC ("GQUIC") isn't very close to the IETF QUIC standard under development. The IETF went with TLS 1.3 as the cryptographic foundation (which didn't exist when Google built GQUIC) and most the details have changed considerably. You can definitely see a family resemblance, but for Google this was a proof of concept hack and for the QUIC WG they're building what is probably a successor to TCP. It's the difference between a five year old's doodle of a house and the plans you need to submit to get someone to approve it and then build the house.
The chairs are currently not Google employees (they work at Fastly and NetApp) and the editors on the main transport draft aren't Google either (Mozilla and Fastly). There are Google people in the room (such as Adam Langley of course) but there are people from the other browsers too.