[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] IDN character repertoire, nameprep
- To: "Adam M. Costello" <amc@cs.berkeley.edu>,<idn@ops.ietf.org>
- Subject: Re: [idn] IDN character repertoire, nameprep
- From: "Edmon" <edmon@neteka.com>
- Date: Tue, 20 Mar 2001 15:50:25 -0500
- Delivery-date: Tue, 20 Mar 2001 12:45:57 -0800
- Envelope-to: idn-data@psg.com
> > In order to prohibit characters, the DNS server has to undo the ACE
> > encoding. You have just started to modify DNS, something that many
> > people try desperatly to avoid.
>
> Good point, let me slightly amend the model. Whatever program
> translates the domain names into ACE in the first place should perform
> the prohibition at that time. This function could be performed by an
> enhanced DNS server that loads zone files containing natively-encoded
> domain names, or by a separate program that creates zone files
> containing ACEs.
>
I think this is probably the best way to do prohibition. In other words, it
is done during domain registration at the registry/DNS server whether it is
local or at the TLD and not at all dns applications. This way, new
characters could be more easily introduced. Which brings us to Bill
Manning's comment yesterday at the working group session which reminds us
that music is one other language!... luckily, musical symbols are included
in unicode, so we will be able to use it for domian names soon!...
Edmon