[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sun, 3 Feb 2002 16:44:54 +0100 (MET)
Date: Sun, 3 Feb 2002 16:44:54 +0100 (MET)
From: Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>
To: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
Cc: Elisabeth.Porteneuve@cetp.ipsl.fr, Marc.Blanchet@viagenie.qc.ca,
email@example.com (Andrew McLaughlin), firstname.lastname@example.org,
email@example.com, firstname.lastname@example.org (Fred Baker),
email@example.com (Harald Alvestrand),
firstname.lastname@example.org (Hualin Qian),
email@example.com (Ho Jan-Ming),
firstname.lastname@example.org (H. T. Kung),
email@example.com (Kenny Huang), firstname.lastname@example.org,
email@example.com, firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org (James Seng/Personal),
email@example.com (John Klensin),
firstname.lastname@example.org (Xiaodong Lee),
email@example.com (Stuart Lynn), firstname.lastname@example.org (Wei Mao),
email@example.com (Masanobu Katoh),
firstname.lastname@example.org (Mouhamet Diop),
email@example.com (Thomas Narten),
firstname.lastname@example.org (Erik Nordmark),
email@example.com (Patrik Falstrom),
firstname.lastname@example.org (Paul Hoffman),
email@example.com (Qiheng Hu),
firstname.lastname@example.org (Mohamed Sharil Tarmizi),
email@example.com (Sang-Hyon Kyong),
firstname.lastname@example.org (Nai-Wen Hsu), email@example.com,
firstname.lastname@example.org (Li Ming Tseng),
email@example.com (Vint Cerf),
firstname.lastname@example.org (Zhang Wen Hui),
email@example.com (Wen-Sung Chen),
firstname.lastname@example.org (Chun-Hsin Wu), email@example.com
Subject: [idn] Re: Chinese Domain Name Consortium (CDNC) Declaration
Dear Xiang Deng,
Thank you very much indeed to insist on the problem,
and provide an excellent pedagogical explanation using
"a" and "A", and refering to the economy and cost.
Latin and Cyrillic scripts have completely different
code points in Unicode, while these scripts share many
signs which are the same when printed on paper or on screen.
No need to add that the upper and lower case of letters are
different code points in Latin script and in Cyrillic script.
The combinatory effects are terrible, and they are language
independent. It is the same everywhere, not only for Chinese
code points. Pure maths, the same for everyone.
Assume Chinese name of 10 glyphs. Each one may take 2 versions,
TC or SC. The number of possible configurations is 2**10 = 1024.
It means that to effectively register a name (i.e., get all
of the predicable variants pointing to the same place)
of 10 glyphs one have to pay 1024 times for such a domain name.
Assume now a Latin or Cyrillic name of 10 signs. The same
reasoning apply, each character in Unicode have two different
versions, one Latin, one Cyrillic. And I forget the upper and
lower case, "a" and "A".
The number of possible configurations is 2**10 = 1024.
It means that to effectively register a name of 10 code points
and protect it in Latin and Cyrillic scripts one have to pay
1024 times more than in "LDH".
For a label of 5 code points we have 32 times the cost,
for 5 - 64, for 7 - 128, etc. It is tremendous cost increase.
The company "MacDonald", 9 code points, will have to buy
2**9 variants of its name, 512, pointing to the same place.
The company "ICANN", 5 code points, will have to buy 2**5
variants of its name.
It reminds me about the inventor of chess game, who requested
to be paid in grains, 2 to the power of number of squares,
2 to the power of 64. There was not enough grains on the Earth
to pay for it.
There is not enough grains now. What will be the effect on world
economy ? Is ICANN going to announce to the world that it must
multiply its Internet names budget by a factor of hundred or
thousand to be able to face IDN coming ?
What makes me even more scared is to announce to the world that
the printed information with URLs, on paper or screens alike,
will become useless.
The printed names will be undefined without having script
precised for each and every sign. The real chaos.
> From firstname.lastname@example.org Sat Feb 2 05:14 MET 2002
> Message-ID: <013101c1ab9f$41ae8270$4407e29f@deng>
> From: "xiang deng" <email@example.com>
> To: <firstname.lastname@example.org>, "Erin Chen" <email@example.com>
> Cc: "Vinton G. Cerf" <firstname.lastname@example.org>, "Masanobu Katoh <"
> "John klensin" <email@example.com>, "Stuart Lynn"
> "Mohamed Sharil Tarmizi" <firstname.lastname@example.org>,
> "JET Members" <email@example.com>,
> "Masanobu Katoh" <firstname.lastname@example.org>,
> "Mouhamet Diop" <email@example.com>, "Patrik F?lstr?m"
> "Qiheng Hu" <firstname.lastname@example.org>,
> "Sang-Hyon Kyong" <email@example.com>,
> "Elisabeth Porteneuve" <Elisabeth.Porteneuve@cetp.ipsl.fr>,
> "hlqian" <firstname.lastname@example.org>, "mao" <email@example.com>,
> "Zhang Wen Hui" <firstname.lastname@example.org>,
> "tsenglm@-poo???s.???j.tw" <email@example.com>,
> "hoho" <firstname.lastname@example.org>,
> "Kenny Huang" <email@example.com>,
> "Chun-Hsin Wu" <firstname.lastname@example.org>,
> "sstseng" <email@example.com>,
> "Wen-Sung Chen" <firstname.lastname@example.org>, "yktham"
> "jasonho" <email@example.com>, "alanysho"
> "christine" <firstname.lastname@example.org>
> Subject: Re: Chinese Domain Name Consortium (CDNC) Declaration
> Date: Sat, 2 Feb 2002 12:08:23 +0800
> Dear Andrew:
> Let me use my awkward English to do some explanations.
> 1. Identifier and name
> From technical argument, IDN Protocol is discussing identifier only,
> they are no meaning, no relationship totally, just identifier to
> distinguish each other.
> But thing is more complex. These identifiers are not just used in
> technical protocol, they are names which users must pay for.
> So the identifier is identifier like name.
> 2. Traditional & Simplified Chinese character
> In Chinese characters, there is a small subset. In this subset, two
> glyphs have same meaning, same connotation,same extension, and
> we can substitute one with the other in any situation without
> anything. (such as: A & a) They have different code point in
> they are different identifier, they are different domain name.
> 3. Delegation problem and registration-level solution
> For example:
> registration-level solution: A -> 184.108.40.206
> a -> 220.127.116.11
> Delegation problem:
> / \
> A a
> / \ / \
> A a A a
> / \ / \ / \ /\
> A a A a A a A a
> If I have a Chinese domain name a.a.a, I will
> ask level-one\level-two\level-three to follow the
> regulation synchronously, and will config my
> mail server, web server or other server 8 times.
> If there is a new network application like ENUM
> in future, the level relationship is so important to
> this application, how about Chinese domain name?
> 4. about Prohibit
> My comprehension about "prohibit" is pending up temporarily.
> It's the usual method to deal with unsolved part of a big problem.
> 5. Relationship among CJK
> 2001.11.18 CDNC-JET Beijing Meeting had reach consensus
> about solve CJK issue.
> I think one principle is:
> It's a bi-blade sword, the solution don't be detrimental to each
> Personal best regards
> Deng xiang
> > ----- Original Message -----
> > From: "Andrew McLaughlin" <email@example.com>
> > Dear Erin:
> > Thank you for communicating this CDNC declaration. These are
> > concerns; we will study them carefully.
> > In order to improve my understanding, could I please ask for some
> > information about one point: registration policy. You state that
> > of an equivalence-mapping capability for traditional/simplified
> > characters "can't be compensated by registration policy." Could you
> > explain? I am wondering why DNS registries that offer Chinese
> > domain names could not simply ensure that any domain name
> > traditional Chinese characters is matched with an equivalent
> > simplified Chinese characters (and vice versa). DNS nameserver
> > would be the same for both the traditional and the simplified domain
> > (I understand that this is not an ideal solution, in that it places
> > much DNS configuration by domain name registrants).
> > It would be very helpful to me and others to understand why a
> > registration-level solution is insufficient.
> > Best regards,
> > --andrew
> > andrew mclaughlin - vice president & chief policy officer
> > internet corporation for assigned names and numbers
> > <firstname.lastname@example.org> <http://www.icann.org>