Re: Unicode/UTF-8 issues (was: commentsondraft-ietf-sasl-anon-00)

["Kurt D. Zeilenga" <[e-mail]>]

At 12:09 PM 2/20/2003, Alexey Melnikov wrote:

>"Kurt D. Zeilenga" wrote:
>
>> Okay, how about I replace the grammar and the paragraph before
>> it as follows:
>
>This mostly works, see below.
>
>>   A formal grammar for the client message using Augmented BNF [ABNF]
>>   is provide below as a tool for understanding this technical
>>   specification.
>>
>>   message     = [ email / token ]
>>                 ;; MUST be prepared in accordance with Section 2
>>
>>   UTF1        = %x00-3F / %x41-7F ;; less '@' (U+0040)
>>   UTF2        = %xC2-DF UTF0
>>   UTF3        = %xE0 %xA0-BF UTF0 / %xE1-EC 2(UTF0) /
>>                 %xED %x80-9F UTF0 / %xEE-EF 2(UTF0)
>>   UTF4        = %xF0 %x90-BF 2(UTF0) / %xF1-F3 3(UTF0) /
>>                 %xF4 %x80-8F 2(UTF0)
>>   UTF0        = %x80-BF
>>
>>   TCHAR       = UTF1 / UTF2 / UTF3 / UTF3 / UTF4
>>               ;; any UTF-8 encoded Unicode character
>>               ;; except '@' (U+0040)
>
>Hmm, this suggests a typo in draft-yergeau-rfc2279bis-04.txt (UTF3 is
>shown twice).

Or an error on my part.  UTF3 should only be listed once here.


>Also note, that this doesn't have UTF5 & UTF6 that you currently have:
>
>      UTF5        = %xF8-FB 4(UTF0)
>      UTF6        = %xFC-FD 5(UTF0)
>
>(but they have to be cleaned up to prevent overlong sequences).

Yes.  There are a couple of 4 v 6 octet cleanups to be made as well.