[w3ctag/design-reviews] WG Revision: WebTransport (Issue #1212)

wilaw created an issue (w3ctag/design-reviews#1212)

### Specification

https://www.w3.org/TR/2026/WD-webtransport-20260325/

### Explainer

https://github.com/w3c/webtransport/blob/main/explainer.md

### Links

- The WG's request for this TAG review: https://github.com/w3c/webtransport/issues/741 
- TAG review of the previous version of this specification, if any: https://github.com/w3ctag/design-reviews/issues/669
- A description of what has changed since our previous review: [Summary of Changes](https://github.com/w3c/webtransport/issues/741#issuecomment-4083412342) along with a [diff ](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2021%2FWD-webtransport-20211014%2F&doc2=https%3A%2F%2Fwww.w3.org%2FTR%2F2026%2FWD-webtransport-20260325%2F) 


### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo: https://github.com/w3c/webtransport
- Primary contacts:
  - Victor Vasiliev @vasilvv Google Editor
  - Nidhi Jaju @nidhijaju Google Editor
  - Jan-Ivar Bruaroey @jan-ivar Mozilla Editor
  - Will Law @wilaw Akamai co-chair
  - Jan-Ivar Bruaroey @jan-ivar Mozilla co-chair
  - Yves Lafon @ylafon W3C Staff Contact
- Organization/project driving the specification: W3C
- This work is being funded by: Google, Mozilla, Apple, Akamai through workgroup participation.
- Primary standards group developing this feature: [WebTransport Working Group](https://www.w3.org/groups/wg/webtransport)
- Incubation and standards groups that have discussed the design: 
  - WHATWG Fetch https://github.com/whatwg/fetch/issues?q=is%3Aissue%20webtransport%20state%3Aclosed
  - WHATWG Streams https://github.com/whatwg/streams/issues?q=is%3Aissue%20state%3Aclosed%20webtransport
  - W3C WebAppSec-CSP https://github.com/w3c/webappsec-csp/issues?q=is%3Aissue%20webtransport



### Feedback so far

- Active horizontal reviews: https://github.com/w3c/webtransport/issues/741
- Multi-stakeholder feedback:
  - Chromium comments: [Intent to Ship: WebTransport Application Protocol Negotiation ](https://groups.google.com/a/chromium.org/g/blink-dev/c/PfPf23iI0n0/m/phYat8D1AAAJ)
  - Mozilla comments: https://github.com/mozilla/standards-positions/issues/167
  - WebKit comments: https://github.com/WebKit/standards-positions/issues/18
- Major unresolved issues with or opposition to this specification: None
- Status/issue trackers for implementations: 
  - Chrome Status (shipped) https://chromestatus.com/feature/4854144902889472
  - Mozilla's (shipped) https://bugzilla.mozilla.org/show_bug.cgi?id=1709355
  - WebKit's Bugzilla (shipped) https://bugs.webkit.org/show_bug.cgi?id=297534 and [Safari release note](https://webkit.org/blog/17862/webkit-features-for-safari-26-4/)


### You should also know that...

_No response_

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1212


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1212
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1212@github.com>