- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Sun, 16 May 2021 18:16:18 +0000
- To: public-webrtc-logs@w3.org
@unicomp21 Not sure what use case you are contemplating, but this doesn't seem like a WebRTC issue (although it might relate to the WebTransport API or protocol). WebTransport is a client/server API, not a P2P API like [WebRTC-QUIC](https://github.com/w3c/webrtc-quic). As a result, WebTransport is not designed to handle NAT traversal; the server is assumed to have a globally reachable IP address. So as to be able to handle use cases where UDP and QUIC might be blocked, addition to running over HTTP/3, WebTransport API is also contemplating support for HTTP/2 failover. Assuming that HTTP/2 failover support is added, the WebTransport API should be usable for both consumers and enterprise users. Exception might be enterprises which block UDP and most TCP, except for HTTP versions < 2. That could be addressed by TURN over TCP/TLS and wouldn't be helped by TURN over WebTransport. You might want to attend the [IETF WebTransport WG meeting on May 20](https://datatracker.ietf.org/doc/agenda-interim-2021-webtrans-02-webtrans-01/). -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2651#issuecomment-841855148 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 16 May 2021 18:16:22 UTC