WebTransport status and plan

[Yutaka Hirano]

Hi,

As you may know, the IETF working group decided to focus on WebTransport over HTTP/3. We are going to switch our implementation soon, and will start an origin trial. Note that the current implementation, WebTransport over QUIC, will be removed altogether.

We're planning to have the origin trial M91 through M94. Also we don't expect that we'll be ready to ship WebTransport over HTTP/3 in M95, which means for some milestones WebTransport over HTTP/3 will be available only with command line flags - Are you fine with the situation? We can extend the origin trial period so it is possible to raise your voice at that time, but I'd like to hear from you earlier rather than later.

Thanks,

[guest271314]

> Note that the current implementation, WebTransport over QUIC, will be removed altogether.

What?! Why? I have finally been able to realize use case that were not possible without numerous workarounds using WebTransport over QUIC https://github.com/guest271314/webtransport

[Yutaka Hirano]

Sorry for the trouble. Please see the discussions in the IETF working group for the rationale of the protocol selection.

WebTransport over HTTP/3 is similar to WebTransport over QUIC so you will be able to switch the protocol, hopefully without many troubles.

Thanks,

[guest271314]

The changes effectively make obsolete https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/quic_transport_server.py, https://github.com/GoogleChrome/samples/blob/f69ce40bed9783006c088eabb8b5987748605cd0/webtransport/client.html#L33, and https://bugs.chromium.org/p/chromium/issues/detail?id=1011392 obsolete, correct?

[Victor Vasiliev]

The server code in the example does not work with WebTransport over HTTP/3.  The web page with an example should work fine with WebTransport over HTTP/3, since the API is mostly transport-agnostic.

--
You received this message because you are subscribed to the Google Groups "web-transport-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web-transport-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/web-transport-dev/afe4467f-4a0b-431c-abb0-2ebb09bab1d6n%40chromium.org.