[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [idn] IDNs and email
- To: firstname.lastname@example.org
- Subject: RE: [idn] IDNs and email
- From: Andrew Draper <ADRAPER@altera.com>
- Date: Wed, 16 Feb 2000 02:54:51 -0800
- Delivery-date: Wed, 16 Feb 2000 02:50:53 -0800
- Envelope-to: email@example.com
Paul Hoffman / IMC wrote:
> At 09:15 AM 2/15/00 -0800, firstname.lastname@example.org wrote:
> > > | If an encoding is used which is not mapped into ASCII then there
> > > | be an ASCII-only representation of each IDN, and there MUST be a way
> > > | a program to find the ASCII-only representation (or lack of it) for
> > > | IDN.
> >Nicely put. I agree completely.
> There are two issues here: ASCII and DNS-compatible names. Protocols like
> SMTP and PKIX require ASCII, but there may be protocols that define
> DNS-strings to single-case letters plus digits plus '-' only. If such
> protocols exist (and I don't know that they do, but I wouldn't be
> surprised), do we want to accommodate those as well?
I don't know of any such protocols but also suspect they exist. Do we need
find an example before we start to design around them?
I meant a DNS-compatible name but couldn't think of a clear way to say what
meant. What about using hostname-charset instead of ASCII-only? This
the requirement to:
| If an encoding is used which is not mapped into the hostname charset then
| there SHOULD be a hostname-charset representation of each IDN, and there
| MUST be a way for a program to find the hostname-charset representation
| (or lack of it) for an IDN.
There should probably be a definition of hostname-charset somewhere as well:
| hostname-charset. This is the character set which is legal in legacy
| names (before IDN). It consists of the ASCII characters A-Z (case
| matching), the digits 0-9 and the hyphen.
Of course if someone can find a reference instead then that would be better.