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
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.