[hybi] Proposed charter for HyBi BoF in Hiroshima

Joe Hildebrand <joe.hildebrand@webex.com> Tue, 22 September 2009 06:20 UTC

Return-Path: <Joe.Hildebrand@webex.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id E44283A6891 for <hybi@core3.amsl.com>; Mon, 21 Sep 2009 23:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.929
X-Spam-Status: No, score=-105.929 tagged_above=-999 required=5 tests=[AWL=-0.570, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Vi-BbF5moZUH for <hybi@core3.amsl.com>; Mon, 21 Sep 2009 23:20:11 -0700 (PDT)
Received: from gw2.webex.com (gw2.webex.com []) by core3.amsl.com (Postfix) with SMTP id EEB193A6783 for <hybi@ietf.org>; Mon, 21 Sep 2009 23:20:10 -0700 (PDT)
Received: from SRV-EXSC03.webex.local ([]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 21 Sep 2009 23:21:12 -0700
Received: from ([]) by SRV-EXSC03.webex.local ([]) with Microsoft Exchange Server HTTP-DAV ; Tue, 22 Sep 2009 06:15:47 +0000
User-Agent: Microsoft-Entourage/
Date: Tue, 22 Sep 2009 00:15:46 -0600
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: <hybi@ietf.org>
Message-ID: <C6DDC7B2.143D8%joe.hildebrand@webex.com>
Thread-Topic: Proposed charter for HyBi BoF in Hiroshima
Thread-Index: Aco7TB8rSRNnQlNwyUuSs4BLUk6rLQ==
IM-ID: xmpp:jhildebrand@corp.jabber.com
Presence-ID: xmpp:jhildebrand@corp.jabber.com
Jabber-ID: jhildebrand@corp.jabber.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 22 Sep 2009 06:21:12.0978 (UTC) FILETIME=[E210B720:01CA3B4C]
Subject: [hybi] Proposed charter for HyBi BoF in Hiroshima
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: Tue, 22 Sep 2009 06:20:12 -0000

Please suggest changes, this is just a first draft that tries to capture
several conversations that we've had, including the bar BoF in Stockholm.

Joe Hildebrand


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, the amount of semantic encoded at the HyBi
layer will be minimized, allowing multiple higher-level protocols to take
advantage of the basic eventing mechanism.  These higher-level protocols are
out of scope for the working group, although liaison with other working
groups will be encouraged.

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 HTML5 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.

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