An HTTP/2 extension for bidirectional messaging communication
draft-xie-bidirectional-messaging-01

Document Type Active Internet-Draft (individual)
Last updated 2019-04-04
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)
httpbis Working Group                                             G. Xie
Internet-Draft                                               F. Frindell
Intended status: Standards Track                           Facebook Inc.
Expires: 6 October 2019                                     4 April 2019

     An HTTP/2 extension for bidirectional messaging communication
                  draft-xie-bidirectional-messaging-01

Abstract

   This draft proposes a http2 protocol extension, which enables
   bidirectional messaging communication between client and server.

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 6 October 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 the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Xie & Frindell           Expires 6 October 2019                 [Page 1]
Internet-Draft           bidirectional messaging              April 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   2
   3.  Solution Overview . . . . . . . . . . . . . . . . . . . . . .   3
       3.1.  Routing Stream and ExStream . . . . . . . . . . . . . .   3
       3.2.  Bidirectional Messaging Communication . . . . . . . . .   3
       3.3.  States of RStream and ExStream  . . . . . . . . . . . .   4
       3.4.  Negotiate the Extension through SETTINGS frame  . . . .   5
       3.5.  Interaction with standard http2 features  . . . . . . .   5
   4.  HTTP2 EX_HEADERS Frame  . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
       5.1.  FRAME TYPE Registry . . . . . . . . . . . . . . . . . .   6
       5.2.  Settings Registry . . . . . . . . . . . . . . . . . . .   6
       5.3.  Error Code Registry . . . . . . . . . . . . . . . . . .   7
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   HTTP/2 is the de facto application protocol in Internet.  The
   optimizations developed in HTTP/2, like stream multiplexing, header
   compression, and binary message framing are very generic.  They can
   be useful in non web browsing applications, for example, Publish/
   Subscribe, RPC.  However, the request/response from client to server
   communication pattern limits HTTP/2 from wider use in these
   applications.  This draft proposes a HTTP/2 protocol extension, which
   enables bidirectional messaging between client and server.

   The only mechanism HTTP/2 provides for server to client communication
   is PUSH_PROMISE.  While this satisfies some use-cases, it is
   unidirectional, i.g. the client cannot respond.  In this draft, a new
   frame is introduced which has the routing properties of PUSH_PROMISE
   and the bi-directionality of HEADERS.  Further, clients are also able
   group streams together for routing purposes, such that each
   individual stream does not need to carry additional routing
   information.

2.  Conventions and Terminology

   The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
   SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
   document, are to be interpreted as described in [RFC2119].

   All the terms defined in the Conventions and Terminology section in
   [RFC7540] apply to this document.

Xie & Frindell           Expires 6 October 2019                 [Page 2]
Internet-Draft           bidirectional messaging              April 2019

3.  Solution Overview

3.1.  Routing Stream and ExStream

   A routing stream (RStream) is a long lived HTTP/2 stream in nature.
   RStreams are initiated by clients, and can be routed independently by
Show full document text