On Thu, 26 Mar 1992 16:26:28 -0500 (EST) you said:
I don't think a new type is needed. I believe that using
application/octet-stream will work fine. The CRLF issue may be a
problem in some contexts if you use base64 for transfer-encoding, but
should NEVER be a problem if you use quoted-printable. (That's what the
recent debate about newline-in-quoted-printable was all about.)
Oh no, please... If, at this stage, it can still be written down that the
choice of encoding method has anything to do with the kind of object
transported, I am afraid a big SHOW-STOPPER flag should be raised.
By the way : as far as I have understood the latest draft, application/
octet-stream does not designate a canonical representation which includes
a way the represent line breaks. So, if such an object is encoded in q-p,
there will be no hard line breaks in the encoding. And it will be convertible
to base64. /AF