I'm not clear how thess relates to our issue. The RFCs deal with how the software should deal with converting upper to lower case. But our issue is how human beings will see things. That is, what they will expect that what they see will produce.
It's real clear from our last two meetings that, for Turkish users, I vs Dotless I will be an issue. For them, even though their language has pairs of words which differ only by which letter is used, allowing two domain names like that is a problem. I believe the word used was "unacceptable."
We can discuss whether to make such variants allocatable rather than blocked. (Which I incline against.) But I don't see that we can refuse to make them variants.
Bill Jouris
On Wed, Jul 8, 2020 at 12:39 PM, Tan Tanaka, Dennis via Latingp
<latingp@icann.org> wrote:
_______________________________________________
Latingp mailing list
Latingp@icann.orghttps://mm.icann.org/mailman/listinfo/latingp_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (
https://www.icann.org/privacy/policy) and the website Terms of Service (
https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.