Version-Independent Properties of QUIC
draft-ietf-quic-invariants-11
QUIC M. Thomson
Internet-Draft Mozilla
Intended status: Standards Track 25 September 2020
Expires: 29 March 2021
Version-Independent Properties of QUIC
draft-ietf-quic-invariants-11
Abstract
This document defines the properties of the QUIC transport protocol
that are expected to remain unchanged over time as new versions of
the protocol are developed.
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/-invariants.
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 29 March 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Thomson Expires 29 March 2021 [Page 1]
Internet-Draft QUIC Invariants September 2020
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. An Extremely Abstract Description of QUIC . . . . . . . . . . 2
2. Fixed Properties of All QUIC Versions . . . . . . . . . . . . 2
3. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
4. Notational Conventions . . . . . . . . . . . . . . . . . . . 3
5. QUIC Packets . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Long Header . . . . . . . . . . . . . . . . . . . . . . . 4
5.2. Short Header . . . . . . . . . . . . . . . . . . . . . . 5
5.3. Connection ID . . . . . . . . . . . . . . . . . . . . . . 6
5.4. Version . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Version Negotiation . . . . . . . . . . . . . . . . . . . . . 6
7. Security and Privacy Considerations . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Incorrect Assumptions . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. An Extremely Abstract Description of QUIC
QUIC is a connection-oriented protocol between two endpoints. Those
endpoints exchange UDP datagrams. These UDP datagrams contain QUIC
packets. QUIC endpoints use QUIC packets to establish a QUIC
connection, which is shared protocol state between those endpoints.
2. Fixed Properties of All QUIC Versions
In addition to providing secure, multiplexed transport, QUIC
[QUIC-TRANSPORT] allows for the option to negotiate a version. This
allows the protocol to change over time in response to new
requirements. Many characteristics of the protocol could change
between versions.
This document describes the subset of QUIC that is intended to remain
stable as new versions are developed and deployed. All of these
invariants are IP-version-independent.
Thomson Expires 29 March 2021 [Page 2]
Internet-Draft QUIC Invariants September 2020
The primary goal of this document is to ensure that it is possible to
deploy new versions of QUIC. By documenting the properties that
cannot change, this document aims to preserve the ability for QUIC
endpoints to negotiate changes to any other aspect of the protocol.
Show full document text