Re: [hybi] Extensibility mechanisms?

Ian Hickson <ian@hixie.ch> Sun, 18 April 2010 02:55 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 B3B723A6985 for <hybi@core3.amsl.com>; Sat, 17 Apr 2010 19:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.894
X-Spam-Level:
X-Spam-Status: No, score=-0.894 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_20=-0.74]
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 JCVvOObuZfwr for <hybi@core3.amsl.com>; Sat, 17 Apr 2010 19:55:29 -0700 (PDT)
Received: from looneymail-a1.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id C9B7F3A677E for <hybi@ietf.org>; Sat, 17 Apr 2010 19:55:29 -0700 (PDT)
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-a1.g.dreamhost.com (Postfix) with ESMTP id 5400A15DC36; Sat, 17 Apr 2010 19:55:22 -0700 (PDT)
Date: Sun, 18 Apr 2010 02:55:22 +0000
From: Ian Hickson <ian@hixie.ch>
To: Greg Wilkins <gregw@webtide.com>
In-Reply-To: <4BC96A0D.4080904@webtide.com>
Message-ID: <Pine.LNX.4.64.1004180246380.751@ps20323.dreamhostps.com>
References: <h2w5c902b9e1004152345j992b815bz5f8d38f06a19181a@mail.gmail.com> <Pine.LNX.4.64.1004160701250.751@ps20323.dreamhostps.com> <4BC860FD.8080007@webtide.com> <Pine.LNX.4.64.1004161952530.751@ps20323.dreamhostps.com> <4BC96A0D.4080904@webtide.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Extensibility mechanisms?
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: Sun, 18 Apr 2010 02:55:30 -0000

On Sat, 17 Apr 2010, Greg Wilkins wrote:
> 
> I'm sorry but despite your original aims, enabling amateur programmers 
> to write protocols that avoid the need for vendor supplied 
> infrastructure is not the prime reason this WG has come into existence.

If that isn't a goal for this working group, then that's fine, but it 
means I'm in the wrong group.


> The reason that most of us are here, and the reason that our employers 
> pay our salaries to be here, is so that vendors can produce software 
> and/or appliances that can be deployed by their clients with some remote 
> hope of interoperating with the products from other vendors.

The reason I'm here is that the IETF asked me to work on Web Sockets in 
this working group. Web Sockets is a technology aimed as, as you put it, 
enabling amateurs programmers to write protocols that avoid the need for 
vendor supplied infrastructure (amongst other things). If the IETF is 
still interested in working on such a technology, what's the right working 
group for it? If the IETF is not interested in working on such a working 
group, then it would be in everyone's interests for that to be made clear, 
so that we don't act at cross purposes, and so that the work on that 
technology can resume elsewhere.

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