On Dec 5, 2012, at 12:11 PM, Cullen Jennings (fluffy) <[email protected]> wrote:
> > SASLprep is based on a 10 year old version of unicode and does not provide a > reasonable forward compatible way to update the mapping tables for embedded > devices. I'd rather not tie ourselves to an absolute version of Unicode. I'd > rather not give people the false idea that unicode passwords were going to > reliably work across implement ions because that seems pretty unlikely. > Obviously there is ongoing work to fix this but the base protocol is a place > were for now we can just use characters that are not a problem. Ekr, Cullen and I discussed this one on a call today. Our current proposal is to say that passwords are binary objects in RELOAD base, but that applications using RELOAD either MAY or SHOULD define string prep profiles appropriate to the application. Can we live with some variation of that? -- Dean _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
