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

Ian Hickson <ian@hixie.ch> Fri, 29 January 2010 11:39 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 15A513A688D for <hybi@core3.amsl.com>; Fri, 29 Jan 2010 03:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level:
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[AWL=-0.652, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 qmrAOK0Osr6V for <hybi@core3.amsl.com>; Fri, 29 Jan 2010 03:39:05 -0800 (PST)
Received: from looneymail-a4.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 274393A6858 for <hybi@ietf.org>; Fri, 29 Jan 2010 03:39:05 -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 128178165; Fri, 29 Jan 2010 03:39:26 -0800 (PST)
Date: Fri, 29 Jan 2010 11:39:24 +0000
From: Ian Hickson <ian@hixie.ch>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
In-Reply-To: <4B62C5FE.8090904@it.aoyama.ac.jp>
Message-ID: <Pine.LNX.4.64.1001291134350.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> <6.2.5.6.2.20100128225542.06fa8d68@resistor.net> <Pine.LNX.4.64.1001290817520.22020@ps20323.dreamhostps.com> <4B62C5FE.8090904@it.aoyama.ac.jp>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-1555694626-703513121-1264765164=:22020"
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 11:39:06 -0000

On Fri, 29 Jan 2010, "Martin J. Dürst" wrote:
> 
> Ian, could you please explain how exactly *you* imagine such a 
> cooperation should work, if not e.g. by cross-posting?

The same way it works with the HTML5 specification and the various Web 
Apps specifications -- feedback is collected from both groups (and indeed, 
anywhere else that feedback is provided, e.g. on blogs or forums), and 
changes are made that take into account all the feedback. The most active 
members of both groups stay in regular contact, e.g. on IRC, or by e-mail, 
to ensure that everyone is on the same page. Where editorial differences 
arise (e.g. the IETF prefers text/plain specs, the WHATWG prefers HTML- 
based specs), the groups ensure that normative requirement remain 
identical across different versions. Basically, exactly as has been 
happening for the past few years already.

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