Re: [hybi] Process! was: [whatwg] HttpOnly cookie for WebSocket?

Ian Hickson <ian@hixie.ch> Fri, 29 January 2010 04:17 UTC

Return-Path: <ian@hixie.ch>
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 73E3C3A687E for <hybi@core3.amsl.com>; Thu, 28 Jan 2010 20:17:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[AWL=-0.670, BAYES_00=-2.599, PLING_QUERY=1.39]
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 VRm92mNrzWPc for <hybi@core3.amsl.com>; Thu, 28 Jan 2010 20:17:12 -0800 (PST)
Received: from looneymail-a4.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 16AF53A6781 for <hybi@ietf.org>; Thu, 28 Jan 2010 20:17:11 -0800 (PST)
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a4.g.dreamhost.com (Postfix) with ESMTP id B8A2081C6; Thu, 28 Jan 2010 20:17:32 -0800 (PST)
Date: Fri, 29 Jan 2010 04:17:32 +0000
From: Ian Hickson <ian@hixie.ch>
To: Greg Wilkins <gregw@webtide.com>
In-Reply-To: <4B625733.2020907@webtide.com>
Message-ID: <Pine.LNX.4.64.1001290407290.22020@ps20323.dreamhostps.com>
References: <de17d48e1001280012i2657b587i83cda30f50013e6b@mail.gmail.com> <4B614CEC.2050400@ericsson.com> <Pine.LNX.4.64.1001280856380.22020@ps20323.dreamhostps.com> <4B616F17.4030402@ericsson.com> <4B619223.60408@webtide.com> <Pine.LNX.4.64.1001282141080.22020@ps20323.dreamhostps.com> <4B620B8F.6030706@gmx.de> <Pine.LNX.4.64.1001282217320.22053@ps20323.dreamhostps.com> <bbeaa26f1001281449q1a6e1813q3f537fe15a5a9d60@mail.gmail.com> <4B625733.2020907@webtide.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Process! was: [whatwg] HttpOnly cookie for WebSocket?
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: Fri, 29 Jan 2010 04:18:11 -0000

On Fri, 29 Jan 2010, Greg Wilkins wrote:
>
> The whatwg has done a great job getting it this far, but I really think 
> they should trust (and be involved in) the IETF process to take it to 
> the next stage.

I'm happy to work with the IETF, the point is just that the IETF should 
cooperate with the WHATWG, on a joint effort, just like the W3C cooperates 
with the WHATWG over HTML5.

To be blunt, though, if the IETF wants trust, it should earn it. Had the 
IETF actually approached the WHATWG community or even mentioned working 
with the WHATWG anywhere in the charter, or, say, responded to my feedback 
on the charter, or had a realistic timetable in the charter that 
acknowledged the stage at which the WebSockets spec is at, maybe trust 
would be easier.

Instead, what's happened is the equivalent of me talking to some of the 
people working on HTTP, and then saying "ok we'll do HTTP on a new mailing 
list" and not even letting the HTTP working group know about it.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'