Using QUIC Datagrams with HTTP/3
draft-schinazi-masque-h3-datagram-04
| Document | Type |
Replaced Internet-Draft
(candidate for masque WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Schinazi , Lucas Pardue | ||
| Last updated | 2021-01-14 (Latest revision 2021-01-05) | ||
| Replaces | draft-schinazi-quic-h3-datagram | ||
| Replaced by | RFC 9297 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-masque-h3-datagram | |
| Consensus boilerplate | Unknown | ||
| 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:
Abstract
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. This allows HTTP messages to convey related information using unreliable DATAGRAM frames, ensuring those frames are properly associated with an HTTP message. Discussion of this work is encouraged to happen on the MASQUE IETF mailing list (masque@ietf.org (mailto:masque@ietf.org)) or on the GitHub repository which contains the draft: https://github.com/DavidSchinazi/draft-h3-datagram.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)