IETF Logo Mail Archive

Re: [hybi] [whatwg] HttpOnly cookie for WebSocket?

Ian Hickson <ian@hixie.ch> Thu, 28 January 2010 11:26 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 4DDAE3A695F for <hybi@core3.amsl.com>; Thu, 28 Jan 2010 03:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 OMUkpSgU-fwO for <hybi@core3.amsl.com>; Thu, 28 Jan 2010 03:26:07 -0800 (PST)
Received: from looneymail-a4.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 5197A3A67B4 for <hybi@ietf.org>; Thu, 28 Jan 2010 03:26:07 -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 4DFC481C6; Thu, 28 Jan 2010 03:26:25 -0800 (PST)
Date: Thu, 28 Jan 2010 11:26:24 +0000
From: Ian Hickson <ian@hixie.ch>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
In-Reply-To: <4B616F17.4030402@ericsson.com>
Message-ID: <Pine.LNX.4.64.1001281117370.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>
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] [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: Thu, 28 Jan 2010 11:26:08 -0000

On Thu, 28 Jan 2010, Salvatore Loreto wrote:
> 
> first I think it would be better have and maintain both whatwg and hybi 
> mailing list in any conversation related to WebSocket

Please don't cross-post to the WHATWG list -- it causes threads to 
fragment since not everyone is subscribed to both lists and the WHATWG 
list rejects non-subscriber posts.


> at the BoF in Hiroshima there was a clear consensus from all the 
> participants (both the one physically present and the one remotely 
> attending via streaming and chat) to move the WebSocket standardization 
> work within IETF community.

As I recall, the suggestion was for the W3C to work with the WHATWG on the 
API spec, and for the IETF to work with the WHATWG on the protocol spec. 
Certainly I do not recall any communication from the IETF to the WHATWG to 
the effect that the WHATWG should stop working on or publishing the 
WebSocket protocol spec. Indeed I was quite shocked to see my feedback to 
this effect be ignored and the charter be published with no mention of 
cooperation with the WHATWG, and with a ridiculous timeline that has us 
going back to requirements and only reaching last call in March 2011, when 
the spec in question has, as I mentioned in my e-mail to the WHATWG 
earlier, already reached last call as of October last year. I was even 
more shocked to see no mention of a test suite, which is really the only 
time-consuming thing that really remains to be done at this point.

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

v2.23.0 | Report a Bug | By Email