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

[Ian Hickson <[e-mail]>]

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 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 
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. :-)


> Moreover I have seen a lot of mail exchanges raising possible problems in the
> current version of the WebSocket draft
> that you should consider and address in the draft or provide to the IETF
> community good technical reasons why you choose to not consider them

There's a couple of e-mails from earlier today that I haven't yet 
considered, but other than that, I've read and considered all the e-mails 
to this list, and provided detailed reasons for rejecting any proposals 
I've not adopted. If I missed one, please let me know.

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