Bruce Lilly wrote:
Content-Transfer-Encoding actually specifies two nearly
independent items; an encoding and the domain of the
(possibly-encoded) content. Both of the currently
standardized encodings have a 7bit domain.
An alternative way of looking at deflate-8bit is that it
specifies *three* things; a compression method in addition
to the encoding and domain.
Other possible approaches would be to specify the compression
separately, either as a parameter (to Content-Disposition
perhaps) or via a separate "Content-Compression" header field.
The compression isn't a transfer encoding issue per se. It's
more of a disposition issue (the content could be saved either
in compressed or uncompressed form by the the recipient's UA).