Shawn Steele wrote:
a "you SHOULD do the obvious" norm does not really help, or does it ?
I think it does. EAI requires that the client software understand
UTF-8 (otherwise From: and To: look stupid), so any application
must therefore be able to handle UTF-8 in the body as well.
That's what I doubted: An EAI-aware MUA can of course handle UTF-8,
and hopefully the user of this MUA finds an e-mail service provider
with EAI-aware MSA / IMAP / POP3. But this user might still have
friends with less capable MUAs and service providers, or use mailing
lists and newsgroups where UTF-8 is not yet the norm.
A technical SHOULD trying to modify netiquette would make me nervous.
Limited to "SHOULD be the default" it is acceptable, this could be
added to the eai-scenarios and/or eai-email-clients draft.
