[hybi] updated Charter proposal

Salvatore Loreto <salvatore.loreto@ericsson.com> Wed, 21 October 2009 08:38 UTC

Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94D0B3A6860 for <hybi@core3.amsl.com>; Wed, 21 Oct 2009 01:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.994
X-Spam-Level:
X-Spam-Status: No, score=-4.994 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dqv4F4N0DzdS for <hybi@core3.amsl.com>; Wed, 21 Oct 2009 01:38:36 -0700 (PDT)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 36DEE3A67EB for <hybi@ietf.org>; Wed, 21 Oct 2009 01:38:36 -0700 (PDT)
X-AuditID: c1b4fb24-b7bd7ae000002270-8b-4adec8938778
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw5.ericsson.se (Symantec Mail Security) with SMTP id CE.08.08816.398CEDA4; Wed, 21 Oct 2009 10:38:43 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Oct 2009 10:34:43 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Oct 2009 10:34:41 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 736312870 for <hybi@ietf.org>; Wed, 21 Oct 2009 11:34:41 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3F20921A22 for <hybi@ietf.org>; Wed, 21 Oct 2009 11:34:41 +0300 (EEST)
Received: from localhost.localdomain (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id E810221A21 for <hybi@ietf.org>; Wed, 21 Oct 2009 11:34:40 +0300 (EEST)
Message-ID: <4ADEC7A0.7040307@ericsson.com>
Date: Wed, 21 Oct 2009 11:34:40 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090825)
MIME-Version: 1.0
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 21 Oct 2009 08:34:41.0697 (UTC) FILETIME=[559D0110:01CA5229]
X-Brightmail-Tracker: AAAAAA==
Subject: [hybi] updated Charter proposal
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 08:38:37 -0000

Hi there,

here a new/updated version of the charter proposal for HyBi wg.
This version includes all the suggestions and comments received in the 
the list discussion.

please provide comments!

Best Regards
Salvatore Loreto



Proposed Charter for HyBi WG (rev.2)
Last Updated: 2009-10-21
-----------------------------------------------

Chairs:
* TBD
* TBD

Applications Area Director(s):
* Lisa Dusseault <lisa.dusseault@gmail.com>
* Alexey Melnikov <alexey.melnikov@isode.com>

Applications Area Advisor:
* Lisa Dusseault <lisa.dusseault@gmail.com>

Mailing Lists:
General Discussion: hybi@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/hybi
Archive: http://www.ietf.org/mail-archive/web/hybi/current/maillist.html

Description of Working Group:
HTTP has in the past been used as a request/response protocol most often,
leading to clients polling for new data or users hitting the refresh button
in their browsers.  Newer web applications are finding ways to push data
from the server to the client as soon as it is available, through a variety
of mechanisms.  The Hypertext-Bidirectional (HyBi) working group will seek
standardization of approaches that HTTP clients, servers, and intermediate
boxes can use to communicate with one another in both directions.

Since any modification of the web infrastructure may take a good amount of
time to be deployed, outputs of the working group will include both short
and long term solutions.  The existing web being much more complicated than
it seems, the working group will prioritize the characterization of the
design space, including the web clients, intermediaries, firewalls, NATs,
web servers, etc. into which both solutions will need to be deployed.

For both short and long term work items, a general approach is preferred,
with abstract semantics that can apply to a large number of applications.

The short term approach will be deployable on today's Internet, across
whichever current or historical web browsers the working group decides 
upon.
Although wide browser support is a goal, lack of support on any single
browser version will not be a sufficient cause to block consensus.  The
short term approach may also define hints to allow newer intermediaries to
optimize traffic.

In the long term, new features will be required of clients, servers, or
intermediaries allowing a more scalable and robust end-to-end experience.

Although multiple protocols exist as starting points for both the short and
long term, backward compatibility with these protocols is not a 
requirement.
In particular, the working group will liaison with the WebApps working 
group
of the W3C around the Websockets protocol; if agreed by both parties, the
HyBi working group may take over the development of the Websockets 
protocol.

Wide browser support is a goal for long term solution, however the solution
should also be suitable for clients other than Web Browser. The Working 
Group
will work to standardize a generic solution that can work in all the 
environments
and elements of the web infrastructure (e.g. web browser, generic HTTP 
client,
web server, intermediaries, etc.) and it is not specific for just one.

The Working Group should consider:
* Implementer experience
* Impact on existing implementations and deployments
* Ability to achieve broad implementation
* Ability to address broader use cases than may be contemplated by the
original authors

The Working Group will produce one or more documents suitable for
consideration as Proposed Standard that will:
* Define requirements for short- and long-term solutions, including
characterization of the design space
* Define a short-term solution for the bi-directional web, deployable on
today's Internet
* Define a long-term solution for the bi-directional web, which will likely
require modifications to the web infrastructure


Goals and Milestones:
---------------------
Mar-2010:  WGLC on the Design Space characterization (Informational)
Mar-2010:  WGLC on Requirements document on Short term solution
Mar-2010:  WGLC on Requirements document on Long term solution
May-2010:  Requirements to IESG
Mar-2011:  WGLC on Short term solution improvements
May-2011:  WGLC on Long term solution protocol