Previous: Use of SASLprep in CRAM-MD5, Up: Protocol Clarifications
The non-standard mechanism LOGIN presumably does not support non-ASCII. We suggest that the client should send unprepared UTF-8 and that the server apply SASLprep with the AllowUnassigned bit cleared on the received username and password.