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

Imran Ahmed Shah ias_pk at yahoo.com
Mon Nov 7 15:08:46 EST 2011 


> -----Original Message-----
> From: Imran Ahmed Shah [mailto:ias_pk at yahoo.com]
> Sent: Tuesday, November 08, 2011 12:35 AM
> To: 'governance at lists.cpsr.org'; 'Adam Peake'; 'Lee W McKnight'
> Cc: 'Daniel Kalchev'
> Subject: RE: [governance] Is really Bulgarian Cyrillic .бг (.bg) similar
to other
> Latin ccTLDs?
> 
> > -----Original Message-----
> > From: governance at lists.cpsr.org [mailto:governance at lists.cpsr.org] On
> > Behalf Of Adam Peake
> > Sent: Monday, November 07, 2011 06:43 PM
> > To: governance at lists.cpsr.org; Lee W McKnight
> > Cc: Daniel Kalchev
> > Subject: Re: [governance] Is really Bulgarian Cyrillic .бг (.bg)
> > similar to other Latin ccTLDs?
> >
> > How about we suggest no ascii should be used under an idn ccTLD. If
> > there's cyrillic at the second, third etc level then no one's going to
> > confuse that with Brazil.
> 
> [IAS:] If you would like to propose only Cyrillic characters will be
allowed for
> IDN.IDN (Cyrillic.бг) for Bulgaria, where ASCI.бг will not allowed, just
to
> create a significant differentiation this is a Cyrillic IDN domain.
> 1. Please not that this is again different from the Fast Track  Program
> implementation process where 1-IDN+ASCI.IDN is allowed.
> 2. How the users will be educated to be able to understand that what's
mean
> what.
> 3. Today, Cyrillic-IDN.com & Cyrillic-IDN.net is already allowed, the
above
> education will not work in all cases.
> 4. Cyrillic-IDN.bg might be allowed now or in future, so again the formula
will
> not work to establish a common understanding.
> 
> > Still think taking this to the Ombudsman would be worthwhile. He might
> > not be able to make recommendations to help BG, but could provide
> > advice for[IAS:] the new gTLD round.
> [IAS:] Ombudsman would be useful for the followings:
> 1.	To provide an example to be followed as precedent when the rules
> and bylaws do not able to resolve the conflict.
> 2.	To prevent further decisions on weak backgrounds or against the
> demand of user's requirements.
> However, I think appeal with Ombudsman would only be workable,
> a.	if the case is submitted by including Bulgarian government
> representative (applicant)
[IAS:] Till now, we have no representative from the Applicant (.бг) is
appeared in the discussion, however I hope, Mr Daniel can bring them on IGC
mailing list and can engage them to take next step with sharing thoughts and
planning.

> b.	and we should know all about the consumer,
[IAS:] Required

> c.	consumer rights,
[IAS:] Required

> d.	decision against the consumer rights,
[IAS:]  .. and what is missing in the policy, what is the main cause and
reason of this conflict.
[IAS:] i.e. already under discussion, the refusal by ICANN on basis of DNS
Stability Panel declaration that . бг is "confusingly similar" (with some
other letters).

> e.	other similar examples and decisions made by the authority,
[IAS:] as mentioned by Daniel that Greek example is same, they were allowed
be Bulgaria is not.

> f.	required solution / (to be proposed for helping Ombudsman for
> quick decision making)
[IAS:] Required

> and
> g.	if the IGC support this action, we should draft and propose a policy
in
> global prospect not only for the бг, however .бг example can be used.
[IAS:] as we also discussed and agreed about writing letter to ICANN's Board
and ALAC

> 
> Thanks
> 
> Imran Ahmad Shah
> 
> > Adam
> >
> >
> >
> > 2011/11/6 Lee W McKnight <lmcknigh at syr.edu>:
> > > I agree with the direction Avri and Imran have taken the suggested
> > language for the letter.
> > >
> > > And disagree with all due respect, with Paul that there is any point
> > > at trying
> > to get a he said-she said apology process going.
> > >
> > > Let's just encourage ICANN to move on towards an open and
> > > transparent
> > process in next phase.
> > >
> > > Which coincidentally sets stage for a belated .бг (.bg) remedy; with
> > > noone
> > making or asking for apologies.
> > >
> > > Lee
> > > ________________________________________
> > > From: governance at lists.cpsr.org [governance at lists.cpsr.org] on
> > > behalf of Daniel Kalchev [daniel at digsys.bg]
> > > Sent: Saturday, November 05, 2011 4:52 PM
> > > To: governance at lists.cpsr.org
> > > Subject: Re: [governance] Is really Bulgarian Cyrillic .бг (.bg)
> > > similar to other
> > Latin ccTLDs?
> > >
> > > Paul,
> > >
> > > This is indeed an interesting proposition, but until now nether the
> > > Bulgarian
> > Government, neither ICANN has accepted the possibility that they may
> > have make a mistake at some point. It would be interesting to observe
> > if such progress is possible.
> > >
> > > Daniel
> > >
> > > On Nov 5, 2011, at 7:53 PM, Paul Lehto wrote:
> > >
> > >>
> > >> 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.
> > >
> > >
> >
> __________________________________________________________
> > __
> > > 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

More information about the Governance mailing list