Using QUIC Datagrams with HTTP/3
draft-schinazi-quic-h3-datagram-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-04
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group D. Schinazi
Internet-Draft Google LLC
Intended status: Experimental November 04, 2019
Expires: May 7, 2020
Using QUIC Datagrams with HTTP/3
draft-schinazi-quic-h3-datagram-02
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.
Discussion of this work is encouraged to happen on the QUIC IETF
mailing list quic@ietf.org [1] or on the GitHub repository which
contains the draft: https://github.com/DavidSchinazi/draft-
h3-datagram [2].
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 May 7, 2020.
Copyright Notice
Copyright (c) 2019 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
Schinazi Expires May 7, 2020 [Page 1]
Internet-Draft HTTP/3 Datagrams November 2019
(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 . . . . . . . . . . . . . . . 2
2. HTTP/3 DATAGRAM Frame Format . . . . . . . . . . . . . . . . 3
2.1. Flow Identifiers . . . . . . . . . . . . . . . . . . . . 3
3. Flow Identifier Allocation . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The QUIC DATAGRAM extension [I-D.pauly-quic-datagram] provides
application protocols running over QUIC [I-D.ietf-quic-transport]
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
[I-D.ietf-quic-http] by adding an identifier at the start of the
frame payload.
This design mimics the use of Stream Types in HTTP/3, which provide a
demultiplexing identifier at the start of each unidirectional stream.
Discussion of this work is encouraged to happen on the QUIC IETF
mailing list quic@ietf.org [3] or on the GitHub repository which
contains the draft: https://github.com/DavidSchinazi/draft-
h3-datagram [4].
1.1. Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
Schinazi Expires May 7, 2020 [Page 2]
Internet-Draft HTTP/3 Datagrams November 2019
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. HTTP/3 DATAGRAM Frame Format
When used with HTTP/3, the Datagram Data field of QUIC DATAGRAM
Show full document text