Re: [idn] Re: character tables

["JFC (Jefsey) Morfin" <[e-mail]>]

At 03:58 28/02/2005, John C Klensin wrote:
>To have three different, and incompatible, tables --associated with three 
>different registries-- for "the same language" is not only possible, but 
>likely.

There are 260 TLDs. There are 7260 languages, some of them having 2 or even 
3 scripts. There are around 13000 dialects of some importance (one consider 
that a language needs 100.000 people speaking it to survive. e-colonization 
(dominance of an e-culture) should probably lead to the initial deprecation 
of some languages, but recent history shows a cultural resistance and 
resurgence after such a chock.So one can consider that Internet will most 
probably help languages to survive and develop: a 50.000 people minium 
might be a good rule of thumb (think of trade, community idioms).

So roughly one can consider that 50.000 languages with possible 260 
variants (at TLD level) are to be considered when planning a solution able 
to scale. Obviously most of them will try to use the same script as much as 
they can for the TLDs. But this cannot be considered as systematic all 
throughout a language. So one has to consider 10 millions possibilities 
most of them synonyms or not implemented. I am just talking of the legacy: 
PADs may introduce 10 times this.

This looks an impossible task in following the IDNA internationalization 
concepts. I do not think it is a big deal for the DNS concepts if respected 
and real life constraints.

jfc

NB. The problem discussed was the phishing permitted by IDNA. Not to 
(re)build a consistent global namespace support by the DNS. The current 
grassroots process of which NETPIA is only one of the participants will 
necessarily address it, only because 86% of the people need it. IMHO if we 
wanted the IETF to do something positive in that area, we should start in 
making a review of all the existing solutions, projects, trends, and 
probable possibilities and try to give them some common guidance towards a 
common consistency.