I think the standard should satisfy followings:
- Content-Type must indicate the type of the body properly (of course)
- any combination of Content-Type and C-T-Encoding should be possible
- any order of recursive (nested) C-T-Encodings should be applicable
oh no, not this argument again...
Maybe I reinvented something rejected in past but I'm curious why using
message/rfc822 for nested encoding is not good.
the more levels of encoding you have, the less chance you
have of being able to interoperate.