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

Jamie Lokier <jamie@shareable.org> Mon, 17 May 2010 19:37 UTC

Return-Path: <jamie@shareable.org>
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 DAFC43A683C for <hybi@core3.amsl.com>; Mon, 17 May 2010 12:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.033
X-Spam-Level:
X-Spam-Status: No, score=-1.033 tagged_above=-999 required=5 tests=[AWL=-1.034, BAYES_50=0.001]
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 T2YznSmdUFl7 for <hybi@core3.amsl.com>; Mon, 17 May 2010 12:37:12 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id CF6893A680E for <hybi@ietf.org>; Mon, 17 May 2010 12:37:11 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1OE67b-0007t2-71; Mon, 17 May 2010 20:37:03 +0100
Date: Mon, 17 May 2010 20:37:03 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Greg Wilkins <gregw@webtide.com>
Message-ID: <20100517193703.GG20356@shareable.org>
References: <y2s5c4444771005131226l18de7b18l6d80411890049552@mail.gmail.com> <E6E437C7-BE01-4C27-A3E6-5B05A80599A6@apple.com> <20100514034909.GA23444@shareable.org> <4BECF665.5020102@webtide.com> <AANLkTikAy0iWkaoUVgLqee1kW29xZIByDn0MKBUNHmiE@mail.gmail.com> <4BEDA65C.1070009@webtide.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4BEDA65C.1070009@webtide.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: Hybi <hybi@ietf.org>
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: Mon, 17 May 2010 19:37:13 -0000

Greg Wilkins wrote:
> So if we use TLS, then I think it is even more important
> that we consider how we can limit and/or reduce the
> usage of connections. Multiplexing would help.
> Sharing connections with HTTP traffic is also a good idea.

Multiplexing over TLS works for me technically as far as scaling at
the client and server.  I'd worry a little about the inability to
fan-in and fan-out at intermediate proxies, which is not likely to be
relevant to the majority of locations, but is potentially useful in
some networks.

My main concern, with TLS, would be the social/political ramifications
of everything being encrypted and end-to-end authenticated.

Maybe that's a good direction to take the web, but are we sure
WebSocket and the Hybi forum is the place to push it, starting from a
technical concern?

If port 443 is needed, why not send non-TLS traffic over it?  Are
proxies which pass TLS bytes unchanged going to recognise unencrypted
data and mangle it?  Is it forbidden to use anything other than TLS
over it?

Thanks,
-- Jamie