WiSH: A General Purpose Message Framing over Byte-Stream Oriented Wire Protocols (HTTP)
draft-yoshino-wish-03

Document Type Active Internet-Draft (individual)
Last updated 2017-05-10
Stream (None)
Intended RFC status (None)
Formats plain text 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                                         T. Yoshino
Internet-Draft                                                    W. Zhu
Intended status: Standards Track                            Google, Inc.
Expires: November 11, 2017                                  May 10, 2017

 WiSH: A General Purpose Message Framing over Byte-Stream Oriented Wire
                            Protocols (HTTP)
                         draft-yoshino-wish-03

Abstract

   This document defines a general purpose message framing named WiSH
   which supports bi-directional (bidi) message-based communication over
   byte-stream oriented protocols such as HTTP (in its standard
   semantics).  WiSH is designed to be compatible with WebSocket.  WiSH
   can be viewed as a binary and bidi alternative to the framing defined
   for the server-sent events (SSE, EventSource) Web API [SSE].

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 http://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 11, 2017.

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
   (http://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

Yoshino & Zhu           Expires November 11, 2017               [Page 1]
Internet-DrWiSH: A General Purpose Message Framing over Byte-   May 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Conformance Requirements and Terminology  . . . . . . . . . .   3
   4.  WiSH Protocol . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Framing . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Using WiSH over HTTP  . . . . . . . . . . . . . . . . . . . .   5
   7.  WebSocket Compatibility Consideration . . . . . . . . . . . .   5
     7.1.  Valid UTF-8 Requirement . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Non-normative References  . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The WebSocket protocol was proposed to provide native client-server
   bidi messaging for the Web.  It has been implemented and deployed
   widely, but there are still missing semantics and features.  See
   [BidiwebSurvey].

   WiSH is a general purpose message framing for use over the standard
   HTTP semantics to provide bidi messaging semantics.  WiSH stands for
   Web in Strict HTTP.

   The communication protocol providing the standard HTTP semantics can
   be HTTP/1.1 [RFC7231], HTTP/2 [RFC7540], HTTP/2 + QUIC [QUIC], or any
   future protocols.  Wire protocol features such as multiplexing,
   session priority, etc. are provided by the underlying protocol
   [TransportAbstraction].  Unlike HTTP/2, HTTP/1.1 doesn't specify if
   earlier 2xx responses are allowed [RFC7540].  Therefore, when
   HTTP/1.1 is used as the underlying protocol, full-duplex
   communication may be broken if the client, server or any intermediary
   chooses to buffer or reject earlier 2xx responses.  Since
   intermediaries may buffer response bodies, bidi communication over
   WiSH may experience extra latency compared to WebSocket.  When HTTPS
   is used, response body buffering by intermediaries is less likely to
   happen.

   The wire protocol features of WebSocket, such as handshake or control
   messages, are all dropped.  WiSH respects the semantics of the
Show full document text