Fw: [idn] IDNs in email message bodies

["Edmon" <edmon@neteka.com>]

> > > 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.
> >
> > no.  not only is this not "in fact", it's simply incorrect.
> > the addresses in the message header are intended both for display
> > and for use in forming replies.
> >
> > also, in practice, RFC 2047 encoded-words are routinely decoded,
> > translated, re-encoded, and/or corrupted by mail transports and
> > delivery systems.
> >
>
> Yes they are used for both display and for "forming" replies, and it is
> during this "forming" process where the ACE conversion should take place.
> The information itself within the field is for display and we should not
> confuse it with the actual protocol for transportation.  Just like typing
a
> domain name in the URL bar or copy and pasting into the URL bar, you
should
> see the multilingual domain there! and not be forced to type an ACE
domain.
>
> Edmon
>
>