4 ms·
> 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
by 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