[hybi] design space draft

Jack Moffitt <jack@collecta.com> Mon, 28 June 2010 22:10 UTC

Return-Path: <metajack@gmail.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 7F0023A686B for <hybi@core3.amsl.com>; Mon, 28 Jun 2010 15:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.77
X-Spam-Status: No, score=-0.77 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1YncYMxqaFgr for <hybi@core3.amsl.com>; Mon, 28 Jun 2010 15:09:59 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com []) by core3.amsl.com (Postfix) with ESMTP id 9DD2B3A67CC for <hybi@ietf.org>; Mon, 28 Jun 2010 15:09:56 -0700 (PDT)
Received: by qwe5 with SMTP id 5so1785691qwe.31 for <hybi@ietf.org>; Mon, 28 Jun 2010 15:09:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=VRwlARseOo0KQINEmNU+LEz+dOqEbw8x/zhe2Cf64IU=; b=p6eo7coJ27MQ72RfwbEN6hvTwRGWeqbATpxq7G9kMp2SvP0LeE8e2t/+5q3Jc6tN2E SuEdkw0VgEHOo4PUDZP8GBGxPg4Ax2gJW1oZ/hrdd8lmKdjelfZ4t04E/KrhXgGoRuSu D5J24fDLxCC1Q8FnY3o7a2nbTCxB1cUadco/s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=niYsFnnrsgmrk/lKxtgjCaGdnSbs9F4pIttGY/daaW3WFiPvQsCDkeIuQkx/5kpnrn bJspcmjPRqmTosnaj3ej2V/OlGLo46EWfNO1+hkPyYb+rFkxwZIf+PuEBNNy5ocR2qMi smUwsbkFgI/jrweJMhcsGsuoVAaYay2opaQr4=
MIME-Version: 1.0
Received: by with SMTP id v4mr3901449qae.165.1277762999090; Mon, 28 Jun 2010 15:09:59 -0700 (PDT)
Sender: metajack@gmail.com
Received: by with HTTP; Mon, 28 Jun 2010 15:09:59 -0700 (PDT)
Date: Mon, 28 Jun 2010 16:09:59 -0600
X-Google-Sender-Auth: dQHiwCO1oidU928PgCq22u3MahE
Message-ID: <AANLkTinnJmYf3bXX2GnjlL-MjFAn3asv38jLrEHd1hC_@mail.gmail.com>
From: Jack Moffitt <jack@collecta.com>
To: hybi@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [hybi] design space draft
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: Mon, 28 Jun 2010 22:10:00 -0000

I just published the initial version of the design space draft:

       Title           : Design Space for Bidirectional Protocols
       Author(s)       : J. Moffitt, et al.
       Filename        : draft-ietf-hybi-design-space-00.txt
       Pages           : 9
       Date            : 2010-06-28

This draft outlines the issues and protocols that make up the general
design area of the bi-directional web.

There are a few changes from the previous version:

* I expanded on the restrictions that browser-based clients have,
including for example the fact that JavaScript has no real ability for
working with binary as anything other than blobs.
* I filled out the security considerations section with the few things
I could think of that affect current protocols. Please let me know if
there are more that I should add.
* Most areas in the previous version that were left unfinished have
been filled in (mostly examples of the various kinds of clients).

I think it would be good to get some feedback on the restrictions
placed on the protocol due to JavaScript runtimes, as I suspect these
will be important for future discussions.

Also, Julien already pointed out to me that I am referencing the wrong
document for the WebSocket protocol. I will make sure this is
corrected in the next version.