RFC 9220: Bootstrapping WebSockets with HTTP/3
In plain English — editorial summary, not part of the RFC
The mechanism for running the WebSocket Protocol over a single stream of an HTTP/2 connection is equally applicable to HTTP/3, but the HTTP-version-specific details need to be specified. This document describes how the mechanism is adapted for HTTP/3.
Document record
- Document ID
- RFC9220
- Published
- June 2022
- Authors
- R. Hamilton
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5411A Hitchhiker's Guide to the Session Initiation Protocol (SIP)Current
February 2009
- RFC 9221An Unreliable Datagram Extension to QUICCurrent
March 2022
- RFC 9218Extensible Prioritization Scheme for HTTPCurrent
June 2022
- RFC 9213Targeted HTTP Cache ControlCurrent
June 2022
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9209The Proxy-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9205Building Protocols with HTTPCurrent
June 2022
- RFC 9235TCP Authentication Option (TCP-AO) Test VectorsCurrent
May 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?