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

[James Seng <jseng@pobox.org.sg>]

-------- Original Message --------
Subject: Proposal for creation of new gTLD for IDN
Date: Thu, 6 Jul 2000 14:01:02 폝
From: "Deuk-Kul Jang" <dkjang@smind.co.kr>
To: "James Seng" <jseng@pobox.org.sg>,"Marc Blanchet"
<Marc.Blanchet@viagenie.qc.ca>,"idn mailing list" <idn@ops.ietf.org>

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