On Tue, Feb 19, 2013 at 8:30 PM, Peter Saint-Andre <[email protected]> wrote: > On 2/19/13 3:46 PM, Nico Williams wrote: >> On Mon, Feb 18, 2013 at 11:05 PM, Peter Saint-Andre >> <[email protected]> wrote: >>> IMHO this is similar to the previous discussion about naming >>> needing to include space characters (after all, your name is >>> "Chris Newman", not "ChrisNewman"). After much discussion, >>> participants in the PRECIS WG concluded that it would be safer >>> to disallow space characters in the NameClass, and that >>> application protocols would need to define their constructs as a >>> space-separated series of NameClass instances. And in fact >>> that's what we've done in draft-ietf-precis-saslprepbis: >> >> I think this is a mistake. There are plenty of online games where >> users are allowed to have fairly arbitrary names. E.g., bzflag >> (although in recent years I think additional restrictions have been >> added on the registration side). Online gaming is probably a >> desired customer for SASL -- why not? >> >> I think restrictions on user naming should be imposed primarily by >> the registrar, not by the client or server software. We might >> well advise against allowing whitespace in usernames, and we might >> need to map different whitespace codepoints to just one, and so on, >> but not prohibit. > > Hi Nico, please (re-)read Section 4.3 of draft-ietf-precis-framework > before concluding that the participants in the PRECIS WG are utterly > misguided on the issue of whitespace. :-)
I said what now? :) But OK, I read that, and I remain unconvinced. What am I missing? If they did have a clue then they didn't write text that I find convincing. Who cares if some devices produce whitespace other than ASCII space? That's what mappings are for. Or maybe I'm missing something. Assume I'm partly ignorant here. What am I missing? Nico -- _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
