Data

WebTransport spec status

Where the WebTransport specifications stand today: the W3C API, the IETF protocol drafts and the RFCs they build on, each with its source.

Documents

8 documents. Status is shown as the source words it; the badge only reinforces it. Scroll the table sideways on narrow screens.

Status, version or revision, date and source of WebTransport specifications, IETF drafts and RFCs, checked 28 October 2026.
Document	Kind	Status	Version / rev	Date	Source
WebTransport (W3C API specification)	W3C	Candidate Recommendation Snapshot draft spec	CR 2026-07-30	30 July 2026	w3.org
WebTransport over HTTP/3	IETF draft	Active Internet-Draft; WG state: In WG Last Call; IESG state: I-D Exists; intended status: Proposed Standard draft spec	rev 16	6 July 2026	datatracker.ietf.org
The WebTransport Protocol Framework	IETF draft	Active Internet-Draft; WG state: In WG Last Call; IESG state: I-D Exists; intended status: Proposed Standard draft spec	rev 13	6 July 2026	datatracker.ietf.org
WebTransport over HTTP/2	IETF draft	Active Internet-Draft; WG state: In WG Last Call; IESG state: I-D Exists; intended status: Proposed Standard draft spec	rev 15	6 July 2026	datatracker.ietf.org
QUIC: A UDP-Based Multiplexed and Secure Transport	RFC	Proposed Standard stable	RFC 9000	May 2021	rfc-editor.org
HTTP/3	RFC	Proposed Standard stable	RFC 9114	June 2022	rfc-editor.org
An Unreliable Datagram Extension to QUIC	RFC	Proposed Standard stable	RFC 9221	April 2022	rfc-editor.org
HTTP Datagrams and the Capsule Protocol	RFC	Proposed Standard stable	RFC 9297	August 2022	rfc-editor.org

Data fetched 28 October 2026 from the W3C API, the IETF Datatracker API and the RFC Editor; checked 28 October 2026. IETF draft dates are the Datatracker's timestamp for the document; RFC dates are month and year only, as the RFC Editor gives them.

Where the data comes from

Each row is read from the document's own publisher: the W3C API for the WebTransport API specification, the IETF Datatracker API for the drafts, and the RFC Editor for published RFCs. A refresh script keeps the last good value for any row it cannot fetch and marks it stale. Download this data as JSON.

Known unknowns

IETF draft names and revision numbers can change as the working group continues its work, so a draft listed here may be renamed, replaced or published as an RFC under a different number. This table shows names and revisions as of 28 October 2026.

A discrepancy we observed on 28 October 2026: the W3C WebTransport specification (Candidate Recommendation Snapshot of 30 July 2026) and the IETF WebTransport over HTTP/3 draft (rev 16) give different values for the HTTP/3 :protocol token. The W3C text we read uses "webtransport", while the IETF draft says "webtransport-h3". We read only part of the W3C text and have not tested what current browsers and servers actually send, so treat this as unresolved. Check the draft revision your implementation targets rather than assuming one value.

Cite this page

Title: WebTransport spec status (W3C and IETF)
Author: WebTransport Day (organization)
URL: https://webtransport.day/spec-status/
Updated: October 28, 2026

WebTransport Day. "WebTransport spec status (W3C and IETF)." Last updated October 28, 2026. https://webtransport.day/spec-status/

Report an error on this page