WebTransport over HTTP/3
draft-vvv-webtransport-http3-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 HTTP/3
                    draft-vvv-webtransport-http3-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
   Http3Transport, a WebTransport protocol that is based on HTTP/3
   [HTTP3] and provides support for unidirectional streams,
   bidirectional streams and datagrams, all multiplexed within the same
   HTTP/3 connection.

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               Http3Transport                     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.  Session IDs . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Session Establishment . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Establishing a Transport-Capable HTTP/3 Connection  . . .   4
     4.2.  Extended CONNECT in HTTP/3  . . . . . . . . . . . . . . .   4
     4.3.  Creating a New Session  . . . . . . . . . . . . . . . . .   5
     4.4.  Limiting Number of Simultaneous Sessions  . . . . . . . .   5
   5.  WebTransport Features . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Unidirectional streams  . . . . . . . . . . . . . . . . .   6
     5.2.  Client-Initiated Bidirectional Streams  . . . . . . . . .   6
     5.3.  Server-Initiated Bidirectional Streams  . . . . . . . . .   7
     5.4.  Datagrams . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Session Termination . . . . . . . . . . . . . . . . . . . . .   8
   7.  Transport Properties  . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Upgrade Token Registration  . . . . . . . . . . . . . . .   9
     9.2.  QUIC Transport Parameter Registration . . . . . . . . . .   9
     9.3.  Frame Type Registration . . . . . . . . . . . . . . . . .  10
     9.4.  Stream Type Registration  . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   HTTP/3 [HTTP3] is a protocol defined on top of QUIC [QUIC-TRANSPORT]
   that can provide multiplexed HTTP requests within the same QUIC
   connection.  This document defines Http3Transport, a mechanism for
   embedding arbitrary streams of non-HTTP data into HTTP/3 in a manner
   that it can be used within WebTransport model [OVERVIEW].  Using the
   mechanism described here, multiple Http3Transport can be transmitted
   simultaneously with regular HTTP traffic on the same HTTP/3
   connection.

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
Show full document text