> Can you tell us more about what policy objective you are trying to achieve by preventing existing registry operators from applying for IDN strings related to their existing ASCII strings? 

first some of my reasoning:

1.  i believe they are engaged in an illegitimate extension of confusing similarity to be something beyond visual or auditory confusion to meaning confusion. (some would argue i go too far in allowing for auditory based confusing simialrity since that would mean that transliterations would be considered confusingly similar)

2. once they can extend this it means they can challenge anyone else on getting a name that has the same meaning as their name

3. but then they realized that if they did this, they could not have those names either.

4. so they want to demand an exception that says of course confusing similarity does not apply to them since they own the original.

5. and this gives them a monopoly of names that mean the same as theirs in all scripts and languages, but they are not willing to commit to synchronicity - meaning that all second level names would also need to be aliased in some way; i.e name.com does not have to point to the same location as name.idncom or idnname.idncom - resulting in confusion at the second level.  i.e they want to sell .idnname to a completely new market.

6.  they want to claim that this was the intent of the GNSO all along - when it was never discussed.

7. they want to declare consensus in a small drafting team without going through any sort of bottom-up process to find out if everyone is comfortable with it and if we have dealt with all the complexities.

So, some of my policy objectives are:

- give all applicants the same footing in regard to confusing simialrity
- prevent incumbent monopoly of all idns similar in meaning to .com and .org and other existing gTLDs based on a broad definiton of confusingly similar
- stop policy by revisionism and registry fiat
- prevent user confusion at the second level
- keep from sweeping the complexities in this policy action under the table.

cheers,

a.



On 14 Apr 2010, at 23:45, Milton L Mueller wrote:

> Avri
> I do not understand the rationale for your position. 
> If I were .com, or .org, or .anything, of course I would want to have a similar-meaning or looking domain in different languages. 
> 
> I am not sure how .com can be considered "confusingly similar" to two chinese characters that mean "company" in putonghua. But even if it is, by some warped definition, how can it be "confusing" when both are run by the same company?
> 
> If Pepsi registers a trademark that is visually, aurally, or linguistically similar to its own logos or trademarked names, then of course there is no legal problem with that. Confusing means that you think it's Pepsi but it's not. If it is similar to Pepsi's brand and it is in fact Pepsi behind it, it's not confusing. 
> 
> With IDNs in particular, there is a pro-consumer case to be made for allowing the operator of .foo to have various IDN TLDs resembling .foo so that customers who already have a ascii .foo name can have something similar in IDN. 
> 
> Can you tell us more about what policy objective you are trying to achieve by preventing existing registry operators from applying for IDN strings related to their existing ASCII strings? 
> 
> --MM
> ________________________________________
> From: Non-Commercial User Constituency [[log in to unmask]] On Behalf Of Avri Doria [[log in to unmask]]
> Sent: Wednesday, April 14, 2010 6:47 PM
> To: [log in to unmask]
> Subject: [NCUC-DISCUSS] are confusing similar gTLDs not confusing if the same registry has them all?
> 
> Hi,
> 
> The following is  a line from and IDNG Drafting Team where Chuck is proposing the following.
> 
> Begin forwarded message:
> 
>> 
>> I don't think that delay of the overall process is an option.  At the same time, I believe that a simple clarifying statement from the GNSO Council could be crafted on this issue.  It could be something along the lines of the following: "Recommendation 2 of the GNSO new gTLD recommendations (restriction of confusingly similar new gTLDs) was not intended to prevent an applicant from applying for multiple IDN versions of the same gTLD, whether that gTLD is an existing gTLD or a new gTLD."  I strongly believe that that is an accurate statement regardless of how one defines confusingly similar.
> 
> 
> I have sent a note indicating that I do not believe this is an accurate statement.
> 
> I believe we should add a discussion of this to our meeting as it may be brought up in the Council meeting.
> 
> I do not know where NCSG stands on the issue of a single applicant applying for the same stream in a multitude of scripts and being excused from the confusing similarly rules because it is all one registry applying for the names - e.g. .com in a multitude of scripts.  Especially since they believe that they should be no binding to rules of synchronicity (e.g. if you have the name in one, you have the same name in the other and it is an alias).
> 
> i am personally against making any changes to the DAG without extensive discussions and under what if any constraints one would put on applicants in such a situation.
> 
> The thread can be found starting at: http://forum.icann.org/lists/gnso-idng/msg00397.html
> 
> looking forward to hearing people's view on the topic.
> 
> a.
>