Can we have a potential middle ground proposal for the treatment of the now "Reserved Names"? 1. I was doing some thinking and although we have been using .redcross and .rodcross, the reality is that in 2012 those would not have been considered "confusingly similar" under the string similarity review. Why do I say this, because the "e" and the "o" are aurally distinct, and do not have the visual similarity that the evaluation was concerned with. They are not near each other on a keyboard, have different vowel sounds and different meanings. As a result we should not be using that example because it skews the entire discussion. 2. What we are really concerned about are visual homoglyphs in the same script. And the big issue is with the latin script. We are not concerned with .redcross with a cyrillic "d" because that would mix the scripts would not be allowed. We are concerned with things like: a).rédcross (Latin small e with acute) b) .reḋcross (Latin small e with dot above or d with dot) c) .redcròss (o with grave) d).redcrośs (s with acute) or: a) .o1ympic (digit 1 for “l”) b) .0lympic (digit 0 for “o”) c) . olymplc (the letter “l” for the letter “i”) 3. Proposal: Treatment of Reserved Names and Similar Strings * * * Homoglyphs: Applications for Reserved Names, and for any homoglyphs of those names, may be submitted only by the entities expressly eligible for those Reserved Names. Applications from any other party are ineligible. * Confusingly Similar Strings (Non-Homoglyphs): * If a qualified entity applies for a Reserved Name, and another applicant applies for a string that is confusingly similar to that Reserved Name (but not a homoglyph), those applications shall not be placed in the same contention set. Both may be delegated. * If no qualified entity applies for the Reserved Name in the current round, and another party applies for a confusingly similar (non-homoglyph) string, that application may proceed. The delegation of such a string shall not prevent the qualified entity from applying for and obtaining the Reserved Name in a future round. * String Confusion Objections and Blocking: * No String Confusion Objection may be filed or sustained by either the qualified applicant for the Reserved Name or the applicant for the confusingly similar string, in this or any future round. * Accordingly, those applications shall never be placed in the same contention set as a result of a string confusion proceeding. * The approval, delegation, or continued operation of one string shall never block or prevent the approval, delegation, or continued operation of the other string on the basis of string confusion or string similarity. 4. I understand this could be considered New Policy, but it could align with the 2014 PDP's vision of "protecting" the exact matches, while at the same time ensuring that we do not allow these homoglyphs get through because of the no string similarity reviews not being performed. This seems to check the boxes of what we (and ICANN staff in my opinion) are really concerned with (I think) and finds a way that they can co-exist. Thoughts? [8ed357ae-3462-4ba2-8758-18c70a79d71c]