Has any browser announced anything approaching a timeline for when they'll support IETF QUIC?https://twitter.com/eastdakota/status/1044604596767797248 …
-
-
Er, diff the specs? Seriously, it’s pretty wide ranging. TLS 1.3 instead of custom crypto, new handshake, unidirectional streams, etc etc etc.
-
and different packet design, hq is not at all has h2 over (original) gQUIC, and... (although gquic has slowly converged in iquic's direction over time too)
-
Right - gQuic is slowly morphing into iQuic.
-
A few endpoints log H2 transactions as "HTTP/2.0" - curl, Firefox, Apache(?)... What would they do for HTTP/QUIC? Is this where "HTTP/3" is a good fit?
-
as funny as it may sound, it will actually become a serious thing to decide soon...
-
Arguably, we already need to decide for DevTools and HAR, for example. (But no, HTTP/3 is not the way to go)
-
That's a discussion that's ongoing.
-
Not only is there confusion between gQUIC and iQUIC (which will hopefully go away), there's also confusion between QUIC-the-transport and QUIC-for-HTTP.
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.