I'd really like to keep the content-encoding simple. I'm not convinced
that allowing multiple nested encodings is beneficial enough to be worth
the extra cost involved.
As to compression, I would personally be happy to either include a
compressed-message content-type or a compressed content-encoding, if
someone knowledgable about compression can write up a good, exhaustive,
implementable, legally not-a-rat-hole specification. I'm simply not
qualified.
The same "I want to see a rigorous spec" philosophy applies, in my mind,
to specifying the use of uuencode. -- Nathaniel