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

SM <sm@resistor.net> Sat, 30 January 2010 00:14 UTC

Return-Path: <sm@resistor.net>
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 916643A67F3 for <hybi@core3.amsl.com>; Fri, 29 Jan 2010 16:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Level:
X-Spam-Status: No, score=-1.383 tagged_above=-999 required=5 tests=[AWL=-0.174, 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 KR9ztLQGujr7 for <hybi@core3.amsl.com>; Fri, 29 Jan 2010 16:14:44 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id A608B3A679C for <hybi@ietf.org>; Fri, 29 Jan 2010 16:14:44 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4/8.14.4) with ESMTP id o0U0EwVo027044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <hybi@ietf.org>; Fri, 29 Jan 2010 16:15:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1264810507; x=1264896907; bh=fX33EcyjE6SSuCBIA5jcBNam8gqMuefyO/SCcTw8PbQ=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=O4qiQFswf8wJuckeC5UvWU7fs9eYXM1b4zORG4FTIP7I4f1foX99OuiQkyYgnJAia KlgISWZzq40bcTBAxS93izgtmB0spjHkOiFAL5z1SVJbGQ7VAQzdmbIF6uMSBk86T/ zTxEhDc2wdmW7tWvl8C6eQLdBunGKTY86kmshyus=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=IS7nMaS7ZqrxdP2I9eK+01P4VAtvMNELNn9uaAEOfAZqQZBbgUKss/VR8yJsOy4+Q VgZZDjGlWzZEIoCX2lEMWdof6bOqqgX9yXEaxxj9A+sTGi5njBg+8RNSPGKRWx0hgqs 8Ej3/rW9czJr7VMDg3hK91CFHu4vurlhXbKVC4s=
Message-Id: <6.2.5.6.2.20100129153903.0a498ad8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 29 Jan 2010 16:11:14 -0800
To: Hybi <hybi@ietf.org>
From: SM <sm@resistor.net>
In-Reply-To: <4B635D45.6050308@webtide.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> <6.2.5.6.2.20100129023917.06806000@resistor.net> <Pine.LNX.4.64.1001291140440.22020@ps20323.dreamhostps.com> <6.2.5.6.2.20100129071038.09c66860@resistor.net> <4B635D45.6050308@webtide.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: Sat, 30 Jan 2010 00:14:45 -0000

At 14:12 29-01-10, Greg Wilkins wrote:
>I no Ian does not put much stock in charters, but this one
>http://www.whatwg.org/charter has a tiny foot note that says:

As some of the discussion has been about talking to the WHATWG, my 
question is to find out who is talking on behalf of the group.

At 14:21 29-01-10, Jamie Lokier wrote:
>If one specification does not address significant requirements, and
>the other specification does but will take a long time to arrive, then
>it may well be in the interest of the internet community to have both.

That's the extreme alternative and it could be unpleasant.

At 14:17 29-01-10, Jamie Lokier wrote:
>This is how it looks to me:
>
>It's about different groups of people, so the term "consensus" is
>being used to mean different things in this discussion; hence conflict
>and emotion.  (There is also a mismatch of expectations, which I will

Yes.

Regards,
-sm