BiDirectional or Server-Initiated HTTP (hybi)

BiDirectional or Server-Initiated HTTP (hybi)
Concluded WG
BiDirectional or Server-Initiated HTTP (hybi)
About
Documents
Meetings
History
Photos
Email expansions
List archive »
Note:
The data for concluded WGs is occasionally incorrect.
WG
Name
BiDirectional or Server-Initiated HTTP
Acronym
hybi
Area
Applications and Real-Time Area
(art)
State
Concluded
Charter
charter-ietf-hybi-02
Approved
Document dependencies
Document
dependencies
Loading...
Pan and zoom the dependency
graph after the layout settles.
Show legend
Loading...
Additional resources
Issue tracker
Wiki
Personnel
Chairs
Gabriel Montenegro
Salvatore Loreto
Area Director
Barry Leiba
Secretary
S Moonesamy
Mailing list
Address
hybi@ietf.org
To subscribe
Archive
Final
Charter for

Working Group
The BiDirectional or Server-Initiated HTTP (HyBi) working group
defines the WebSocket Protocol, a technology for bidirectional
communication between an HTTP client and an HTTP server that
provides greater efficiency than previous approaches (e.g., use
of hanging requests or long polling).

Having completed work on the core protocol (
RFC 6455
), the group
continues to define extensions for use by WebSocket
implementations. The following extensions and optimizations are
currently in scope:

1. A per-frame compression extension to improve bandwidth
usage (
draft-tyoshino-hybi-websocket-perframe-deflate
is a
likely starting point).

2. A multiplexing extension to improve the scalability of the
WebSocket protocol (
draft-tamplin-hybi-google-mux
is a likely
starting point).

3. Timeout-handling capabilities to reduce the chattiness of the
protocol (
draft-thomson-hybi-http-timeout
is a likely starting
point).

The working group will also serve as a discussion venue for
subprotocols. However, no subprotocol is currently chartered as a
deliverable, and the WG must be rechartered to work on any
subprotocols.

The group will not work on an updated version of the WebSocket
protocol, unless it is specifically rechartered to do so.

The group will continue coordinating with the W3C WepApps working
group with respect to the above deliverables and to ensure the best
match possible between the WebSocket protocol and the WebSocket API.
The group will also continue coordinating with other working groups
within the IETF (e.g., HTTPBIS) as appropriate.
Done milestones
Date
Milestone
Associated documents
Done
Send compression extension to IESG for consideration as a Proposed Standard
Done
Issue WG last call on the per-frame compression extension
Done
Adopt a WG item for the per-frame compression extension