Sam Hartman <[email protected]> writes: >>>>>> "Simon" == Simon Josefsson <[email protected]> writes: > > Simon> Florian Zeitz <[email protected]> writes: > >> While online games might not always want case folded strings, I > >> doubt having two usernames that differ only in case is ever > >> desirable. > > Simon> I have accounts in systems were that is used -- for example, > Simon> in one I have a lower-case username 'jas' for the ordinary > Simon> user and an uppercase variant 'JAS' as a personalized admin > Simon> account. > > Simon> In general, I believe that any I18N solution that disallow > Simon> reasonable semantics of how username and passwords are > Simon> interpreted will be completely ignored. What can (and > Simon> should) be discussed is what "reasonable semantics" means. > Simon> But forcing uppercase and lowercase characters to be regarded > Simon> as the same is to me so completely and obviously unreasonable > Simon> that I believe there is a disconnect between requirements and > Simon> solution. > > For myself, I've viewed a lot of systems, some of which case fold > usernames and some of which do not. > > I think there's a lot of evidence that systems like AD that case-fold > usernames are easier to use. > In my mind sufficient evidence to try and move the internet in that > direction.
I disagree that an I18N document is the appropriate way to move the Internet to case-insensitive usernames. If case-sensitive usernames is a significant problem, then it should be possible to publish a BCP recommending against that. Then existing protocols with case-sensitive usernames like HTTP, FTP, SMTP, SSH, etc could be revised. I don't believe any of that will happen, so we'll have to live with case sensitive usernames, and my take is that I18N documents should permit that. /Simon _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
