Re: [hybi] requirement draft as wg item

Greg Wilkins <gregw@webtide.com> Thu, 13 May 2010 13:21 UTC

Return-Path: <gregw@webtide.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 289F73A6B3A for <hybi@core3.amsl.com>; Thu, 13 May 2010 06:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.413
X-Spam-Level:
X-Spam-Status: No, score=-0.413 tagged_above=-999 required=5 tests=[AWL=-0.228, BAYES_40=-0.185]
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 XAsRYx3ahMF8 for <hybi@core3.amsl.com>; Thu, 13 May 2010 06:21:28 -0700 (PDT)
Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by core3.amsl.com (Postfix) with ESMTP id B8D5F3A6B29 for <hybi@ietf.org>; Thu, 13 May 2010 06:18:47 -0700 (PDT)
Received: by wyg36 with SMTP id 36so737890wyg.27 for <hybi@ietf.org>; Thu, 13 May 2010 06:18:34 -0700 (PDT)
Received: by 10.227.151.66 with SMTP id b2mr8533084wbw.158.1273756714610; Thu, 13 May 2010 06:18:34 -0700 (PDT)
Received: from [192.168.0.100] (host116-234-static.43-88-b.business.telecomitalia.it [88.43.234.116]) by mx.google.com with ESMTPS id z33sm8925816wbd.1.2010.05.13.06.18.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 13 May 2010 06:18:33 -0700 (PDT)
Message-ID: <4BEBFC26.6060203@webtide.com>
Date: Thu, 13 May 2010 15:18:30 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: "hybi@ietf.org" <hybi@ietf.org>
References: <4BE972C5.4060006@ericsson.com> <AANLkTil_SAqnOPlL4c1TzAS5NSnQe0AJq91tGuWeWXJA@mail.gmail.com>
In-Reply-To: <AANLkTil_SAqnOPlL4c1TzAS5NSnQe0AJq91tGuWeWXJA@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] requirement draft as wg item
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: Thu, 13 May 2010 13:21:29 -0000

Mike Belshe wrote:
> A few questions:
> * Does requirement 1, stating the WebSocket must run on top of a
> transport protocol inhibit use of WebSockets on top of any other
> protocols like SPDY? Is that an intended consequence?

I think there is a lot of confusion between websockets the wire protocol
and websockets the browser feature.

I think it would make little sense to carry websockets the protocol
over SPDY, but a lot sense to carry websockets the browser feature
over SPDY.

I've previously suggested that we name the protocol WSTP for
Websocket Transport Protocol, so that it would be much clearer
when we are talking about the browser feature and when we are talking
about the wire protocol.


However, I think that REQ.1 could be better phrased.   Maybe something
like: The WebSocket Protocol MUST rund directly on top of TCP or
equivalent transport mechanism ?


> * Requirement 11 refers to a "sub-protocol", but "sub-protocol" is not
> defined. I am not meaning to be difficult, but I am not sure what does
> or does not qualify as as sub-protocol.

I agree and I also don't yet understand exactly what we all mean by
subprotocol

I'm not even sure there is a requirement for subprotocols.  It might
just be a nice to have feature of a particular solution.


regards