Adam M. Costello
<ietf-822(_dot_)amc+0(_at_)nicemice(_dot_)net(_dot_)RemoveThisWord>
schrieb/wrote:
Content-Type: meta/encoded
Content-Encodings:
foo; param=value; param=value,
bar; param=value; param=value,
gzip
Content-Decoded-Type: application/postscript
Content-Disposition: attachment; filename="hello.ps.foo.bar.gz"
Content-Transfer-Encoding: escaped-8bit
Well, that would be quit similar to an encapsulation within a new
message-like body type:
Content-Type: application/message-partial; number=1; total=1;
id="sdfvwef34rzsdkvchn(_at_)example(_dot_)com"
Content-Transfer-Encoding: 8bit
Content-Type: application/postscript
Content-Disposition: attachment; filename="hello.ps"
Content-Transfer-Encoding: quoted-binary; foo="bar"
Content-Encoding: gzip (from HTTP)
Content-Required-Fields: Type, Transfer-Encoding, Encoding (list of
fields which a EMIME parser must know to fully decode the
entity)
The advantage of this is: If it crosses the border to the non-8bit
world, everything inside the enclosing entity can be encoded with qp or
base64.
Claus
--
http://www.faerber.muc.de/