Forward and Reverse HTTP/3 over WebTransport
draft-various-httpbis-h3-webtrans-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Benjamin M. Schwartz , Yaroslav Rosomakho | ||
| Last updated | 2025-08-23 (Latest revision 2025-02-19) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
HTTP/3 was initially specified only for use with the QUIC version 1 transport protocol. This specification defines how to use HTTP/3 over a WebTransport session, which can be implemented using any WebTransport protocol. This enables operation of HTTP/3 when UDP based transport is not available, as well as server-initiated HTTP/3 requests.
Authors
Benjamin M. Schwartz
Yaroslav Rosomakho
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)