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

Thu Nov 10 09:26:06 EST 2011

Hi Avri,

With reference to bottom-up decision and support, I would say that first bottom up decision made by the DNS Stability Panel, and forwarded it to ICANN, and Second bottom-up support is ccNSO about FT Review, see the following document, where this point has been detained with the arguments of ccNSO. 

The public voices were unable to hear after ccNSO comments.

Thanks

Imran Ahmed Shah

-----------------------------------------------------------

2. Summary of Comments 

ICANN received input on the IDN ccTLD Fast Track Review from individual Internet users, the 

DNS technical community, APRALO, the Hong Kong Internet Registration Corporation 

(HKIRC) and the Country Code Names Supporting Organization (ccNSO). An analysis of these 

comments along with ICANN recommendations is provided below.  

Main Themes 

1. A large number of comments were received from individuals and entities in the Bulgarian 

Internet community, asking that ICANN re-evaluate the Bulgarian IDN ccTLD request for 

.bg in Cyrillic. Many questioned the transparency of the decision that found the applied for 

Bulgarian string was too similar to .br. Several commenters proposed that the requested 

string is not confusable with “.br.” The commenters further proposed that because the 

proposed string is not confusable with .br, the applied-for string should be accepted by 

ICANN within the Fast Track Process. Alternatively, the Country Code Names Supporting 

Organization (ccNSO) stated that disputes and objection/re-evaluation are policy issues that 

should not be addressed through an amendment to the Fast Track Process. 

2. The ccNSO, APRALO, HKIRC and Jothan Frakes commended the successful launch of the 

Fast Track process. The ccNSO and HKIRC noted that the transparency in the process was 

appropriate and maintaining confidentiality during string evaluation allows requesting 

countries and territories to resolve issues of public authority and community-support without 

undue politicization of the process. 

3. Several members of the DNS technical community noted issues with the treatment of IDN 

tables. One comment suggested that it was time for ICANN to stop publishing the IANA

Repository. Several noted that this inserts ICANN into registry naming policy. The ccNSO 

stated that this was a policy issue not appropriately addressed in ICANN implementation 

processes. One comment stated that ICANN should not engage in or actively foster the 

management of IDN tables. 

4. Several commenters noted that the Fast Track was intended to be for clear cases and noncontroversial requests. 
If the Fast Track process is to continue, issues with confusable strings 

as mentioned in the comments, will continue to arise. 

5. Several commenters raised the issue of variants.  

The comment forum can be viewed at http://forum.icann.org/lists/fast-track-review-2010/.

> -----Original Message-----

> From: governance at lists.cpsr.org [mailto:governance at lists.cpsr.org] On

> Behalf Of Avri Doria

> Sent: Thursday, November 10, 2011 06:28 PM

> To: IGC

> Subject: Re: [governance] Is really Bulgarian Cyrillic .?? (.bg) similar to other

> Latin ccTLDs?

> 

> Hi,

> 

> I was in Bulgaria for the domain.forun at which Rod spoke.

> 

> Of course I do not know what Rod and Parvanov spoke about.  But in other

> statements Rod, and Veni both made, they hid behind the bottom-up

> process and stated that it was rejected because of the bottom-up process

> and said that if the Bulgarians and Greeks wanted to change the rules they

> needed to go back to the ccNSO.  It is amazing how many time they invoked

> bottom-up process to defend unpopular Staff decisions - it was the mantra

> of the day.

> 

> Of course they never spoke of what bottom-up decisions they were talking

> about.  Was there a bottom-up decision about what sort of things were

> confusing similar?  Was there a bottom-up decision about a lack of

> transparency and the absence of an appeal of an arbitrary decision or an

> extended review procedure?  No, these are ICANN implementation details.  I

> was an observer of the ccNSO group that made recommendations, and these

> issues never came up.  And for the GNSO, no matter how much the bottom-

> up process has requested an extended review for confusing similarity, it has

> been rejected by the ICANN Staff.  ICANN Staff has decided on its own that it

> is supreme when it comes to harmful confusing similarity.  I remember no

> bottom-up decisions giving ICANN staff supremacy in any topic, let alone this

> one.

> 

> Another disturbing thing came up during these meetings.  There was a new

> notion introduced by those who spoke for ICANN.  I must note that I may

> have misunderstood it because some of it came from ICANN Staffers

> speaking in Bulgarian so I only heard a translation, but it sounded like the

> following:

> 

> In any review of Cyrillic or Greek characters, not only do they have to  worry

> about existing LDH (letter digit hyphen) ASCII TLDs, but also myst complete

> with potential LDH ASCII that might be applied for some day.  This notion was

> extend not only to un-allocated ISO 2 character designations but to any

> Cyrillic or Greek TLD that may look similar to LDH characters.

> 

> I.e. the notion I got out was that if the Cyrillic or Greek looks anything like

> ASCII, they can't have it.  ASCII trumps all. While this is bad, considering the

> stretch ICANN Staff makes when making these decision (б looks like b -

> really???), it is really awful. From the discussions I understood this would

> apply in gTLDS as much as it does in ccTLDs.

> 

> If I understood correctly, this is a bad thing, and this issue of .бг is just the tip

> of the iceberg of a really serious defect in the ICANN process for new TLDs.

> 

> avri

> 

> 

> 

> 

> On 9 Nov 2011, at 10:06, Kleinwächter, Wolfgang wrote:

> 

> > As I can see from the ICANN website, ICANNs Rod Beckstrom had a

> meeting with the Bulgarian president Mr. Parvanow, the day before

> yesterday (November 7). Did the Bulgarian president raise the issue of .bg

> and what was Beckstroem response?

> >

> > Thanks

> >

> > wolfgang

> >

> __________________________________________________________

> __

> > You received this message as a subscriber on the list:

> >      <mailto:governance at lists.cpsr.org> governance at lists.cpsr.org

> > To be removed from the list, visit:

> >      <http://www.igcaucus.org/unsubscribing> http://www.igcaucus.org/unsubscribing

> >

> > For all other list information and functions, see:

> >      <http://lists.cpsr.org/lists/info/governance> http://lists.cpsr.org/lists/info/governance

> > To edit your profile and to find the IGC's charter, see:

> >      <http://www.igcaucus.org/> http://www.igcaucus.org/

> >

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

> >

> 

> __________________________________________________________

> __

> You received this message as a subscriber on the list:

>       <mailto:governance at lists.cpsr.org> governance at lists.cpsr.org

> To be removed from the list, visit:

>       <http://www.igcaucus.org/unsubscribing> http://www.igcaucus.org/unsubscribing

> 

> For all other list information and functions, see:

>       <http://lists.cpsr.org/lists/info/governance> http://lists.cpsr.org/lists/info/governance

> To edit your profile and to find the IGC's charter, see:

>       <http://www.igcaucus.org/> http://www.igcaucus.org/

> 

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.igcaucus.org/pipermail/governance/attachments/20111110/331a25b3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 70673 bytes
Desc: not available
URL: <http://lists.igcaucus.org/pipermail/governance/attachments/20111110/331a25b3/attachment.png>
-------------- 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