<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Tina,<br>
<br>
I believe my questions below are in no way related to the '.бг
case'. If the use of .бг confuses you, let's use .ελ as an example.
Does that help to avoid 'disclosure' of the case?<br>
<br>
We hope the applicant from Bulgaria will soon be on the list or if
they already are reading, will decide to participate.<br>
I have made it clear several times, that it was never my intention
to speak on their behalf. I really do not want to speak on their
behalf, for many different reasons.<br>
<br>
But, you see, I am part of the Bulgarian Internet community, in
several of my.. "capacities", such as, but not limited to - the
individual responsible for introduction of Internet in Bulgaria some
20+ years ago, the individual responsible for the creation and
operation of the BG ccTLD for the past 20 years, an active
participant in the local consultation process within Bulgaria
involved specifically with this case. Member of various ICANN
working groups. I am not going to list any ISOC etc memberships,
because you see, that is strictly irrelevant to this topic. By the
way, I also pretend to understand the specifics of the Cyrillic
script and it's relation to other scripts such as Greek or Latin.<br>
I have also some other knowledge, related to this issue, that I have
decided to remain untold. For now.<br>
<br>
I am aware there are several other members of the Bulgarian Internet
community who actively follow this discussion here. I have confirmed
this in several discussions we had already, including at the recent
domain.forum. It is their choice to speak here or not.<br>
<br>
By the way, this 'secrecy' is one of the indeed serious flaws in the
implementation of the IDN Fast Track process by ICANN. It serves no
other purpose but to ruin the trust ICANN has with the community.<br>
<br>
Daniel<br>
<br>
On 10.11.11 00:03, Tina Dam wrote:
<blockquote
cite="mid:CAN8jcvCDgNnNHArdwDP1aDWJri3mNhmxiCAs6Rzq2pGY84enYQ@mail.gmail.com"
type="cite">
<p>Hey Daniel, sorry but I said before, I cannot speak on behalf
of icann, nor about the specific case.</p>
<p>What I was doing was providing general information for both
limitations and options.</p>
<p>By the way, is the applicant from Bulgaria part of this list?
Maybe they would be able to provide more information, as it is,
in any event their decision on what to disclose.</p>
<p>Tina</p>
<div class="gmail_quote">On Nov 9, 2011 12:18 AM, "Daniel Kalchev"
<<a moz-do-not-send="true" href="mailto:daniel@digsys.bg">daniel@digsys.bg</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
On 07.11.11 20:03, Tina Dam wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Here it is in PDF. I was trying to show that by avoiding
ASCII at<br>
second level does not mean that we get rid of confusion - as
per<br>
Adam's suggestion.<br>
<br>
Tina<br>
</blockquote>
<br>
This is indeed true, however it brings few more questions:<br>
<br>
1. If there is no way to avoid confusion, why is ICANN so
obsessed to claim that .бг is indeed confusable, while it is
not? It is apparently not confusable on its own standing, even
less confusable attached to a second or third level string. (I
have more to say on this, but it be too long and I am not sure
I want to become an 'confusability' expert)<br>
<br>
2. How come then ICANN is going to accept the ad-hoc working
group recommendation to permit the Cyrillic (Bulgarian) and
Greek versions of .EU where "we found out that these strings
are really confusable, even if with their own versions, but
because EURID promised they will register only Cyrillic under
the Cyrillic version and only Greek under the Greek version,
we are going to accept it". This, from memory from the last
Dakar meeting.<br>
<br>
Tina, while you are not in charge of the second
recommendation, you certainly was in charge in the first.<br>
<br>
Thing is, confusion exist for humans always. Some humans are
easier confused than others, there is even medical terminology
on this subject. But.. thing is, human confusion is not the
business of ICANN as it is not their business to decide what
is a country and what is not.<br>
Before you say ICANN has a mission to avoid threats to
stability and security of internet:<br>
1. The .бг case (as I already cited) has clear opinion of the
security panel that it will not lead to problems for the
stability and security of the Internet.<br>
2. I am fine with exact and obvious matches, for ALL involved
characters. That is, a TLD consisting of Cyrillic or Greek
characters that exactly match Latin (ASCII) characters should
not be permitted. Such as (in Cyrillic) а, о, е, р, м, т
(funny enough, this character was never considered a problem
by ICANN until I brought it up in the Cyrillic VIP working
group).<br>
<br>
By the way, you speculate a bit about "Latin". It is ASCII, an
alphabet, based on Latin, that is used for the original TLD
names and therefore it is ASCII and not Latin that has to have
"priority" if any.<br>
<br>
Latin, just like Cyrillic and Greek should be "second grade"
if it is so decided in the ICANN world.<br>
According to some, it is even "third grade", at least for the
IDN Fast Track process.<br>
<br>
Daniel<br>
<br>
____________________________________________________________<br>
You received this message as a subscriber on the list:<br>
<a moz-do-not-send="true"
href="mailto:governance@lists.cpsr.org" target="_blank">governance@lists.cpsr.org</a><br>
To be removed from the list, visit:<br>
<a moz-do-not-send="true"
href="http://www.igcaucus.org/unsubscribing" target="_blank">http://www.igcaucus.org/unsubscribing</a><br>
<br>
For all other list information and functions, see:<br>
<a moz-do-not-send="true"
href="http://lists.cpsr.org/lists/info/governance"
target="_blank">http://lists.cpsr.org/lists/info/governance</a><br>
To edit your profile and to find the IGC's charter, see:<br>
<a moz-do-not-send="true" href="http://www.igcaucus.org/"
target="_blank">http://www.igcaucus.org/</a><br>
<br>
Translate this email: <a moz-do-not-send="true"
href="http://translate.google.com/translate_t"
target="_blank">http://translate.google.com/translate_t</a><br>
<br>
</blockquote>
</div>
</blockquote>
</body>
</html>