Re: [idn] IDNs in email message bodies

[Edmon]

>
> as far as I'm concerned, RFC 2047 encoding is a non-starter for domain
names
> in protocol elements.  2047 was specifically designed to encode text whose
> only purpose was to be presented to a user; and it therefore completely
> skirts all issues related to normalization, canonicalization, etc.
>

While I agree to a certain degree (within the protocol and
transportation/routing), I would like to say that in the context of this
discussion where we are disucssing the "message headers" and "content body"
of an email, the information is in fact for display purpose.  And as you
have precisely pointed out, cases should be preserved.  That is if I typed
in "[EMAIL PROTECTED]"
for example, it should be displayed as is after it is sent to the recipient.
An ace representation would not preserve the case.

Edmon