I have no problem in principle with calling out any particular 2022
profile, permitting it, and designating it with whatever mechanism is
used to designate other header character sets.
The problem is only with identifying "ISO 2022", without indication of,
and prior agreement on, a profile, as if it were a character set.
Given that people will want to use RFC-XXXX conformant email software
in Japan, and that the Internet Draft version of RFC-XXXX requires the
specification of the character set, and that the JUNET profile of ISO
2022 will have to be used in Japan, we must come up with a name for,
at the very least, the JUNET 2022 profile, or perhaps a more
extensible 2022 profile that could accommodate the Koreans and Chinese
as well.
Since a new draft of RFC-XXXX is imminent, I guess we should wait for
it, and then present copies to the relevant people in Asia, and
discuss the ISO 2022 issue.
p.s.: I would caution, however, that there is mail software (mostly
receiving UAs) on the network that will strip apparent escape sequences
(or the ESC character) on the theory that they are protecting users
against screen-killers.
I don't know about any email software that strips ESCs in message
bodies, but I do know about netnews software that does this. Anyway, I
consider it highly unlikely that the Japanese will all switch to a
different character encoding just because some Americans are paranoid
about "screen-killers"! :-)
Cheers,
EvdP