Ciao TAG!

I'm requesting a review of the WebTransport API Specification.

WebTransport is an API that allows web applications to establish interactive, bidirectional, multiplexed network connections It fills gaps in the web platform, such as lack of UDP-like networking API and lack of WebSocket-like API without head-of-line blocking, by proving a web accessible interface to the WebTransport protocol being developed by the IETF WebTransport Working Group. It provides:

• Reliable streams
• Unreliable datagrams
• Encryption and congestion control
• An origin-based security model
• Multiplexing with existing HTTP/3 connections

It's great for sending or receiving high-frequency, small messages that don't need to be reliable (like game state), sending or receiving low-latency media and transferring files.

• Explainer¹ : https://github.com/w3c/webtransport/blob/main/explainer.md
• Specification URL: https://w3c.github.io/webtransport/
• Tests: https://wpt.fyi/results/webtransport?label=master&label=experimental&aligned&q=webtransport and https://github.com/bashi/rfcs/blob/08cd404ee62df4dd93b11175310d44fa98187c96/rfcs/webtransport_h3_test_server.md (still under development)
• Security and Privacy self-review²: https://w3c.github.io/webtransport/#privacy-security
• GitHub repo (if you prefer feedback filed there): https://github.com/w3c/webtransport
• Primary contacts (and their relationship to the specification):
  • Yutaka Hirano (@yutakahirano) - Google - editor
  • Bernard Aboba (@aboba) - Microsoft Corporation - editor
  • Victor Vasiliev (@vasilvv) - Google - editor
  • Jan-Ivar Bruaroey (@jan-ivar) - Mozilla - co-chair
  • Will Law (@wilaw) - Akamai - co-chair
  • Yves Lafon (@ylafon) - W3C - staff contact
• Organization(s)/project(s) driving the specification: W3C WebTransport Working Group
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://www.chromestatus.com/feature/4854144902889472

Further details:

• [x ] I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: we have a prepared a milestone for a minimum viable implementation and TAG oversight is requested as part of that milestone.
• The group where the work on this specification is currently being done: W3C WebTransport Working Group
• This work is being funded by: Google, Microsoft, Mozilla and Akamai through WG participation.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback. Please prefix the title with [TAG] and we will triage appropriately.