On Tue, Sep 02, 2014 at 05:42:28PM -0700, Dan Chiba wrote: > usernames "fussball" and "fußball" should be treated as equal for case > insensitive matching, or as distinct for case sensitive matching.
I don't see any case in those two strings. What am I missing? But anyway, it's not clear to me that the usernames "fussball" and "fußball" should in fact always and everywhere be treated as equal. For my understanding is that the use of ß is very much a localization issue: the ligature is never used in Swiss written German. One could argue that it'd be extremely unwise to permit distinct user registrations that are otherwise identical except for ss and ß (certainly I would). But if we think that's a good reason to insist on a mapping, then that would also seem to be a good reason to say, "No case folding, period." Indeed, that's one of the big differences between IDNA2003 and IDNA2008; IDNA2008 violates a deep tradition in the DNS in this way, basically because we couldn't make the mapping work the way we'd like. > username string matching. If the profile doesn't fully specify the spec but > it's up to the deployment/service policies, I would like the components to > be able to identify the policies precisely. While I agree with that in principle, it sounds like an interoperability and implementation nightmare (which issue is, I think, what got us the current compromise text). Best regards, A -- Andrew Sullivan [email protected] _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
