[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] IDNs in email message bodies
- To: "Eric A. Hall" <ehall@ehsco.com>
- Subject: Re: [idn] IDNs in email message bodies
- From: Keith Moore <moore@cs.utk.edu>
- Date: Mon, 26 Mar 2001 16:05:06 -0500
- cc: Patrik Fältström <paf@cisco.com>, idn working group <idn@ops.ietf.org>
- Delivery-date: Mon, 26 Mar 2001 13:05:28 -0800
- Envelope-to: idn-data@psg.com
> HELO, PATH, HTTP sequences and other "pushed" names can be ACE, or they
> can use an RFC-2047 style encoding syntax.
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.
(note that even if you use 2047 to encode nameprepped Unicode, there is
more than one way to encode such names... names encoded in such a way
cannot be compared for equivalence as if they were ascii)
any domain name that appears in a protocol element that is intended to be
*interpreted* or *compared* (as opposed to merely *displayed*) needs to
be ACE-encoded.
Keith