Re: [hybi] An alternative design for the web socket handshake

Greg Wilkins <gregw@webtide.com> Thu, 13 May 2010 21:26 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 492B43A6CF4 for <hybi@core3.amsl.com>; Thu, 13 May 2010 14:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.687
X-Spam-Level:
X-Spam-Status: No, score=-0.687 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_20=-0.74]
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 dQa+FWjJ6Ld8 for <hybi@core3.amsl.com>; Thu, 13 May 2010 14:26:27 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 287603A6CC0 for <hybi@ietf.org>; Thu, 13 May 2010 14:26:26 -0700 (PDT)
Received: by wwb28 with SMTP id 28so245115wwb.31 for <hybi@ietf.org>; Thu, 13 May 2010 14:26:13 -0700 (PDT)
Received: by 10.227.72.206 with SMTP id n14mr321423wbj.229.1273785973795; Thu, 13 May 2010 14:26:13 -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 y22sm11512579wby.5.2010.05.13.14.26.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 13 May 2010 14:26:13 -0700 (PDT)
Message-ID: <4BEC6E70.80102@webtide.com>
Date: Thu, 13 May 2010 23:26:08 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Hybi <hybi@ietf.org>
References: <y2s5c4444771005131226l18de7b18l6d80411890049552@mail.gmail.com> <E6E437C7-BE01-4C27-A3E6-5B05A80599A6@apple.com>
In-Reply-To: <E6E437C7-BE01-4C27-A3E6-5B05A80599A6@apple.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] An alternative design for the web socket handshake
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 21:26:28 -0000

Maciej Stachowiak wrote:
> The main downside is that it would be impossible to do non-TLS WebSocket; 

It would not be impossible.

If websocket was allocated a dedicated port for non-TLS connections,
then that could be used at least for development and testing.

TLS would only need to be used for actual deployment and the nextprotoneg
extension does allow easy sharing of port 443.  However I'm not sure how
long it will take before nextprotoneg is well supported by TLS libraries?

Note that the possibility of using non-HTTP handshake suggests that even
if we start with HTTP upgrade, it would be worthwhile to not depend too
much on HTTP headers in the handshake.  Having something like the
control frames in Scott Fergusons proposal will work regardless of the
way the connection is made.


cheers