Kurt Zeilenga wrote: > > On Oct 30, 2008, at 11:14 AM, Peter Saint-Andre wrote: > >> Warning: this message might open a big can of worms. :) >> >> >> Note: This email is UTF-8 and uses UTF-8 characters. If you can't read >> them, get a better email client. > > Stringprep ties us to Unicode 3.2. > > I think it important to move to preparation algorithm which don't tie > implementations to a particular version of Unicode while maintaining > compatibility with existing algorithms when Unicode 3.2 is used.
Agreed. > One approach is to redefine the algorithm in terms of Unicode properties > (to the degree possible). This is the approach being used in IDNAbis, > and what I'm hoping to do for SASLprep and LDAPprep algorithms. Yes, I have been tracking the IDNAbis work and I think that's the right way to go, but I don't know if that's the right way to go for our work on rfc3920bis. Do you think that the IDNAbis work is far enough along for us to reuse it in rfc3920bis and use a similar approach for nodeprep and resourceprep? > I'd be willing to assist in doing the same for various XMPP prep > algorithms. Thanks! Peter
