[governance] Is really Bulgarian Cyrillic .бг (.bg) similar to other Latin ccTLDs?

[Imran Ahmed Shah]

Hi Tina and Daniel
The main problem in controlling the human's brain, the computer problem may be resolved as it is programmed by the human brain.

Following is an important example:
Just like TM, TM and ™ all examples are visually similar and identification was confusing, however, the people have learned about it after usage. Now the computer recognizes these first two examples are combination of two letter of ASCII character set and differentiate (superscript the positioning as well) them T as Decimal Code 84 and M as Decimal Character 77, while the third one Symbol used for an unregistered trademark (code =0153). 

However, the user human may be confused in between ASCI two letter combination TM (superscript) and the Symbol ™. Human Brain has support of six senses and memory expands with learning through the experiments as well. 

Now, it is understood that the IDN ccTLD Fast Track program was launched only for the communities of a non-latin official language countries that understand that language exclusively. And as once upon of time (Soul workshop), you have said that the string evaluation is a matter of the country itself, so, ICANN has to delegate this IDN ccTLD without gaining the margin to apply in the new gTLD (IDN) program or the waiting for the ccNSO “long-term” policy development for IDN ccTLD. I am believe that ICANN will allow all existing TLDs to create apply for their identical IDN strings in its next program but I strongly recommend that the Fast Track issue should be resolved with in the Fast Track itself, because the ICANN is an organization to which the users of Internet depends on and ICANN would never like to leave space for the users to seek alternate pole.

Thanks

Imran Ahmed Shah
> -----Original Message-----
> From: governance at lists.cpsr.org [mailto:governance at lists.cpsr.org] On
> Behalf Of Daniel Kalchev
> Sent: Wednesday, November 09, 2011 01:18 PM
> To: governance at lists.cpsr.org
> Subject: Re: [governance] Is really Bulgarian Cyrillic .бг (.bg) similar to other
> Latin ccTLDs?
> 
> 
> 
> On 07.11.11 20:03, Tina Dam wrote:
> > Here it is in PDF. I was trying to show that by avoiding ASCII at
> > second level does not mean that we get rid of confusion - as per
> > Adam's suggestion.
> >
> > Tina
> 
> This is indeed true, however it brings few more questions:
> 
> 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)
> 
> 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.
> 
> Tina, while you are not in charge of the second recommendation, you
> certainly was in charge in the first.
> 
> 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.
> Before you say ICANN has a mission to avoid threats to stability and security
> of internet:
> 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.
> 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).
> 
> 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.
> 
> Latin, just like Cyrillic and Greek should be "second grade" if it is so decided in
> the ICANN world.
> According to some, it is even "third grade", at least for the IDN Fast Track
> process.
> 
> Daniel
> 
> __________________________________________________________
> __
> You received this message as a subscriber on the list:
>      governance at lists.cpsr.org
> To be removed from the list, visit:
>      http://www.igcaucus.org/unsubscribing
> 
> For all other list information and functions, see:
>      http://lists.cpsr.org/lists/info/governance
> To edit your profile and to find the IGC's charter, see:
>      http://www.igcaucus.org/
> 
> Translate this email: http://translate.google.com/translate_t


____________________________________________________________
You received this message as a subscriber on the list:
     governance at lists.cpsr.org
To be removed from the list, visit:
     http://www.igcaucus.org/unsubscribing

For all other list information and functions, see:
     http://lists.cpsr.org/lists/info/governance
To edit your profile and to find the IGC's charter, see:
     http://www.igcaucus.org/

Translate this email: http://translate.google.com/translate_t