[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] compatibility chars in draft-ietf-idn-nameprep
- To: RJ Atkinson <rja@inet.org>
- Subject: Re: [idn] compatibility chars in draft-ietf-idn-nameprep
- From: Keith Moore <moore@cs.utk.edu>
- Date: Wed, 16 Aug 2000 09:20:10 -0400
- cc: idn@ops.ietf.org
- Delivery-date: Wed, 16 Aug 2000 06:20:33 -0700
- Envelope-to: idn-data@psg.com
> So, for that reason, I think that while it is reasonable
> to prohibit certain characters from use "on the wire", it is
> unreasonable to prohibit all user interfaces from converting from
> a prohibited character to an *fully equivalent* allowed character.
perhaps. but in such cases it's important that the protocol
(and API) used doesn't confuse the two. If some layer translates
a prohibited character into a permitted one, then the protocol
and API need to provide the feedback to the application -
here's what you typed, here's what I assumed you meant.
That way it as at least possible to write applications which
handle these things reasonably.
(applications used to do this with domain names- if you typed in
a name which mapped to a CNAME the app would then display the
name indicated by the CNAME record)
Keith