An Unreliable Datagram Extension to QUIC
draft-pauly-quic-datagram-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-09-10
|
|
Replaced by |
|
draft-ietf-quic-datagram
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
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 T. Pauly
Internet-Draft E. Kinnear
Intended status: Standards Track D. Schinazi
Expires: March 14, 2019 Apple Inc.
September 10, 2018
An Unreliable Datagram Extension to QUIC
draft-pauly-quic-datagram-00
Abstract
This document defines an extension to the QUIC transport protocol to
add support for sending and receiving unreliable datagrams over a
QUIC connection.
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 March 14, 2019.
Copyright Notice
Copyright (c) 2018 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.
Pauly, et al. Expires March 14, 2019 [Page 1]
Internet-Draft QUIC Datagrams September 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Specification of Requirements . . . . . . . . . . . . . . 2
2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Transport Parameter . . . . . . . . . . . . . . . . . . . . . 3
4. Datagram Frame Type . . . . . . . . . . . . . . . . . . . . . 3
5. Behavior and Usage . . . . . . . . . . . . . . . . . . . . . 4
5.1. Flow Control and Acknowledgements . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
9. Informative References . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The QUIC Transport Protocol [I-D.ietf-quic-transport] provides a
secure, multiplexed connection for transmitting reliable streams of
application data. Reliability within QUIC is performed on a per-
stream basis, so some frame types are not eligible for
retransmission.
Some applications, particularly those that need to transmit real-time
data, prefer to transmit data unreliably. These applications can
build directly upon UDP [RFC0768] as a transport, and can add
security with DTLS [RFC6347]. Extending QUIC to support transmitting
unreliable application data would provide another option for secure
datagrams, with the added benefit of sharing a cryptographic and
authentication context used for reliable streams.
This document defines two new DATAGRAM QUIC frame types, which carry
application data without requiring retransmissions.
1.1. Specification of Requirements
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
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. Motivation
Transmitting unreliable data over QUIC provides benefits over
existing solutions:
Pauly, et al. Expires March 14, 2019 [Page 2]
Internet-Draft QUIC Datagrams September 2018
o Applications that open both a reliable TLS stream and an
unreliable DTLS flow to the same peer can benefit by sharing a
single handshake and authentication context between a reliable
QUIC stream and flow of unreliable QUIC datagrams. This can
reduce the latency required for handshakes.
o QUIC uses a more nuanced loss recovery mechanism than the DTLS
Show full document text