Bootstrapping WebSockets with HTTP/2
draft-mcmanus-httpbis-h2-websockets-01

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

• Versions
• 00
• 01
• 02

Network Working Group                                         P. McManus
Internet-Draft                                                   Mozilla
Intended status: Standards Track                        October 26, 2017
Expires: April 29, 2018

                  Bootstrapping WebSockets with HTTP/2
                 draft-mcmanus-httpbis-h2-websockets-01

Abstract

   This document defines a mechanism for running the WebSocket Protocol
   [RFC6455] over a single stream of an HTTP/2 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 April 29, 2018.

Copyright Notice

   Copyright (c) 2017 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

McManus                  Expires April 29, 2018                 [Page 1]
Internet-Draft                     I-D                      October 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The ENABLE_CONNECT_PROTOCOL SETTINGS Parameter  . . . . . . .   3
   4.  The Extended CONNECT Method . . . . . . . . . . . . . . . . .   3
   5.  Using Extended CONNECT To Bootstrap The WebSocket Protocol  .   4
     5.1.  Connection Preamble . . . . . . . . . . . . . . . . . . .   5
       5.1.1.  Version Type  . . . . . . . . . . . . . . . . . . . .   5
       5.1.2.  Subprotocol Type  . . . . . . . . . . . . . . . . . .   5
       5.1.3.  Extensions Type . . . . . . . . . . . . . . . . . . .   6
       5.1.4.  Origin Type . . . . . . . . . . . . . . . . . . . . .   6
       5.1.5.  End-Preamble Type . . . . . . . . . . . . . . . . . .   6
     5.2.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Design Considerations . . . . . . . . . . . . . . . . . . . .   8
   7.  About Intermediaries  . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The Hypertext Transfer Protocol (HTTP) provides compatible resource
   level semantics across different versions but it does not offer
   compatibility at the connection management level.  Other protocols,
   such as WebSockets, that rely on connection management details of
   HTTP must be updated for new versions of HTTP.

   The WebSocket Protocol [RFC6455] uses the HTTP/1.1 [RFC7230] Upgrade
   mechanism to transition a TCP connection from HTTP into a WebSocket
   connection.  A different approach must be taken with HTTP/2
   [RFC7540].  The multiplexing nature of HTTP/2 does not allow
   connection wide header and status codes such as the Upgrade and
   Connection request headers or the 101 response code due to its
   multiplexing nature.  These are all required by the [RFC6455]
   connection establishment process.

   Being able to bootstrap WebSockets from HTTP/2 allows one TCP
   connection to be easily shared by both protocols and extends HTTP/2's
   more efficient use of the network to WebSockets.

   This document extends the HTTP/2 CONNECT method.  The extension
   allows the substitution of a new protocol name to connect to rather
   than the external host normally used by CONNECT.  The result is a
   tunnel on a single HTTP/2 stream that can carry data for WebSockets

McManus                  Expires April 29, 2018                 [Page 2]
Internet-Draft                     I-D                      October 2017

   (or any other protocol).  The other streams on the connection may