QUIC: A UDP-Based Multiplexed and Secure Transport
draft-ietf-quic-transport-34
- Versions
- 00
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
Document | Type | Active Internet-Draft (quic WG) | ||
---|---|---|---|---|
Authors | Jana Iyengar , Martin Thomson | |||
Last updated | 2021-02-12 (latest revision 2021-01-14) | |||
Replaces | draft-ietf-quic-spin-exp, draft-hamilton-quic-transport-protocol | |||
Stream | IETF | |||
Intended RFC status | Proposed Standard | |||
Formats | plain text html xml pdf htmlized (tools) htmlized bibtex | |||
Reviews | ||||
Stream | WG state | Submitted to IESG for Publication (wg milestone: Jul 2020 - Core Protocol docume... ) | ||
Document shepherd | Lars Eggert | |||
Shepherd write-up | Show (last changed 2020-09-25) | |||
IESG | IESG state | RFC Ed Queue | ||
Action Holders |
(None)
|
|||
Consensus Boilerplate | Yes | |||
Telechat date | ||||
Responsible AD | Magnus Westerlund | |||
Send notices to | quic-chairs@ietf.org | |||
IANA | IANA review state | Version Changed - Review Needed | ||
IANA action state | RFC-Ed-Ack | |||
RFC Editor | RFC Editor state | EDIT | ||
Details |
QUIC J. Iyengar, Ed. Internet-Draft Fastly Intended status: Standards Track M. Thomson, Ed. Expires: 19 July 2021 Mozilla 15 January 2021 QUIC: A UDP-Based Multiplexed and Secure Transport draft-ietf-quic-transport-34 Abstract This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. DO NOT DEPLOY THIS VERSION OF QUIC DO NOT DEPLOY THIS VERSION OF QUIC UNTIL IT IS IN AN RFC. This version is still a work in progress. For trial deployments, please use earlier versions. Note to Readers Discussion of this draft takes place on the QUIC working group mailing list (quic@ietf.org (mailto:quic@ietf.org)), which is archived at https://mailarchive.ietf.org/arch/search/?email_list=quic Working Group information can be found at https://github.com/quicwg; source code and issues list for this draft can be found at https://github.com/quicwg/base-drafts/labels/-transport. 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/. Iyengar & Thomson Expires 19 July 2021 [Page 1] Internet-Draft QUIC Transport Protocol January 2021 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 19 July 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. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1. Document Structure . . . . . . . . . . . . . . . . . . . 8 1.2. Terms and Definitions . . . . . . . . . . . . . . . . . . 10 1.3. Notational Conventions . . . . . . . . . . . . . . . . . 11 2. Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1. Stream Types and Identifiers . . . . . . . . . . . . . . 13 2.2. Sending and Receiving Data . . . . . . . . . . . . . . . 14 2.3. Stream Prioritization . . . . . . . . . . . . . . . . . . 14 2.4. Operations on Streams . . . . . . . . . . . . . . . . . . 15 3. Stream States . . . . . . . . . . . . . . . . . . . . . . . . 15 3.1. Sending Stream States . . . . . . . . . . . . . . . . . . 16 3.2. Receiving Stream States . . . . . . . . . . . . . . . . . 18 3.3. Permitted Frame Types . . . . . . . . . . . . . . . . . . 21 3.4. Bidirectional Stream States . . . . . . . . . . . . . . . 21 3.5. Solicited State Transitions . . . . . . . . . . . . . . . 23 4. Flow Control . . . . . . . . . . . . . . . . . . . . . . . . 24 4.1. Data Flow Control . . . . . . . . . . . . . . . . . . . . 24 4.2. Increasing Flow Control Limits . . . . . . . . . . . . . 25 4.3. Flow Control Performance . . . . . . . . . . . . . . . . 26 4.4. Handling Stream Cancellation . . . . . . . . . . . . . . 27 4.5. Stream Final Size . . . . . . . . . . . . . . . . . . . . 27 4.6. Controlling Concurrency . . . . . . . . . . . . . . . . . 28 5. Connections . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.1. Connection ID . . . . . . . . . . . . . . . . . . . . . . 29 5.1.1. Issuing Connection IDs . . . . . . . . . . . . . . . 31Show full document text