headers
Adam M. Costello | 1 May 23:37

Re: Two Internet Drafts of possible interest

John C Klensin <klensin <at> jck.com> wrote:

> http://www.ietf.org/internet-drafts/draft-klensin-idn-tld-02.txt

Section 3.1:

> A user in Korea who can access the national ccTLD in the Korean
> language and character set has every reason to expect that both
> generic top level domains and domains associated with other countries
> would be similarly accessible, especially if the second-level domains
> bear Korean names.

If there are Korean labels registered under a France TLD, then users
would certainly benefit from being able to access those domains using a
Korean translation of ".fr".  I see no benefit in ensuring that French
or Chinese labels are accessible under the Korean translation of ".fr".
If a solution happens to make domains accessible under counter-intuitive
TLDs (via some sort of local or global aliasing), that's fine, but it
doesn't need to be a goal.

> That level of local optimization is not realistic -- some would
> argue not possible -- with the DNS since it would ultimately require
> that every top level domain be replicated for each of the world's
> languages.  That replication process would involve not just the top
> level domain itself: in principle, all of its subtrees would need to
> be completely replicated as well.

I don't see the benefit of replicating the subtrees.  If Korean and
Chinese translations of ".fr" exist, and if I have a server that I
want to be accessible via Korean and Chinese domain names, why would I
(Continue reading)

Permalink | Reply | 1 comment |
headers
JFC (Jefsey) Morfin | 2 May 06:22

Re: Two Internet Drafts of possible interest

Dear John, Adam,
I will put myself in a different perspective to address the ML.ML situation.
- there are 54 different scriptings supported where all the TLD may 
probably be trimmed down to a 100 maximum (ideally 54) scripts.
- there is one particular existing scripting made of "numbers" from 0 to Z 
and minus, supporting a non conflicting convertion function from the other 
53 scripting codes (punycode). (As per the common understanding of the word 
I name it "international", "internationalized domain names" are ML domain 
names which can be internationalized in 0-Z and backed ito their initial 
codes, using punycode).
- there is a low work on aliasing because NSI did not understand yet that 
helping hosting companies to support aliasing was multiplying DN sales. But 
there will be an increasing need for aliasing and complex host access 
address management with IPv6, new mail services, etc. and when other 
Registries understand the golden mine aliasing maybe for them.
- the DNS is not only Bind. What is important in all this is the protocol. 
The DNS back office can change, to support new management concepts and 
services, keeping or not flat db.files. As different existing tools show it.
- IDNA is going to ask for an IDNA module to be added to the applications 
or to the resolver. This module can do more.
- multilingual real life will _demand_ everything monolingual people tend 
to consider as unlikely. This is not questionable.

There are three key concepts to use.
1. virtual zones.
These zones correspond to a real life zone that does not match 
(smaller/larger) any DNS made zone. An example of virtual zone are all the 
aliases of a same domain - which can be of different level.

2. ULD (user level domain).
(Continue reading)

Permalink | Reply | 0 comments |

Gmane