[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] compatibility chars in draft-ietf-idn-nameprep
- To: Frank Ernens <fgernens@enternet.com.au>
- Subject: Re: [idn] compatibility chars in draft-ietf-idn-nameprep
- From: Keith Moore <moore@cs.utk.edu>
- Date: Fri, 18 Aug 2000 00:48:08 -0400
- cc: idn@ops.ietf.org
- Delivery-date: Thu, 17 Aug 2000 21:49:36 -0700
- Envelope-to: idn-data@psg.com
>Whereas, someone who has an existing application which does almost
>no error checking and calls gethostbyname() will find it convenient
>to have that call convert from the locale 8-bit or multibyte character
>set and do the compatibility folding for them. If the resolver is
>in a dynamically linked library, the existing executable might work.
that's pretty unlikely to work in general. existing applications aren't
built to deal with 8-bit domain names, either in their parsing code or
in their display routines or in the data formats that they exchange
with other applications. overloading existing APIs with IDN semantics
strikes me as a good way to break a large number of things at once.
applications that don't know about IDNs shouldn't have to see them.
Keith