Re: Content-Disposition (new issue?)

Julian Reschke wrote:

> Considering that, it's seems best to remove all mentions of C-D
> from Part 3, and to create a separate spec that describes the 
> use of Content-Disposition within HTTP.
> Feedback appreciated,

If that separate draft ends up with *deprecating* Content-Dispo
you could as well deprecate it in 2616bis, and be done with it.

Similar, if the separate draft would say "experimental" with a
pointer to the old RFCs, no new insights, you could also do it
in 2616bis.  Nothing forces you to say "standard" and fix it in
2616bis, just because you mention it for the IANA registration.

But if separate draft is no much work and clearer from your POV
go for it.


Received on Sunday, 20 July 2008 17:24:20 UTC