Re: [hybi] web socket protocol in "last call"?

Julian Reschke <julian.reschke@gmx.de> Wed, 28 October 2009 10:26 UTC

Return-Path: <julian.reschke@gmx.de>
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 DE0643A688E for <hybi@core3.amsl.com>; Wed, 28 Oct 2009 03:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.718
X-Spam-Level:
X-Spam-Status: No, score=-3.718 tagged_above=-999 required=5 tests=[AWL=-1.119, BAYES_00=-2.599]
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 rMY8F5x+sq6a for <hybi@core3.amsl.com>; Wed, 28 Oct 2009 03:26:29 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 964C83A6358 for <hybi@ietf.org>; Wed, 28 Oct 2009 03:26:28 -0700 (PDT)
Received: (qmail invoked by alias); 28 Oct 2009 10:26:42 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.117]) [217.91.35.233] by mail.gmx.net (mp066) with SMTP; 28 Oct 2009 11:26:42 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/SmWA0KTHS7W/8uirC6VFXkOmoqpsdUmbmHKqQ5d REgZQPOuTCdTIt
Message-ID: <4AE81C5B.2040003@gmx.de>
Date: Wed, 28 Oct 2009 11:26:35 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <4AE7F0AE.1000102@gmx.de> <Pine.LNX.4.62.0910280740540.25608@hixie.dreamhostps.com> <4AE7FFC4.8050405@gmx.de> <4AE806AA.60901@ericsson.com> <Pine.LNX.4.62.0910280938560.25608@hixie.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.62.0910280938560.25608@hixie.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.64
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] web socket protocol in "last call"?
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: Wed, 28 Oct 2009 10:26:30 -0000

Ian Hickson wrote:
> On Wed, 28 Oct 2009, Salvatore Loreto wrote:
>> the  WebSocket protocol is already an IETF draft so
>> It is not fair to start a last call in a different community to freeze the
>> protocol without announce it
>> also in the IETF mailing list and ask if IETF people agree on freezing the
>> protocol.
> 
> I don't think anyone is suggesting intentionally freezing the protocol. 
> The WHATWG announcement was just a call for comments.

It appears it's not relevant whether it's intentionally or not.

> It is the case, however, that once we have multiple interoperable 
> implementations, regardless of where we stand with respect to the process 
> here or at the WHATWG, the protocol will be essentially frozen on us, 
> whether we like it or not. (Well, we could change it further, but then 

Well, we could tell implementers not to ship with that feature. 
Actually, we should.

> we'd just be ignored.) I expect this to happen in the coming months.
> 
> 
>> As WebSocket protocol is an Internet draft it should follow the IETF rules.
> 
> It's also a WHATWG draft, so it should also follow the WHATWG rules. :-)

In which case you should clarify what this means in practice, because it 
should be considered when chartering the Working Group.

> ...

BR, Julian