Comment on the String Similarity Amendment
Hello, My name is Vassil Petev, a Bulgarian citizen, and a Unit Manager in an established Bulgarian IT company. I am submitting this comment on behalf of Bulgaria, the Cyrillic speaking community around the world, and the company I work for. I would like to communicate my support for the GNSO Council request that the Applicant Guidebook section on "Outcomes of the String Similarity Review" be amended to allow applicants to request an Extended Review under applicable terms similar to those provided for other issues such as "DNS Stability: String Review Procedure". I hereby present to you my view and understanding of the application process for cases where strings are "confusingly similar" to other TLDs and/or ccTLDs, and request that these views are included in your recommendations to Kurt Pritz, the members of the ICANN New GTLD Implementation Team, and the ICANN Board. My views and perceptions are backed up with two real-life examples, the first one concerning my country, Bulgaria, and the second one covering a case with the company I work for. The attached document provides insight and analyzes in detail on: 1. The case of the Cyrillic ccTLD for Bulgaria (*.бг) and the Latin IDN for Brazil (*.br): o Putting *.бг in context, or what is ICANN staff missing in their current evaluation criteria for confusingly similar strings? o Brazil's IDN vs. Bulgaria's IDN o Analysis from a user point of view 2. The case of the Cyrillic gTLD *.ком (for компания) and the Latin gTLD *.com (for company) o Putting *.ком in context, or what is ICANN staff missing in their current evaluation criteria for confusingly similar strings? o Fraud and companies operating in Cyrillic speaking countries 3. Why this matters to me: The history of the Cyrillic alphabet Thank you for your attention to this matter. Regards, Vassil Petev Unit Manger [cid:image001.jpg@01CB1A10.C51E5750] Attachment:
Petev comment on string similarity test 2010-07-01.pdf |