Re: [idn] opting out of SC/TC equivalence

["ben" <ben@cc-www.com>]

Hi David,

The ICANN Board's Internal Working Group asked:  "Presumably there
will be a demand for top level IDNs, i.e., [IDN].[IDN]. What role
should ICANN play with respect to the selection of these top level
names and their registries? What should be the role of the country
code registry of the country where a particular script is a native
script? And what if a particular script is a native script in more
than one country?"

I know ICANN is interested and I will show ICANN why in my 2 years of
gathering data from everyday people from all over the world that there
is indeed a need for lsTLDs (Language Script TLDs).

Thanks
Ben Chan

----- Original Message -----
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 4:41 PM
Subject: Re: [idn] opting out of SC/TC equivalence


-----BEGIN PGP SIGNED MESSAGE-----

ben wrote:
> Although the current ccTLDs and gTLDs will work for IDNs, they
cannot
> totally satisfy the needs of the users of CDNs.  Another type of TLD
> must be created and I will tentatively call it lsTLDs (Language
Script
> TLDs).  lsTLDs are in native language script... not English- thus
> bringing out the issue of <IDN>.<IDN> that ICANN has already
expressed
> their interest in.

I don't see why there would be any technical problem associated with
having non-ASCII TLDs. They're just like any other label, except that
the first octet must not be US-ASCII '0'-'9' (to allow a domain name
to
be distinguished from an IPv4 address).

(Obviously there are plenty of political problems associated with
adding
any TLD, but that's ICANN's problem.)

- --
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66
15 01
Nothing in this message is intended to be legally binding. If I revoke
a
public key but refuse to specify why, it is because the private key
has been
seized under the Regulation of Investigatory Powers Act; see
www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO3GjpzkCAxeYt5gVAQFHKwgAgVYwRwrUHqle97iXSQGajmNeL5CJLjub
OvHESgdLKTdT9HUxXx9Z71Iq5lzY+/5CZ5xQDV9UFKToKD79jzTh2YCVyr1cD67B
Ng8G3nq2mmsDWVWy4atwhgdhmSEf+XkDydsYvkOCOOy/u4o/LDMfS52vYtCyso6F
ZfvX/cy++kzBKnZ8zNDo+pP4hdzjJYZQl4bDG2xaZaZnakYjFVXRW8OFCNBdl0qL
1/zrfi0RTe5aSnxMCcqaxMxvI4Jp8hai6O+LnAaPrSTdeX3vTqFMRkau7vybCn5Q
rpMTVNjGP/xc4o6JESwOtUl8o9MyHyACwvpjFyL0EA0IbetMf9cAoA==
=OLJz
-----END PGP SIGNATURE-----