[governance] Is really Bulgarian Cyrillic .бг (.bg) similar to other Latin ccTLDs?
Imran Ahmed Shah
ias_pk at yahoo.com
Mon Nov 7 17:18:17 EST 2011
Dear Paul and all IGC Members.
If you are interested to know that who made the mistake, please study the following comments/recommendations of 22 February 2008 with the subject of “Introduction of IDN ccTLDs - Important Suggestions for Policy preparation of FastTrack”, http://forum.icann.org/lists/idn-cctld-issues/msg00011.html that highlight many issues but as we are discussing the naming convention, so I will discuss over here only one:
“Problem Identification:
It is proposed that basis of selecting 2 letter should be resolved first.
Now the question arises is that how this modification will be made.
For the reference of UN Authorities they already have abbreviation in 3 letters for country codes (please see http://unstats.un.org/unsd/methods/m49/m49alpha.htm)
For reference of M/s International Organization of Standardization (ISO), their systems and procedures were developed on the basis of traditional English abbreviations only to accommodate Internet Community which knows English Language. Now the requirement has been changed and demand arisen to develop Multilingual Internet to further accommodate 65% non-English Internet Users (about 820 million). So if the nonconformity is reported, International Organization Standardization has to resolve this issue by deputing their resources (support auditors) to develop well-documented nonconformity and change their standards to accommodate International Languages for the formation of Country and Regional codes of abbreviations. The criteria for the selection of abbreviations should be meaningful to adopt with in the community of the related Country/ Language. “
[IAS:] I have identified the problems of abbreviations and informed ICANN that the standard list that you are going to follow ISO-3166-1 two or three letters country codes is already lacking the abbreviations of the countries in their own respective language. If ICANN is following it, this list should be updated accordingly.
I also send letters & faxes to a. ISO International Offices, b. UN Office, c. World Bank International office at the same time
because ICANN was going to refer this document ISO-3166-1 as a standard list of the countries or territories for IDN ccTLD Fast Track Program.
[IAS:] The result of this initial recommendation also relaxed the two letters limitation so far…
[IAS:] It was better to prepare a list of Country Names and Country Code Abbreviations jointly by UN+ISO+WorldBank and each Country, each line of each country in his official language, and this list should be used as a standard of ISO by any organization, thus ICANN would follow that list and every one may be benefitted. For example, today ccTLD for each country is a standard two letter, Airlines Country Codes for each Country and City is accommodated in 3 letters. Each language community per country would be facilitated with their own abbreviations or country code name as IDN ccTLD.
Now you can better guess what was the one of basic problem of this system that was ignored.
Thanks and Regards
Imran Ahmad Shah
From: governance at lists.cpsr.org [mailto:governance at lists.cpsr.org] On Behalf Of Paul Lehto
Sent: Saturday, November 05, 2011 10:54 PM
To: governance at lists.cpsr.org; Avri Doria
Subject: Re: [governance] Is really Bulgarian Cyrillic .бг (.bg) similar to other Latin ccTLDs?
To the extent possible, a statement regarding "mutual mistake of fact" is usually grounds to get out of a contract or deal or understanding, and into a new process or negotiation. It also allows both parties to save face, in that both have made a mistake. I am not familiar enough with the details of the communications and its history to know if this would possibly apply or not, but if there is some basis for it, I'd advocate serious consideration of making mutual mistake an element of a letter urging reconsideration of this (non)decision.
Paul Lehto, J.D.
2011/11/5 Avri Doria <avri at acm.org>
Hi,
I think this is a good idea. If we can create an IGC consensus letter that
a. discusses this issue
b. asks for a transparent review of the issue
c. asks for a general process by which any ICANN Staff decision on string confusability have a method for transparent review and appeal.
I do not think we need to recommend a solution, but we might recommend policy considerations consistent with the Affirmation of Commitments that would govern such a review and apeal.
We might also want to copy the leadership of ALAC when the letter is sent asking for their support of such an appeal mechanism.
avri
On 5 Nov 2011, at 00:07, Ian Peter wrote:
> Avri wrote:
>
>> Well there is a new Board now, with a new chair.
>> All they need to do is recognize the mistake and tell the staff to fix it.
>> Takes a little courage, but a lot of people on that Board have courage.
>
> Perhaps a carefully drafted letter from this Caucus would be useful in this
> regard?
>
>
>
>
>> From: Avri Doria <avri at psg.com>
>> Reply-To: <governance at lists.cpsr.org>, Avri Doria <avri at psg.com>
>> Date: Fri, 4 Nov 2011 21:58:57 -0400
>> To: IGC <governance at lists.cpsr.org>
>> Subject: Re: [governance] Is really Bulgarian Cyrillic .бг (.bg) similar to
>> other Latin ccTLDs?
>>
>> Well there is a new Board now, with a new chair.
>> All they need to do is recognize the mistake and tell the staff to fix it.
>> Takes a little courage, but a lot of people on that Board have courage.
>>
>> avri
>>
>> On 4 Nov 2011, at 03:16, Daniel Kalchev wrote:
>>
>>>
>>>
>>> On 03.11.11 18:31, Paul Lehto wrote:
>>>> It would seem that there either is, or should be, a process to "call the
>>>> question" as they say in parliamentary procedure. If not, a motion can be
>>>> made for a decision, or a letter sent citing undue delay and calling for a
>>>> decision (with or without additional clarifying expertise appended to it). A
>>>> person familiar with whatever exists in terms of procedure can recommend the
>>>> best format or vehicle for forcing a decision.
>>>>
>>>
>>> There is no formal process to question the outcome of the IDN Fast Track
>>> applications. By definition, the only possible communication is between ICANN
>>> "staff" (whatever that means) and the original applicant. Ironically, even
>>> that country's Government does not have formal way to communicate with ICANN
>>> on the matter.
>>>
>>> Nevertheless, we are exploring every available possibility for some 18 months
>>> now, to understand why this situation continues to persist. ICANN staff are
>>> very wary of any such discussions and I perfectly understand their position.
>>> More so, that the principal that handled this case, Tina Dam, is no longer
>>> with ICANN.
>>> My understanding is that ICANN now recognizes they made a mistake. But they
>>> not only made the mistake to accept blindli this "expert opinion". They also
>>> made the mistake to make several statements already to the effect that "this
>>> is it, accept it or go away". Therefore, the problem at the moment is how
>>> ICANN admits their mistake and how they go out of the rising political
>>> problem.
>>> I have made many proposals on how to address this, but this has been slow
>>> process.. Nobody has given up anyway and it now seems inevitable things will
>>> go on a more global and more politicized forums.
>>>
>>> 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
>>
>
>
> ____________________________________________________________
> 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
--
Paul R Lehto, J.D.
P.O. Box 1
Ishpeming, MI 49849
lehto.paul at gmail.com
906-204-4026 (cell)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.igcaucus.org/pipermail/governance/attachments/20111108/95856a13/attachment.htm>
-------------- next part --------------
____________________________________________________________
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
More information about the Governance
mailing list