Applicability of the QUIC Transport Protocol
draft-ietf-quic-applicability-05
Network Working Group M. Kuehlewind
Internet-Draft Ericsson
Intended status: Informational B. Trammell
Expires: January 6, 2020 Google
July 05, 2019
Applicability of the QUIC Transport Protocol
draft-ietf-quic-applicability-05
Abstract
This document discusses the applicability of the QUIC transport
protocol, focusing on caveats impacting application protocol
development and deployment over QUIC. Its intended audience is
designers of application protocol mappings to QUIC, and implementors
of these application protocols.
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 January 6, 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
(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
Kuehlewind & Trammell Expires January 6, 2020 [Page 1]
Internet-Draft QUIC Applicability July 2019
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. The Necessity of Fallback . . . . . . . . . . . . . . . . . . 3
3. Zero RTT . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Thinking in Zero RTT . . . . . . . . . . . . . . . . . . 4
3.2. Here There Be Dragons . . . . . . . . . . . . . . . . . . 4
3.3. Session resumption versus Keep-alive . . . . . . . . . . 5
4. Use of Streams . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Stream versus Flow Multiplexing . . . . . . . . . . . . . 7
4.2. Prioritization . . . . . . . . . . . . . . . . . . . . . 7
4.3. Flow Control Deadlocks . . . . . . . . . . . . . . . . . 7
5. Packetization and Latency . . . . . . . . . . . . . . . . . . 9
6. Port Selection . . . . . . . . . . . . . . . . . . . . . . . 9
7. Connection Migration . . . . . . . . . . . . . . . . . . . . 10
8. Connection closure . . . . . . . . . . . . . . . . . . . . . 10
9. Information exposure and the Connection ID . . . . . . . . . 11
9.1. Server-Generated Connection ID . . . . . . . . . . . . . 11
9.2. Mitigating Timing Linkability with Connection ID
Migration . . . . . . . . . . . . . . . . . . . . . . . . 12
9.3. Using Server Retry for Redirection . . . . . . . . . . . 12
10. Use of Versions and Cryptographic Handshake . . . . . . . . . 12
11. Enabling New Versions . . . . . . . . . . . . . . . . . . . . 13
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
13. Security Considerations . . . . . . . . . . . . . . . . . . . 14
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
16.1. Normative References . . . . . . . . . . . . . . . . . . 14
16.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
QUIC [QUIC] is a new transport protocol currently under development
in the IETF quic working group, focusing on support of semantics as
needed for HTTP/2 [QUIC-HTTP] such as stream-multiplexing to avoid
head-of-line blocking. Based on current deployment practices, QUIC
is encapsulated in UDP. The version of QUIC that is currently under
development will integrate TLS 1.3 [TLS13] to encrypt all payload
Show full document text