Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)

Julian Reschke wrote:
> ...
> 2) After splitting the spec we define gzip/compress/deflate in Part 3, 
> although they can also act as Transfer-Codings (Part 1). Moving them 
> into Part 1 would thus put them all into a single place.
> (new issue: <>)
> ...

Done with revision 

There was One More Thing related to Transfer and Content Codings we 
discussed in Stockholm: the individual codings are really independent of 
the context they are used in, as RFC 2616 already stated:

"Although the value describes the content-coding, what is more important 
is that it indicates what decoding mechanism will be required to remove 
the encoding." -- 

So they really should be defined separately from Transfer-Coding and 
Content-Coding, and be collected in the same registry (surprise: IANA 
already has both in "http-parameters").

Feedback appreciated...

BR, Julian

Received on Friday, 7 August 2009 17:16:46 UTC