%% You should probably cite draft-hirano-httpbis-websocket-over-http2-01 instead of this revision.
@techreport{hirano-httpbis-websocket-over-http2-00,
    number =    {draft-hirano-httpbis-websocket-over-http2-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hirano-httpbis-websocket-over-http2/00/},
    author =    {Yutaka Hirano},
    title =     {{WebSocket over HTTP/2.0}},
    pagetotal = 17,
    year =      2014,
    month =     feb,
    day =       14,
    abstract =  {The WebSocket protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. Since it requires one TCP connection for every WebSocket connection, having multiple WebSocket connections between the same client and the same server is inefficient. On the other hand, HTTP/2.0 specifies a fast, secure, multiplexed framing protocol. This document provides bi- directional multiplexed communication by layering WebSocket on top of HTTP/2.0. Please send feedback to the ietf-http-wg@w3.org mailing list.},
}