WebTransport over QUIC
draft-vvv-webtransport-quic-00

Document Type Active Internet-Draft (individual)
Last updated 2019-05-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                        V. Vasiliev
Internet-Draft                                                    Google
Intended status: Standards Track                             May 3, 2019
Expires: November 4, 2019

                         WebTransport over QUIC
                     draft-vvv-webtransport-quic-00

Abstract

   WebTransport [OVERVIEW] is a protocol framework that enables clients
   constrained by the Web security model to communicate with a remote
   server using a secure multiplexed transport.  This document describes
   QuicTransport, a transport protocol that uses a dedicated QUIC
   [QUIC-TRANSPORT] connection and provides support for unidirectional
   streams, bidirectional streams and datagrams.

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 November 4, 2019.

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

Vasiliev                Expires November 4, 2019                [Page 1]
Internet-Draft                QuicTransport                     May 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Connection Establishment  . . . . . . . . . . . . . . . . . .   3
     3.1.  Identifying as QuicTransport  . . . . . . . . . . . . . .   3
     3.2.  Verifying the Origin  . . . . . . . . . . . . . . . . . .   3
     3.3.  0-RTT . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Streams . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Datagrams . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Transport Properties  . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  ALPN Value Registration . . . . . . . . . . . . . . . . .   6
     8.2.  QUIC Transport Parameter Registration . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   QUIC [QUIC-TRANSPORT] is a UDP-based multiplexed secure transport.
   It is the underlying protocol for HTTP/3 [I-D.ietf-quic-http], and as
   such is reasonably expected to be available in web browsers and
   server-side web frameworks.  This makes it a compelling transport to
   base a WebTransport protocol on.

   This document defines QuicTransport, an adaptation of QUIC to
   WebTransport model.  The protocol is designed to be low-overhead on
   the server side, meaning that server software that already has a
   working QUIC implementation available would not require a large
   amount of code to implement QuicTransport.  Where possible,
   WebTransport concepts are mapped directly to the corresponding QUIC
   concepts.

1.1.  Terminology

   The keywords "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.

Vasiliev                Expires November 4, 2019                [Page 2]
Internet-Draft                QuicTransport                     May 2019

   This document follows terminology defined in Section 1.2 of
   [OVERVIEW].

2.  Protocol Overview
Show full document text