Re: [hybi] Proposed Charter for HyBi WG (rev.3)

Salvatore Loreto <salvatore.loreto@ericsson.com> Mon, 02 November 2009 10:47 UTC

Return-Path: <salvatore.loreto@ericsson.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 4538C3A681B for <hybi@core3.amsl.com>; Mon, 2 Nov 2009 02:47:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.031
X-Spam-Level:
X-Spam-Status: No, score=-6.031 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 R63y0Gb4Xv0G for <hybi@core3.amsl.com>; Mon, 2 Nov 2009 02:47:45 -0800 (PST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 31FB33A67E1 for <hybi@ietf.org>; Mon, 2 Nov 2009 02:47:45 -0800 (PST)
X-AuditID: c1b4fb3e-b7bf6ae000005dda-ba-4aeeb8e26f5b
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id B8.DA.24026.2E8BEEA4; Mon, 2 Nov 2009 11:48:03 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Nov 2009 11:48:02 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Nov 2009 11:48:02 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 3CD582514; Mon, 2 Nov 2009 12:48:02 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 0281421A2A; Mon, 2 Nov 2009 12:48:02 +0200 (EET)
Received: from localhost.localdomain (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id ADF23219B8; Mon, 2 Nov 2009 12:48:01 +0200 (EET)
Message-ID: <4AEEB8E1.7080903@ericsson.com>
Date: Mon, 02 Nov 2009 12:48:01 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090825)
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <4AE966CA.9090907@ericsson.com> <Pine.LNX.4.62.0910300047310.25608@hixie.dreamhostps.com> <4AEABDBF.80705@ericsson.com> <6.2.5.6.2.20091030120030.043cff78@resistor.net> <Pine.LNX.4.62.0910310335580.25616@hixie.dreamhostps.com> <6.2.5.6.2.20091031080527.040fe028@resistor.net> <Pine.LNX.4.62.0911012010470.27039@hixie.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.62.0911012010470.27039@hixie.dreamhostps.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 02 Nov 2009 10:48:02.0646 (UTC) FILETIME=[F381EF60:01CA5BA9]
X-Brightmail-Tracker: AAAAAA==
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Proposed Charter for HyBi WG (rev.3)
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: Mon, 02 Nov 2009 10:47:46 -0000

Ian Hickson wrote:
> On Sat, 31 Oct 2009, SM wrote:
>   
>> Joint responsibility increases the chances of failure as two working 
>> groups do not work the same way.
>>     
>
> How do you define "success"? I think the more people are involved the more 
> likely we are to get interoperable implementations.
>
>   
>>> It should be noted that the WHATWG's work is based on technical merit 
>>> and not on consensus. If even just one person raises a valid technical 
>>> issue in the WHATWG, they cannot be overridden by the rest of the 
>>> group having complete agreement that they should just ignore the 
>>> technical issue. There is also a firm philosophy that the specs match 
>>> interoperable deployed implementations, and that the specs not leave 
>>> things undefined.
>>>       
>> The IETF process is based on consensus.  An IETF Working Group cannot 
>> change that. The philosophical questions can be addressed in the charter 
>> if the group reaches a consensus about that.
>>
>> My comments are as an individual.  The proposed WG will be part of the 
>> IETF. It is not the IETF.  The entire IETF community will be asked to 
>> comment on the proposal submitted for publication.  The IETF does not 
>> constrain the solution. It is up to the IETF participants to determine 
>> what problem will be solved and how it will be solved.  There's the BoF 
>> and this mailing to discuss about all that and come up with a proposed 
>> charter.  People from the W3C WebApps and WHATWG are not excluded.  Ask 
>> them to join this mailing list and participate.
>>     
>
> Sure. And people from the IETF are not excluded from the WHATWG, and are 
> welcome to join the mailing list and participate there also.
>   
My comment as individual.
I am in the WHATWG ml, but I have to say that I haven't seen any 
discussion, at least lately, on the WebSocket spec.
at least in the specification mailing list.
Actually I'd like also see more people from WHATWG community become 
involved the technical discussion that at the moment
is happening in the HyBi mailing list.

cheers
Sal