Here are some WebSocket extensions being planned by the hybi working group.
Probably something we'll want to keep in sync with.
-------- Original Message --------
Subject: [hybi] New charter for HyBi wg
Date: Wed, 18 Jan 2012 16:21:13 +0100
From: Salvatore Loreto <salvatore.loreto_at_ericsson.com>
To: hybi_at_ietf.org <hybi_at_ietf.org>
converted from rtf
Hi there,
as you know
the WebSocket Protocol has been published on December 2011 as RFC 6455.
Thanks again to all of you for all your technical and editorial
contributions to the design of the protocol.
Now having completed the work on the core protocol, we are ready as a
group to continue the discussion
to define extensions for use by WebSocket implementations.
Gabriel and I have worked on a draft of the new charter for the HyBi wg
that is focused
on the main extensions that have already been discussed by the WG last year.
(See the charter below)
Please let we know your opinion on the draft.
All the feedback, suggestions and proposal are really welcome.
New Charter
------------------
Description of 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. Define a per-frame compression extension to improve the
bandwidth usage.
2. Define a multiplexing extension to improve the scalability of
the WebSocket protocol
3. Define timeout-handling capabilities to reduce the chattiness of
the protocol
The working group will also serve as a discussion forum for
subprotocols.
However, no subprotocol is currently chartered as official WG item.
The HyBi working group will continue its liaison 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 WG will also continue coordinating with other WGs
within the IETF (e.g., HTTPbis)
as appropriate.
Goal and Milestones:
May 2012 - Issue WG last call on the per-frame compression extension
Jun 2012 - Send per-frame compression extension to IESG for
publication as Proposed Standard
Aug 2012 - Issue WG last call on timeout handling
Sep 2012 - Issue WG last call on the multiplexing extension
Oct 2012 - Send timeout handling to IESG for publication as
Proposed Standard
Nov 2012 - Send Multiplexing extension to IESG for publication as
Proposed Standard
best regards
Salvatore Loreto
_www.sloreto.com_