Re: [hybi] comments on draft-ietf-hybi-websocket-requirements-00

gabriel montenegro <g_e_montenegro@yahoo.com> Sat, 10 July 2010 01:30 UTC

Return-Path: <g_e_montenegro@yahoo.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 07AAF3A6949 for <hybi@core3.amsl.com>; Fri, 9 Jul 2010 18:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 xqm2b9N6Gzbp for <hybi@core3.amsl.com>; Fri, 9 Jul 2010 18:30:12 -0700 (PDT)
Received: from web82607.mail.mud.yahoo.com (web82607.mail.mud.yahoo.com [68.142.201.124]) by core3.amsl.com (Postfix) with SMTP id 9A0423A6925 for <hybi@ietf.org>; Fri, 9 Jul 2010 18:30:09 -0700 (PDT)
Received: (qmail 66218 invoked by uid 60001); 10 Jul 2010 01:30:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278725411; bh=Olm1z935MtkSALFcqSAj2AuRjEZvU11wEih1sADLVeE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=2cJSOG8FI8bP3MSn/AHsBqhYlCCuK725wnAzhjapBWvdb4xaoZ2FHW/L3l5FnzPHj3j6bUqI57TsRf7UQdytB+b6o6lNm7oboVO6UErgRfmixmrhnSbWrI4FW8xaGuq4AsF5mcIso0J24LJ5L/qLnv9PCrrfT/mTaHcAqz5kXHk=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qcIP9XQq4EtkToc28yR3o/CQcTz6pUXLOfFT+ocqN+S7dTxo7NPUednQ9UsFEoY9rjXWxIsDB/sPL/Ks17d9yrD3ltPI+VmlMrbGEe2TDdM4sr3pLw//FQgkQN/GHWFW0ZuSHwE3REo59qIHQfBWMkOJTdyr+/Su7wmfj1cswvc=;
Message-ID: <564970.65690.qm@web82607.mail.mud.yahoo.com>
X-YMail-OSG: Iz3h.gIVM1lbeM6LSReSYuLQWPabSWRJ6RhGNgAUAQAA4da N8JLbs2eZyr2fIKavxbVAq4HXCDdT2NMWFI.NDleT3TjCoc.Cm9s0oxv20Ff XWByb65ch7nlfasq.i0jrBlJ4uaWrUdZ.Yuu5pSbFCfGUBA1LVUCWdGijemH bPZax5ip_LXSLjVR3ZsdE0O4EOlpqofffhJ5O84qXr6Ok8T7EGgXP_ffh2Dz 4xt09V3zNe5owvsq406l8PiaQRDGmOEDrx4QUUTLoKwvkE4JNxJZGpxMXeMA nJwKo3L3Oa5IvuOFcR0Fal4ogIVcfP5_kynFttchAW.IXEk2z4G9njDuxfmd DdvxO6iVgKTPwRTzIfzVa4_ZDlA--
Received: from [131.107.0.78] by web82607.mail.mud.yahoo.com via HTTP; Fri, 09 Jul 2010 18:30:10 PDT
X-Mailer: YahooMailRC/397.8 YahooMailWebService/0.8.104.274457
References: <615374.65181.qm@web82607.mail.mud.yahoo.com> <op.vfj9vfna64w2qv@annevk-t60>
Date: Fri, 09 Jul 2010 18:30:10 -0700
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Anne van Kesteren <annevk@opera.com>, hybi@ietf.org
In-Reply-To: <op.vfj9vfna64w2qv@annevk-t60>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [hybi] comments on draft-ietf-hybi-websocket-requirements-00
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: Sat, 10 Jul 2010 01:30:21 -0000

Hi Anne,

please see my comments inline...



> On Thu, 08 Jul 2010 20:20:15 +0200, gabriel montenegro <> ymailto="mailto:g_e_montenegro@yahoo.com" 
> href="mailto:g_e_montenegro@yahoo.com">g_e_montenegro@yahoo.com> 
> wrote:
>    identified both in the HyBi wg input 
> document
>    [I-D.hixie-thewebsocketprotocol] and in the HyBi 
> mailing list
>    dicussion.
>    REQ. 1:  
> The WebSocket Protocol MUST run directly on top of a
>      
> transport protocol (e.g.  TCP, UDP or SCTP, DCCP).
> ---
> No 
> need to say anything, as the point is that whatever HTTP was
> running 
> over should continue to be used after the upgrade. Typically
> this is 
> TCP, yes. So how about rewording thus:
>    REQ. 1:  The 
> WebSocket Protocol MUST run directly on top of
>      the 
> transport over which the initial HTTP handshake was running
>    
>   (typically TCP).

I think the requirement should be removed then. 
> The requirements shouldn't constrain us to a HTTP handshake.


[gm] Hmmm... I was under the impression that the whole point was to 
start with HTTP and then via the Upgrade directive move into the
WebSocket protocol. Or are you saying that there might be other ways
to start other than HTTP?

> 
> ---
>    REQ. 2:  The WebSocket Protocol MUST be able to 
> handle (send and
>      receive) messages on top of a TCP 
> data stream connection.
> ---
> Suggest rewording:
>  
>   REQ. 2:  The WebSocket Protocol MUST be able to handle (send 
> and
>      receive) messages up to a maximum size (TBD) on 
> top of the transport
>      over which the initial HTTP 
> handshake was running (typically TCP).

Why should we constrain size in 
> the requirements?

[gm] Please see my response to Greg's message.

>    REQ. 11:  The WebSocket 
> Client MUST be able to request the server,
>      during 
> the handshake, to use a specific WebSocket sub-protocol.
> ---
> 
> Suggest rewording as follows:
>    REQ. 11:  During the 
> handshake ,the WebSocket Client MUST be able
> to send one or more 
> WebSocket sub-protocol proposals to the server
> so that the server can 
> select one.,This results in the use of a specific
> WebSocket 
> sub-protocol.

I don't think this is needed. It's also something that can 
> easily be added later if application authors find a need for 
> it.

[gm] Are you disagreeing with the proposed rewording or with the original
wording?:

"   REQ. 11:  The WebSocket Client MUST be able to request the server,
      during the handshake, to use a specific WebSocket sub-protocol.
"

The rewording did not change the basic requirement for sub-protocol support, it
was just adding more text as to how that might happen.

thanks,

Gabriel