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

Document Type Active Internet-Draft (individual)
Last updated 2017-03-29
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: September 30, 2017                               March 29, 2017

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

Abstract

   This document defines a general purpose message framing named WiSH
   which supports bi-directional message-based communication over byte-
   stream oriented protocols such as HTTP (in its standard semantics).
   The WiSH framing is designed to be compatible with WebSocket.  You
   may want to think about WiSH as a binary and bi-directional
   alternative to the framing defined for the server-sent events [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 September 30, 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 September 30, 2017               [Page 1]
Internet-DraWiSH: A General Purpose Message Framing over Byt  March 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  . . . . . . . . . .   4
   4.  WiSH Protocol . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Framing . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Using WiSH over HTTP  . . . . . . . . . . . . . . . . . . . .   5
   7.  Content Negotiation and WebSocket Compatibility Consideration   5
     7.1.  Subprotocol Negotiation . . . . . . . . . . . . . . . . .   6
     7.2.  Compression Negotiation . . . . . . . . . . . . . . . . .   7
     7.3.  Valid UTF-8 Requirement . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Non-normative References  . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

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

   WiSH is a message framing format for use over the standard HTTP
   semantics to provide bi-directional messaging semantics.  WiSH stands
   for Web in Strict HTTP.  The communication protocol providing the
   HTTP semantics can be HTTP/1.1 [RFC7231], HTTP/2 [RFC7540], HTTP/2 +
   QUIC [QUIC], or any future protocols.  Wire-protocol functionalities
   such as compression, 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 proxy chooses to buffer or reject earlier 2xx
   responses.  Since proxies may buffer response bodies, communication
   over WiSH may experience extra latency compared to WebSocket.  When
   HTTPS is used, response buffering by proxies is less likely to
Show full document text