RFC 9292: Binary Representation of HTTP Messages
In plain English — editorial summary, not part of the RFC
This document defines a binary format for representing HTTP messages.
Document record
- Document ID
- RFC9292
- Published
- August 2022
- Authors
- M. Thomson; C. A. Wood
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9293Transmission Control Protocol (TCP)Current
August 2022
- RFC 9290Concise Problem Details for Constrained Application Protocol (CoAP) APIsCurrent
October 2022
- RFC 9289Towards Remote Procedure Call Encryption by DefaultCurrent
September 2022
- RFC 9287Greasing the QUIC BitCurrent
August 2022
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 2022
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9308Applicability of the QUIC Transport ProtocolCurrent
September 2022
- RFC 9312Manageability of the QUIC Transport ProtocolCurrent
September 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?