[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] IDNs in email message bodies
- To: "Adam M. Costello" <amc@cs.berkeley.edu>,<idn@ops.ietf.org>
- Subject: Re: [idn] IDNs in email message bodies
- From: "Edmon" <edmon@neteka.com>
- Date: Mon, 26 Mar 2001 16:48:07 -0500
- Delivery-date: Mon, 26 Mar 2001 13:43:49 -0800
- Envelope-to: idn-data@psg.com
>
> Edmon <edmon@neteka.com> wrote:
>
> > > 4. MUA uses the ACE in RFC822 From: and To: headers (as recommended
> > > in idn-mua I-D)
> >
> > I dont agree with 4. I believe that it is sufficient to use 2&3 and
> > leave the headers to be in existing MIME format because headers are
> > for display only.
>
> RFC 822 does not allow non-ASCII characters in domain names in
> structured header fields (like From: and To:), and MIME does not change
> that rule, so the only way to use IDNs there (without changing RFC 822)
> is via ACE.
>
> This is the only way that non-IDN-aware MUAs will be able to reply to
> messages sent from IDN addresses.
>
I was using the "MIME" word loosely and I appologise for that. What I meant
was using the RFC 2047 (MIME Part 3: Message Header Extensions for Non-ASCII
Text) format. In other words, extending MIME for header fields.
Edmon