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

Document Type Active Internet-Draft (individual)
Last updated 2019-11-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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                        November 2, 2019
Expires: May 5, 2020

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

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]
   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 May 5, 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

Vasiliev                   Expires May 5, 2020                  [Page 1]
Internet-Draft                QuicTransport                November 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 . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Connection Establishment  . . . . . . . . . . . . . . . . . .   4
     3.1.  Identifying as QuicTransport  . . . . . . . . . . . . . .   4
     3.2.  Client Indication . . . . . . . . . . . . . . . . . . . .   4
       3.2.1.  Origin Field  . . . . . . . . . . . . . . . . . . . .   5
       3.2.2.  Path Field  . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  0-RTT . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Streams . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Datagrams . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  QuicTransport URI Scheme  . . . . . . . . . . . . . . . . . .   6
   7.  Transport Properties  . . . . . . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  ALPN Value Registration . . . . . . . . . . . . . . . . .   9
     9.2.  Client Indication Fields Registry . . . . . . . . . . . .   9
     9.3.  URI Scheme Registration . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
     10.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   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]
   connection and provides support for unidirectional streams,
   bidirectional streams and datagrams.

   QUIC [QUIC] 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, a protocol conforming to the
   WebTransport protocol framework.  QuicTransport is an application
   protocol running directly over QUIC.  The protocol is designed to
   have low implementation overhead on the server side, meaning that
Show full document text