3 ms·

I think this is unlikely. Part of the advantage of having built your own datapath is being able to change it on a whim; I don't see Google giving this up by agr

I think this is unlikely. Part of the advantage of having built your own datapath is being able to change it on a whim; I don't see Google giving this up by agreeing to stick to some fixed specification.

euyyn 9y ago
It's to be expected from any protocol for which this is true: > the protocol is under rapid development, with extensive rewriting of the protocol occurring over the scale of months Once it stabilizes, I don't see a reason why it couldn't go the same route SPDY -> HTTP/2 did. A faster internet is a win for Google. (I work at Google, but I'm not aware of the QUIC team's plans).
JulienSchmidt 9y ago
After Google presented the protocol to the IETF several months ago, a working group was formed: https://datatracker.ietf.org/wg/quic/about/ https://datatracker.ietf.org/wg/quic/about/ / https://quicwg.github.io/ https://quicwg.github.io/ There will soon be a standardized version of QUIC with a fixed specification, probably by the end of next year. I guess Google will still continue to experiment, but then probably based on the standardized version.