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

[Julian Reschke <[e-mail]>]

Ian Hickson wrote:
> On Wed, 28 Oct 2009, Julian Reschke wrote:
>> Citing <http://blog.whatwg.org/html5-at-last-call>:
>>
>> "There's also a version of the spec called Web Applications 1.0 (for 
>> nostalgic reasons) that has all of the above as well as a number of 
>> other specs, namely Web Storage, Web Database, Server-sent Events, and 
>> the Web Sockets API and protocol, all together in one document. With the 
>> exception of the Web Database spec, they're all now in last call at the 
>> WHATWG."
>>
>> Ian, could you please explain what you mean by "last call" in this 
>> context?
> 
> We're starting to see implementations of the WebSocket protocol, so I 
> wanted to encourage comments from the wider Web authoring community before 
> it's too late (i.e. before we are frozen by shipped implementations). In 
> the conventions we're using at the WHATWG (based on the W3C terminology), 
> the stability of spec sections is goes through First Draft, then Working 
> Draft, then Last Call, then Candidate Recommendation. (This corresponds 
> roughly to the formal WHATWG stages "Working Draft", "Call For Comments", 
> and "Call For Implementations" as described in the WHATWG charter.) You 
> can see the state of each section in the WHATWG draft by looking at the 
> little boxes in the right hand margin.
> ...

"Freezing" the protocol by having implementations being shipped *now* 
seems to be a problem if the protocol is supposed to become a work item 
of a future IETF WG.

BR, Julian