Re: [EAI] I-D Action: draft-ietf-eai-5738bis-01.txt

[Chris Newman <[e-mail]>]

--On August 1, 2011 10:56:08 -0400 Joseph Yee <[e-mail]> wrote:
> I would assume "UTF8=USER" meant to notify client about SASL on username
> & password rather than support of UTF8 on username & password.
>
> If it's about SASL, I think we are safe to remove the tag, with client
> needs to check the SASL tag.  If it's about supporting UTF8 in username &
> password, then I think it's ok to remove "UTF8=USER", but only stating
> "UTF8=ACCEPT" MUST imply the support of UTF8 to username & password.

The IMAP AUTHENTICATE command already supports UTF-8 if the SASL mechanism 
selected does. The PLAIN mechanism supports UTF-8.

So UTF8=USER was only about the IMAP LOGIN command. So I'd replace section 
5 with something like:

5.  LOGIN Command

   If the "UTF8=ACCEPT" capability is advertised, that indicates the
   server understands UTF-8 user names and passwords in the LOGIN
   command. This is not a guarantee that they underlying identity
   system will allow the creation of accounts with UTF-8 user names
   and/or passwords. However, if the identity system does allow such
   accounts, then the server MUST apply SASLprep [RFC4013] to both
   arguments of the LOGIN command. The server MUST reject UTF-8 that
   fails to comply with the formal syntax in RFC 3629 [RFC3629] or
   if it encounters Unicode characters disallowed by SASLprep.

		- Chris