Re: [hybi] draft-ietf-hybi-thewebsocketprotocol-00

SM <sm@resistor.net> Mon, 24 May 2010 21:42 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 D88983A686D for <hybi@core3.amsl.com>; Mon, 24 May 2010 14:42:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.875
X-Spam-Level:
X-Spam-Status: No, score=-0.875 tagged_above=-999 required=5 tests=[AWL=-0.876, BAYES_50=0.001]
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 mOUMB1vPTKgI for <hybi@core3.amsl.com>; Mon, 24 May 2010 14:42:42 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 4E0533A680F for <hybi@ietf.org>; Mon, 24 May 2010 14:42:42 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o4OLgMb6015123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 May 2010 14:42:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1274737350; x=1274823750; bh=nwcNHPPfHP1pcJWzmsp1aje0C9JJo8FRVWEE7YXLeKo=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=RED0aoILMNBE5Xe3iWWYF1LxYbRTv9r/rdRV5wnkmRlIs3CjTvgdYpSphjxMt592N 1p0wu4klrgavlKF0pCr3lpbcVO9brMtzv2tvInOd4vRd69+5fS02wULgKxhc0OWac6 GBJ7ceQX7LdcpF/CNGvhNZV+ZIeqxDLFUQIc8O2A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1274737350; x=1274823750; bh=nwcNHPPfHP1pcJWzmsp1aje0C9JJo8FRVWEE7YXLeKo=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=UPkfneBv4GC9iLYIljKsqpQi5AxSkcI5TCEVBwRz5ovK+lFKKSmShqwqfhCJdVECm 4j2CcYnKwjLi5k7aznCy0cX+Ok/eNEl+HQ0V0zqyX/kKvNeG6aOSoforiI2Qw+SZbw Ior23C3/7qr/KaIr1TQyDOTIygnyBrOWd5QgpyjA=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=UdJFTJiSGu0EJ0Yn7Vrgb8nBHRVkiCLI3qzMth34GLpbssJHx/ohKYkukB1b24Cgc UnDVELGNF9T1dcC4/RYcOLSBWBbUtjnLDEwO1991yugsFslmsTlcXf+qMz6sNSpTJGh jqKtTxTVL7y8ShDuX2rOfFTln93ZnwWlyW2KzWk=
Message-Id: <6.2.5.6.2.20100524133712.0a83b6a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 May 2010 14:40:40 -0700
To: Adam Barth <ietf@adambarth.com>
From: SM <sm@resistor.net>
In-Reply-To: <AANLkTin9Llyz2Ejbqk7iVtuHTSTeN2xSAFN8ATUbIxtV@mail.gmail.c om>
References: <6.2.5.6.2.20100523104659.05fcea60@elandnews.com> <FD7B10366AE3794AB1EC5DE97A93A37305A2FC3CC1@EXMB01CMS.surrey.ac.uk> <AANLkTin9Llyz2Ejbqk7iVtuHTSTeN2xSAFN8ATUbIxtV@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: hybi@ietf.org
Subject: Re: [hybi] draft-ietf-hybi-thewebsocketprotocol-00
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, 24 May 2010 21:42:44 -0000

Hi Adam,
At 11:03 24-05-10, Adam Barth wrote:
>I usually try not to get involved in process discussions, but I
>thought it might be helpful to say a bit about the benefits of
>involving the whatwg in the process.

That has been discussed in October, 2009.  There were also arguments 
about the benefits of the IETF process.

>Generally, the whatwg mailing list has a higher ratio of technical
>content to meta-discussion, which means it's more approachable for
>developers who don't normally participate in standards.  For example,
>I've encouraged various members of the WebKit community to raise their
>concerns and questions about HTML5 in the whatwg instead of on
>public-html because, historically, I've found that they get
>friendlier, more productive responses, which encourages them to
>participate further.

Anyone can participate in an IETF working group.  I haven't raised a 
formal objection as I still believe that it is better to work things out.

>If we exclude the whatwg, we're likely to miss out on these points of
>view.  Although folks like you and I can handle participating in this
>forum, there's a group of folks who find this sort of forum
>intimidating and unwelcoming.  Of course, another solution is to
>encourage folks on this list to be friendlier and more welcoming.  One
>way to start down that road is to avoid speaking in absolutes or the
>imperative.

You are the second person who brought up the question of excluding 
the people from the whatwg.  Is there any message from this mailing 
list that points to that?

draft-ietf-hybi-websocket-requirements-00 was edited by G. Wilkins, 
Webtide.com and M. Stachowiak, Apple. Greg Wilkins resigned [1] as 
editor.  There was a thread about email granularity [2] and a 
discussion about consensus [3].  I am all for a friendlier and 
welcoming approach.  The discussion about the whatwg looks like a red 
herring.  The solution to look for is how to come to an understanding 
about how to get the work done while following the IETF 
process.  This is an IETF working group after all.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/hybi/current/msg02020.html
2. http://www.ietf.org/mail-archive/web/hybi/current/msg01610.html
3. http://www.ietf.org/mail-archive/web/hybi/current/msg02074.html