Re: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt

["FDU - Sung Jae Shim" <sshim@mailbox.fdu.edu>]

Harald,

Thank you for providing me with an example. Allow me explain how the example
can be handled in VIDN. Please see below.

Sung

----- Original Message -----
From: Harald Alvestrand <Harald@Alvestrand.no>
To: FDU - Sung Jae Shim <sshim@mailbox.fdu.edu>; Brian W. Spolarich
<briansp@walid.com>
Cc: <idn@ops.ietf.org>
Sent: Friday, November 24, 2000 8:16 AM
Subject: Re: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt


At 16:01 23/11/2000 -0500, FDU - Sung Jae Shim wrote:
>Sung: If you know any local language other than English, please take a look
>at domain names currently used in the regions where the local language is
>widely spoken. I am sure that you will see some common patterns in those
>domain names, regarding how the characters of the local language are
>transliterated into the characters of English. VIDN uses these common
>patterns of transliteration in converting non-ASCII characters into ASCII
>characters.

The common patterns of Europe produce non-reversible mappings.
dør, doer and dor are 3 different words with separate meanings (door,
toilets and carpenter's tool); the 2 most common mappings map the first
word into the 2 others.

Harald



Sung: In the example above, it seems to me that "dør", "doer" and "dor"
have different meanings in a local language but represent the phonemes that
have the same or very proximate sounds. Since it is common that "dør" in
non-ASCII format is transliterated into either "doer" or "dor" in ASCII
format, these three words may be represented in the current DNS as follows:

(1-1) "dør" (non-ASCII) ---> "doer" (ASCII) or "dor" (ASCII)
(2-1) "doer" (non-ASCII) ---> "doer" (ASCII)
(3-1) "dor" (non-ASCII) ---> "dor" (ASCII)

If we assume that "doer" (ASCII) in (2-1) and "dor" (ASCII) in (3-1) are
already
registered in the DNS, then "dør" (non-ASCII) in (1-1) may be registered as
"doer2" (ASCII) or "dor2" (ASCII) in the current DNS. In other words,

(1-2) "dør2" (non-ASCII) ---> "doer2" (ASCII) or "dor2" (ASCII)
(2-1) "doer" (non-ASCII) ---> "doer" (ASCII)
(3-1) "dor" (non-ASCII) ---> "dor" (ASCII)

Further, let's assume that "dør2" (non-ASCII) in (1-2) is registered as
"doer2" (ASCII) and another name "dor2" (non-ASCII) is registered by an
entity as "dor2" (ASCII) in the current DNS. Then, the following is
possible:

(1-3) "dør2" (non-ASCII) ---> "doer2" (ASCII)
(2-1) "doer" (non-ASCII) ---> "doer" (ASCII)
(3-1) "dor" (non-ASCII) ---> "dor" (ASCII)
(4-1) "dor2" (non-ASCII) ---> "dor2" (ASCII)

So far, there is nothing to do with VIDN. These may be the ways people
speaking the local language create domain names in ASCII format in the
current DNS.

Now, VIDN assigns a unique code to each set of names in non-ASCII and ASCII
formats. Please see the draft for details of one-to-one matching scheme of
VIDN.

(1-3) "dør2" (non-ASCII, VIDN-generated code = 'a13') <---> "doer2" (ASCII,
pre-assigned code: 'a13')
(2-1) "doer" (non-ASCII, VIDN-generated code = 'b21') <---> "doer" (ASCII,
pre-assigned code = 'b21')
(3-1) "dor" (non-ASCII, VIDN-generated code = 'c31') <---> "dor" (ASCII,
pre-assigned code = 'c31')
(4-1) "dor2" (non-ASCII, VIDN-generated code = 'd41') <---> "dor2" (ASCII,
pre-assigned code = 'd41')

As shown above, VIDN achieves a one-to-one, reversible mapping, using the
code-matching scheme. In VIDN, there is no need to make any change to the
current DNS, and both the names in non-ASCII format and their corresponding
names in ASCII format are intelligible in the local context. No new name is
created to use names in the local language.

When the end-user enters "dør2" (non-ASCII), then VIDN connects to "doer2"
(ASCII) that has the matching code and list "dor2" (ASCII) that has a
different code as an alternative. When the end-user enters "doer"
(non-ASCII), then VIDN connects to "doer" (ASCII) that has the matching code
and list "dor" (ASCII) that has a different code as an alternative. When the
end-user enters "dor" (non-ASCII), then VIDN connects to "dor" (ASCII) that
has the matching code and list "doer" (ASCII) that has a different code as
an alternative. When the end-user enters "dor2" (non-ASCII), then VIDN
connects to "dor2" (ASCII) that has the matching code and list "doer2"
(ASCII) that has a different code as an alternative.

Of course, in this process of mapping, VIDN can check whether the names in
ASCII format are active or not on the Internet, and consider only those
active ones.



--
Harald Tveit Alvestrand, alvestrand@cisco.com
+47 41 44 29 94
Personal email: Harald@Alvestrand.no