websockets in the IETF, was: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)

Julian Reschke <julian.reschke@gmx.de> Tue, 23 October 2012 13:27 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD47021F849C for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.227
X-Spam-Level:
X-Spam-Status: No, score=-103.227 tagged_above=-999 required=5 tests=[AWL=-0.628, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8BPjfNkKXvc for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:27:07 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 73ED221F84B1 for <ietf@ietf.org>; Tue, 23 Oct 2012 06:27:07 -0700 (PDT)
Received: (qmail invoked by alias); 23 Oct 2012 13:27:05 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp020) with SMTP; 23 Oct 2012 15:27:05 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18ma8l03Pcms/p9yKvtPBrUsNJXmQDDLlcvSsmsF6 35/qKrpMJmOs8e
Message-ID: <50869B24.2070109@gmx.de>
Date: Tue, 23 Oct 2012 15:27:00 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: websockets in the IETF, was: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net> <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com> <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net> <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Mark Nottingham <mnot@mnot.net>, James M Snell <jasnell@gmail.com>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 13:27:08 -0000

On 2012-10-23 01:59, Ian Hickson wrote:
> ...
> Whether WebSockets is a good idea or not is besides the point. The point
> is that the hybi group was not a pleasant experience for me. If I were to
> be in a position to do Web Sockets again, I would decline the opportunity
> to do it through the IETF. Doing it through the IETF made the work take a
> year longer than it would have, made the protocol less secure (the WG
> removed a number of defense-in-depth features), and made the spec a mess
 > ...

And, as far as I can tell, fixed a security problem in the original 
design (which caused some UA implementers to actually disable what they 
were shipping at that time): <http://w2spconf.com/2011/papers/websocket.pdf>

> (it's a mishmash of different editing styles). Plus, the group _still_
> hasn't done multiplexing, which some of the vendors said was a prereq to
> implementation, something which, prior to the IETF getting involved, was
> only 3 to 6 months out on the roadmap.
> ...

Indeed, but then wasn't it you arguing *against* having it in the base 
spec? (see 
<http://www.ietf.org/mail-archive/web/hybi/current/msg00239.html>)


Best regards, Julian