3 ms·
>Browsers and HTTP servers are adding all that functionality anyway I am going to assume things will improve one HTTP/3 is finalised. But right now I dont see
by ksec 6y ago
>Browsers and HTTP servers are adding all that functionality anyway
I am going to assume things will improve one HTTP/3 is finalised. But right now I dont see QUIC from non-google server at all.
And I cant help but think ( May be it is just me ), are we trying to over-engineer the Internet?
Edit: I just check on the clients side. Turns out Safari 14 may be the first browser to ship with HTTP/3 enabled by default.
- josephg 6y ago> But right now I dont see QUIC from non-google server at all. You won't see webtransport appearing for awhile either. Its all still in draft status. The IETF doesn't rush these things. And for what its worth, the spec for Webtransport is being worked on with close collaboration with the QUIC (HTTP/3) working group at the IETF. Everyone wants webtransport and QUIC to be a good fit for one another, and straightforward to implement in browsers once its ready. I worry about over-engineering too; but the best way to express those fears is to get involved. Standards are written by those who show up. And the IETF welcomes anyone who's interested to join the mailing lists and attend IETF sessions. (So long as you accept the community norms.) Even the in-person events (when they come back) bend over backwards to welcome remote attendance and remote questions. This is the video of the webtransport BoF session from Singapore last year, if you're curious how this sort of thing plays out in person. There were only about 25 people there: https://play.conf.meetecho.com/Playout/?session=IETF106-WEBTRANS-20191120-1330 https://play.conf.meetecho.com/Playout/?session=IETF106-WEBT... Or the direct youtube link (without the text from remote participants): https://youtu.be/o5cJEuO2-vk https://youtu.be/o5cJEuO2-vk
- moderation 6y agoSafari will likely be the last browser to support HTTP/3 as it will only be available in the unreleased MacOS 10.16. HTTP/3 is already in the other browsers with instructions on how to enable [0]. Firefox Nightly and Chrome Dev already support Draft 29 (which is Working Group Last Call [1]. 0. https://www.bram.us/2020/04/08/how-to-enable-http3-in-chrome-firefox-safari/ https://www.bram.us/2020/04/08/how-to-enable-http3-in-chrome... 1. https://mailarchive.ietf.org/arch/msg/quic/F7wvKGnA1FJasmaE35XIxsc2Tno/ https://mailarchive.ietf.org/arch/msg/quic/F7wvKGnA1FJasmaE3...