Version-Independent Properties of QUIC
draft-ietf-quic-invariants-06

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06

QUIC                                                          M. Thomson
Internet-Draft                                                   Mozilla
Intended status: Standards Track                           July 10, 2019
Expires: January 11, 2020

                 Version-Independent Properties of QUIC
                     draft-ietf-quic-invariants-06

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), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-invariants [3].

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 11, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Thomson                 Expires January 11, 2020                [Page 1]
Internet-Draft               QUIC Invariants                   July 2019

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  An Extremely Abstract Description of QUIC . . . . . . . . . .   3
   4.  QUIC Packet Headers . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Long Header . . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Short Header  . . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  Connection ID . . . . . . . . . . . . . . . . . . . . . .   5
     4.4.  Version . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Version Negotiation . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security and Privacy Considerations . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Incorrect Assumptions  . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   In addition to providing secure, multiplexed transport, QUIC
   [QUIC-TRANSPORT] includes the ability to negotiate a version.  This
   allows the protocol to change over time in response to new
   requirements.  Many characteristics of the protocol will 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.

   The primary goal of this document is to ensure that it is possible to
   deploy new versions of QUIC.  By documenting the properties that
   can't change, this document aims to preserve the ability to change
   any other aspect of the protocol.  Thus, unless specifically
   described in this document, any aspect of the protocol can change
   between different versions.

Thomson                 Expires January 11, 2020                [Page 2]
Internet-Draft               QUIC Invariants                   July 2019

   Appendix A is a non-exhaustive list of some incorrect assumptions
   that might be made based on knowledge of QUIC version 1; these do not
   apply to every version of QUIC.

2.  Conventions and Definitions