[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] UTF-8 / RACE
- To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
- Subject: Re: [idn] UTF-8 / RACE
- From: "James Seng/Personal" <James@Seng.cc>
- Date: Mon, 28 May 2001 05:51:08 +0800
- Delivery-date: Sun, 27 May 2001 14:52:07 -0700
- Envelope-to: idn-data@psg.com
> My web page carefully specifies details of the ACE solution: where ACE
> is used, where it is not used, and what has to be changed to make that
> work. The reason that gethostbyname() has to be upgraded, for example,
> is that ACE is not used in ``command lines for telnet, ssh, etc.'' but
> ACE is used in ``DNS queries and responses.''
If we were to consider telnet/ssh etc as "Applications" and then look at
IDNA:
*If* we adopt IDNA, then telnet/ssh etc have to be upgraded to be IDNA
compatible. So we will end up with IDNA-enabled telnet/ssh or
non-IDNA-enabled telnet/ssh. Sad but true. On the bright-side, only
users would needs IDNA-enabled telnet would need to upgrade their
telnet.
Upgrading gethostbyname() is not in-line with IDNA. In fact, by
upgrading gethostbyname(), you are doing IDNRA not IDNA. Correct me if I
am wrong, but IDNRA has already been given up by the authors.
Therefore, I do not think gethostbyname() should be upgraded (again, on
the assumption that IDNA is been adopted).
-James Seng