Excerpts from mail: 9-Dec-94 Re: Don't change RFC822 for.. Masataka
Ohta(_at_)necom830(_dot_)c (1712)
So, don't try to pretend that MIME has solved the I18N issue and
let ISO-2022-INT-* address the untouched issue.
OK. But when sending mail outside the subworld in which you can expect
ISO-2022-JP* to work, please continue to tag the message with a MIME
header so that readers can guess what's inside. And even if the other
IETF group ever reconciles ISO-2022-INT-* to the rest of the texts in
the Internet, it would still be appropriate to tag MIME messages to say
ISO-2022-whatever. The cost is low.
I don't believe that it's necessary that an ISO-2022-JP* enclave has to
start using those tags internally, though it probably wouldn't hurt to
begin using them as convenient, and it would prevent oddities from
slipping out through unexpected gateways. And when/if the entire world
uses ISO-2022-INT* kinds of encodings, MIME tags will still be useful
for designating the exceptions.
Craig