Skip to main content

Using QUIC Datagrams with HTTP/3

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author David Schinazi
Last updated 2020-10-12
Replaced by draft-schinazi-masque-h3-datagram
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-schinazi-masque-h3-datagram
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:


The QUIC DATAGRAM extension provides application protocols running over QUIC with a mechanism to send unreliable data while leveraging the security and congestion-control properties of QUIC. However, QUIC DATAGRAM frames do not provide a means to demultiplex application contexts. This document defines how to use QUIC DATAGRAM frames when the application protocol running over QUIC is HTTP/3 by adding an identifier at the start of the frame payload. Discussion of this work is encouraged to happen on the QUIC IETF mailing list ( ( or on the GitHub repository which contains the draft:


David Schinazi

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)