>> The compatibility/deployment issues are discussed over here:
> I think this fills a hole, is well thought out, and is being done
> cooperatively in the appropriate standards body. Julian has worked very
> hard at filing down the inconsistencies in the http space.
>> So the Internet Draft could proceed to LC and publication without any
>> implementation in browsers.
> I'd actually frown on that. One of the nice things rapid release and
> silent updates give us is the freedom to innovate without being locked
> into those choices for ever. Experience is good - data trumps documents.
> The IETF has always thought so. Being able to checkpoint at 6 week
> intervals lets us undo a bad idea before it becomes a defacto standard -
> that's much harder when its more than a draft we're talking about.
The spec is now in IETF Last Call, ending in four weeks from now. If
there's a problem with the definition, now would be the time to point it