Using QUIC Datagrams with HTTP/3
draft-schinazi-masque-h3-datagram-04
Network Working Group D. Schinazi
Internet-Draft Google LLC
Intended status: Standards Track L. Pardue
Expires: 9 July 2021 Cloudflare
5 January 2021
Using QUIC Datagrams with HTTP/3
draft-schinazi-masque-h3-datagram-04
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 9 July 2021.
Schinazi & Pardue Expires 9 July 2021 [Page 1]
Internet-Draft HTTP/3 Datagrams January 2021
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions and Definitions . . . . . . . . . . . . . . . 3
2. Flow Identifiers . . . . . . . . . . . . . . . . . . . . . . 3
3. Flow Identifier Allocation . . . . . . . . . . . . . . . . . 3
4. HTTP/3 DATAGRAM Frame Format . . . . . . . . . . . . . . . . 4
5. The H3_DATAGRAM HTTP/3 SETTINGS Parameter . . . . . . . . . . 4
6. Datagram-Flow-Id Header Field Definition . . . . . . . . . . 5
7. HTTP Intermediaries . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
9.1. HTTP SETTINGS Parameter . . . . . . . . . . . . . . . . . 7
9.2. HTTP Header Field . . . . . . . . . . . . . . . . . . . . 8
9.3. Flow Identifier Parameters . . . . . . . . . . . . . . . 8
10. Normative References . . . . . . . . . . . . . . . . . . . . 8
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The QUIC DATAGRAM extension [DGRAM] provides application protocols
running over QUIC [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 [H3] 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.
This design mimics the use of Stream Types in HTTP/3, which provide a
demultiplexing identifier at the start of each unidirectional stream.
Schinazi & Pardue Expires 9 July 2021 [Page 2]
Show full document text