A text to correct
- To: <idn-cctld-issues@xxxxxxxxx>
- Subject: A text to correct
- From: "philemon" <philemon@xxxxxxxxxx>
- Date: Mon, 28 Jan 2008 11:16:23 +0100
The text i sent last time has many othograph mistakes for some reasons; instead
please consider the text below. I will appreciate if you can change the
previous text you pasted on the website.
The 'apparent' use of symbol outside the US-ASCII character for ccTLDs strings
is today considered as a real matter which one must take a keen interest in. In
this purpose one needs clear policies as global guidelines.
I think, as it is evocated in the overview of this public call for comment,
that a PDP for the introduction of ccTLD as IDNs is now more and more necessary
to get further forward on this issue, and also try to stop, if it is still
possible, all patched initiatives taken upon here and there; and bring them is
the global umbrella.
However, I don't share the idea of making a kind of the IDN equivalent of the
3166-list, because many countries will never use the IDN version of their
respective ccTLD. In addition, it will be difficult to choose in what script(s)
each ccTLD should be written. Instead, on should consider different IDN ccTLDs
by country by valued script(s). It's means: no script for a given country, no
IDN ccTLD, at less now.
Back to the PDP issue; why not just upgrade the existing ICANN bylaws by taking
into account the aspects relating to the IDN ccTLDs. This will permit to have
one PDP for both types of ccTLDs. In this way, one will only change some
articles of the current bylaws, and this will also substantially reduce the
timeline of resolving this issue.
Anyway the ICANN board had already asked to the ccNSO and GAC to produce a list
of IDN ccTLD associated with the 3166 two letter codes. The answers to the
questions raised in the issues paper produced by the jointed Working group,
constituted an important basis for setting up an PDP, even if it will be
KISSANGOU Jean Philemon
Directeur Technique DRTVnet (ISP)
BP. 2852 Brazzaville Congo