RFC 9297: HTTP Datagrams and the Capsule Protocol
In plain English — editorial summary, not part of the RFC
This document describes HTTP Datagrams, a convention for conveying multiplexed, potentially unreliable datagrams inside an HTTP connection. In HTTP/3, HTTP Datagrams can be sent unreliably using the QUIC DATAGRAM extension. When the QUIC DATAGRAM frame is unavailable or undesirable, HTTP Datagrams can be sent using the Capsule Protocol, which is a more general convention for conveying data in HTTP connections. HTTP Datagrams and the Capsule Protocol are intended for use by HTTP extensions, not applications.
Document record
- Document ID
- RFC9297
- Published
- August 2022
- Authors
- D. Schinazi; L. Pardue
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 9729The Concealed HTTP Authentication SchemeCurrent
February 2025
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
- RFC 9368Compatible Version Negotiation for QUICCurrent
May 2023
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 9440Client-Cert HTTP Header FieldCurrent
July 2023
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?