Re: [idn] IDNs in email message bodies

["James Seng/Personal" <James@Seng.cc>]

Erm, kind of bad idea to use x-ACE as TES for the whole body
content...We have qp and base64...lets leave it alone.

What the ppt is focusing on are the issues when IDN names appears on
RFC821 SMTP command, RFC822 headers (different depending whether it is
From, or Subject) or bodies. How can we work with ACE wrt to
encoding+TES used already in the body etc.

While this is interesting, I think if this topic develops further, we
should jump this to another mailing list, probably DRUM or other related
work on Mail.

-James Seng

----- Original Message -----
From: "Bob Jung" <bobj@netscape.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: "idn working group" <idn@ops.ietf.org>
Sent: Saturday, March 24, 2001 8:58 AM
Subject: Re: [idn] IDNs in email message bodies


> I have not looked at the talk, but I'd assume that if you want to send
> ACE-encoded email, then it should be treated as a MIME
> "Content-Transfer-Encoding" just like QP or base64.
>
> So, your message headers would include something like:
>
>                 Content-Type: text/plain; charset=UTF-8
>    Content-Transfer-Encoding:  x-ACE
>
> -bob
>
> "Adam M. Costello" wrote:
>
> > I just looked at the IDNs-in-MUAs talk (thanks to StarOffice).  I
agree
> > with it regarding the mail headers, but I have doubts about
performing
> > ACE conversions in message bodies.
> >
> > If the Content-Type is text/plain, then the message body is plain
> > text, pure and simple.  There should be no ACE encoding or decoding
> > happening there.  You can include strings that happen to be (and
look
> > like) ACE-encoded domain names, and you can include strings that
happen
> > to be (and look like) non-ACE-encoded IDNs, and in either case you
can
> > copy and paste them into your IDN-aware browser (or other
application,
> > including the MUA itself) and it will work (because that application
> > will perform ACE encoding if necessary).
> >
> > For MUAs that seek out URL-ish things in plain text message bodies
and
> > turn them into hyperlinks, they may need to perform conversions on
the
> > domain names for the purpose of creating the href attributes, but
the
> > visible text of the link should not be altered.
> >
> > AMC
>
>