RE: [idn] Proposal for creation of new gTLD for IDN

["Seungik Lee" <silee@icu.ac.kr>]

I'm a stranger here, and maybe I couldn't follow up all of the topics discussed here. Therefore, what I am saying could be duplicated one.
But excuse me that I comment on this topic at first.

I think it's a great method for encoding multilingual domain name into a kind of ACE format.
We can apply this on locale-dependent case-folding or recognizing the local character sets, - of course that it is already discussed - with a language-key.

However, I am afraid that we cannot choose a *specific* multilingual-key or *specific* language-keys that make no confusion with the original domain names.
Another one: If I copied & pasted some URLs from the other locale systems, what could be happened? I am not sure, but I think it still adds a language-key of my own locale not the one of URL's.

The new gTLDs or cc2LDs are already suggested and being on service by NUBIND, etc. I think it's not such a topic that idn wg focuses on.
If I had misunderstood your document, correct me. ;)


----------------------------------------------------------
Lee Seung-ik, M.S. course student
Collaborative Distributed Systems & Network Lab.
ICU (Information & Communications University)

E-mail: silee@icu.ac.kr
Address: 58-4 Whaam-dong Yuseong-gu Taejon, 305-348 Korea
Tel. #: +82-42-866-6163 (office), +82-42-866-6592 (dorm.)
HP: 011-9820-0688
ICQ: 24731319
Homepage: http://cds.icu.ac.kr/
----------------------------------------------------------
 

-----Original Message-----
From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of Deuk-Kul Jang
Sent: Thursday, July 06, 2000 5:47 PM
To: James Seng; Marc Blanchet; idn mailing list
Subject: [idn] Proposal for creation of new gTLD for IDN


Hallelujah    Hallelujah    Hallelujah


This proposal is concerning an Internet Draft for an encoding for IDN
(http://www.ietf.org/internet-drafts/draft-dkjang-idn-00.txt), that
represent a method for internationalized domain name as below.

-------------------------------
     When a multilingual domain name is converted to the traditional one.
     1. The 'multilingual key' is included automatically in converted names.
     2. The 'language key' is included automatically in the converted
names.
     3. All characters are replaced by 'character substitutes'.
     4. The top level domains are directly translated by the conversion
program.
-------------------------------

Only for IDN, if new gTLDs, such as '.icom'(or .ico) .'inet'(or .ine) ----,
can be created, then new gTLDs will be the 'multilingual key' of No1 by
itself.
Consequently, it is no use to include a multilingual key into a converted
domain name.

For example, a Korean language domain name of
'0xb300/0xd55c/0xbbfc/0xad5d/.0xd68c/0xc0ac/' will be encoded to
'kr2ds96445y1a5.icom' without multilingual key 'z-', instead of
'z-kr2ds96445y1a5.com'.

And if cc2LDs(country code 2nd level domain) can be used, such as '.kr.icom'
'.jp.icom' ----,  then cc2LD will be the language key by itself too.

Finally, the example will be encoded to '2ds96445y1a5.kr.icom'.

P.S.

For IDN, if cc2LD happen to be available under current gTLD, such as
'.kr.com' '.jp.com' ----, the cc2LD can be the multilingual key and the
language key simultaneously.
Then, we can launch IDN immediately without creating new gTLD.

sincerely yours.

Deuk-Kul Jang
dkjang@smind.co.kr