Re: [hybi] updated Charter proposal (WebSocket)

Maciej Stachowiak <mjs@apple.com> Tue, 27 October 2009 00:21 UTC

Return-Path: <mjs@apple.com>
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 E4F0128C1C2 for <hybi@core3.amsl.com>; Mon, 26 Oct 2009 17:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 wfgHH+ROlGjK for <hybi@core3.amsl.com>; Mon, 26 Oct 2009 17:21:12 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 3CCB228C1BF for <hybi@ietf.org>; Mon, 26 Oct 2009 17:21:12 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id 50DF7778D47A for <hybi@ietf.org>; Mon, 26 Oct 2009 17:21:26 -0700 (PDT)
X-AuditID: 1180711d-b7c0eae000004000-b5-4ae63d061dd2
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay13.apple.com (Apple SCV relay) with SMTP id A6.EB.16384.60D36EA4; Mon, 26 Oct 2009 17:21:26 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Received: from il0301a-dhcp113.apple.com (il0301a-dhcp113.apple.com [17.203.14.241]) by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0KS500CQ5CZP9890@gertie.apple.com> for hybi@ietf.org; Mon, 26 Oct 2009 17:21:26 -0700 (PDT)
Message-id: <9F3A17FE-17FC-4397-9E54-C480D73FD237@apple.com>
From: Maciej Stachowiak <mjs@apple.com>
To: Greg Wilkins <gregw@webtide.com>
In-reply-to: <4AE6362B.4030305@webtide.com>
Date: Mon, 26 Oct 2009 17:21:25 -0700
References: <4ADEC7A0.7040307@ericsson.com> <4AE4CCBB.10001@webtide.com> <Pine.LNX.4.62.0910260006420.9145@hixie.dreamhostps.com> <4AE553A0.9030208@ericsson.com> <73F5E810-F40F-42B8-81A9-4AD1306E360F@apple.com> <4AE57B62.4030209@webtide.com> <ca722a9e0910261139q27a3241aieae39a6a0525b290@mail.gmail.com> <4AE6362B.4030305@webtide.com>
X-Mailer: Apple Mail (2.936)
X-Brightmail-Tracker: AAAAAQAAAZE=
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] updated Charter proposal (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: Tue, 27 Oct 2009 00:21:13 -0000

On Oct 26, 2009, at 4:52 PM, Greg Wilkins wrote:

> Lisa Dusseault wrote:
>> On Mon, Oct 26, 2009 at 3:35 AM, Greg Wilkins <gregw@webtide.com>  
>> wrote:
>>> ...
>>> However, I don't think the charter should mandate the WebSocket  
>>> protocol
>>> as the outcome.
>>>
>>> The protocol should be able to be selected on it's own merits - and
>>> that includes the effort that many have put towards it already.
>>>
>>
>> Hi Greg,
>>
>> Asking WGs to run beauty contests typically turns out to be
>> problematic.  I think we get better success at asking whether it's
>> appropriate to form a WG around a specific proposal, and that doesn't
>> exclude other WGs and other proposals.  It's really the WG formation
>> process that lets the entire IETF decide if a WG working on the
>> WebSocket protocol is the right thing to do.   That process does
>> address the merits, and it avoids the "there can be only one"  
>> fallacy.
>
> OK if that's the process, then that's the process.
>
> However, the authors of the protocol have so far been very
> resistant to change (not even using BNF or allocating a
> type byte for mime-encoded content).
>
> So will the WG have the ability to come up with it's own
> draft for a websocket protocol - or will all it be able
> to do is huff and puff and hope to convince the whatwg?

I would expect the standard for deciding the contents of an eventual  
RFC will be "rough consensus and running code".

Regards,
Maciej