RFC 9114: HTTP/3
In plain English — editorial summary, not part of the RFC
The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.
Document record
- Document ID
- RFC9114
- Published
- June 2022
- Authors
- M. Bishop
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 57
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 9959Careful Resume: Convergence of Congestion Control from Retained StateCurrent
May 2026
- RFC 9113HTTP/2Current
June 2022
- RFC 9134RTP Payload Format for ISO/IEC 21122 (JPEG XS)Current
October 2021
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 8999Version-Independent Properties of QUICUpdated
May 2021
- RFC 9260Stream Control Transmission ProtocolCurrent
June 2022
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 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?