At 4:51 PM 10/28/94, Keith Moore wrote:
In general a gateway into an EBCDIC world would not know what the
recipient's UA expects.
That may be so. In which case the gateway cannot help.
Even if the recipient's UA were known not to
expect MIME, the gateway would still have to translate the binary data into
some form which could be understood and extracted by the recipient's UA.
Right. The de-canonicalization step. This has to be done regardless of
the CTE. If the agent can do it, best. If the gateway knows the agent
can't, then the gateway (to be maximally useful) must.
In general, the BINARY c-t-e must be considered *incompatible* with
non-MIME UAs, just as is the case for q-p and base64.
Which is why a MIME to non-MIME gateway has to de-canonicalize it, just as
it has to decode *and* de-canonicalize qp or b64.
CTE: binary does not remove the requirement for canonicalization and
de-canonicalization.
--
Steve Dorner, Qualcomm Incorporated. "Oog make mission statement."