Subject: authentication and authorization identities, and passwords in SASL Mechanisms

From: "Raif S. Naffah" <[email-masked]>
Date: Tue, 1 Apr 2003 21:27:26 +1100

hello there,

can someone calrify the following:

1. why does a SASL Mechanism has to mandate SASLPrep as a needed 
transformation for authentication identities (usernames) and passwords, 
in preference to something like:

   MUST be in Unicode Normalization Form KC [UNICODE-KC]
   without NUL characters.

wouldn't a transformation such as the SASLPrep be part of the SASL 
Profile itself rather than the Mechanism(s)?

2. what is the consensus on specifying/handling authorization identities 
for transportation on the wire?  is [UNICODE-KC] enough?

TIA + cheers;
rsn