Andrew Sullivan asked: > I'd be especially interested in whether people think that table is worth > anything, before I complete it. I'm of two minds.
I'd say yes. To its credit, it made me go look at one of the reviews (Alexey's review of RFC4314 at http://www.ietf.org/mail-archive/web/precis/current/msg00086.html) for more info. I'm not that familiar with IMAP or SASLprep so I am confused about one thing and hope someone can explain it in simple terms for me :) The review says: > Most likely case sensitive. Exact requirements on > case-sensitivity/case-preservation > depend on a specific implementation, e.g. an implementation might treat all > user > identifiers as case insensitive (or case insensitive for US-ASCII subset > only). But RFC 4013 says: > This profile is not intended for use in > preparing identity strings that are not simple user names (e.g., > email addresses, domain names, distinguished names), or where > identity or password strings that are not character data, or require > different handling (e.g., case folding). The table Andrew added has "a,d" (but not "i"). That would be correct if all implementations agreed on the case sensitivity rules. And RFC 4013 says it's not appropriate for things that aren't case sensitive. So I'm confused about the part of the review saying: "Exact requirements on case-sensitivity/case-preservation depend on a specific implementation, e.g. an implementation might treat all user identifiers as case insensitive (or case insensitive for US-ASCII subset only)." Can someone elaborate on this? Thanks, -Dave _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
