Re: [hybi] Handshake was: The WebSocket protocol issues.

Patrick McManus <mcmanus@ducksong.com> Mon, 11 October 2010 21:28 UTC

Return-Path: <mcmanus@ducksong.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 669D83A6832 for <hybi@core3.amsl.com>; Mon, 11 Oct 2010 14:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[AWL=-0.020, 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 coyeXGijr6vm for <hybi@core3.amsl.com>; Mon, 11 Oct 2010 14:28:33 -0700 (PDT)
Received: from linode.ducksong.com (linode.ducksong.com [64.22.125.164]) by core3.amsl.com (Postfix) with ESMTP id 0CC7A3A6864 for <hybi@ietf.org>; Mon, 11 Oct 2010 14:28:32 -0700 (PDT)
Received: by linode.ducksong.com (Postfix, from userid 1000) id 71E9A102A7; Mon, 11 Oct 2010 17:29:44 -0400 (EDT)
Received: from [192.168.16.226] (cpe-67-253-92-25.maine.res.rr.com [67.253.92.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by linode.ducksong.com (Postfix) with ESMTPSA id E704810159; Mon, 11 Oct 2010 17:29:43 -0400 (EDT)
From: Patrick McManus <mcmanus@ducksong.com>
To: Ian Hickson <ian@hixie.ch>
In-Reply-To: <Pine.LNX.4.64.1010112100560.8618@ps20323.dreamhostps.com>
References: <4CAFA043.10101@caucho.com> <AANLkTi=eo-cjBz160FN0cn53v4-CpDSYaEneqkr_ZP7k@mail.gmail.com> <4CAFAC2B.5000800@caucho.com> <55bva61goeqtn0lifgjt5uihf50obh7kf4@hive.bjoern.hoehrmann.de> <4CAFB9C4.6030905@caucho.com> <AANLkTinv5Ym5jwUEqS76z3UkVa7GpmOBT_WXhBbFK0-m@mail.gmail.com> <20101009055723.GL4712@1wt.eu> <AANLkTimY2DjxgZybibSRtc7L34Wns2KhQC=Wa9K6PYku@mail.gmail.com> <20101009204009.GP4712@1wt.eu> <AANLkTi=Az0RmE1Uipo068zMh3YzgMpM2tQ+zYxaDT47A@mail.gmail.com> <20101011053354.GA12672@1wt.eu> <4CB2D7BD.1070004@opera.com> <9B9FA451-5551-4434-8EC1-BAC834FB9A61@apple.com> <AANLkTimDc_aqRTtgRpMKhdhk6x+vPGyOPvU3A=6mK9S7@mail.gmail.com> <4CB3373C.5050507@opera.com> <Pine.LNX.4.64.1010112100560.8618@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 11 Oct 2010 17:29:35 -0400
Message-ID: <1286832575.2924.319.camel@ds9.ducksong.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
Content-Transfer-Encoding: 7bit
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] Handshake was: The WebSocket protocol issues.
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, 11 Oct 2010 21:28:34 -0000

On Mon, 2010-10-11 at 21:04 +0000, Ian Hickson wrote:

> 
> I would like to ask a similar question, but to the people proposing Adam 
> and Eric's latest proposed handshake. What real problem does it solve that 
> NPN with TLS doesn't solve? 

Alternatives to NPN do not require a totally independent spec, which has
not passed through a standards process, to be widely deployed before the
websockets implementation can be used at all. TLS is often terminated
separately from HTTP and under very different administrative policies. A
number of those NPN capable deployments would need to replace embedded
TLS implementations and other
paperwork-heavy-because-it-is-a-security-device servers which are going
to have long half lives.

I really think an NPN dependency is a non starter for that reason. We've
made compatibility with 443/80 a goal because it passes through existing
infrastructure and non-NPN aware devices are part of that
infrastructure.

A world with NPN we could depend on would be great, but I don't want to
tie websockets down to wait for it - but I am really pleased to see the
nuts and bolts of connect and upgrade being sorted through.

-Patrick