Re: [apps-discuss] APPSDIR review of draft-ietf-simple-chat-13

[Alexey Melnikov <[e-mail]>]

Hi Miguel,

On 07/02/2012 14:12, Miguel A. Garcia wrote:
> Hi Enrico:
>
> Thanks for your review.
>
> See inline comments.
>
> On 06/02/2012 10:50, Enrico Marocco wrote:
>> Document: draft-ietf-simple-chat-13
>> Title: Multi-party Chat Using the Message Session Relay Protocol (MSRP)
>> Reviewers: Alexey Melnicov and Enrico Marocco
>> Review Date: 2012-02-06
>> IETF Last Call Date: 2012-02-06
>>
>>
>> Summary: This draft is almost ready for publication as a Proposed
>> Standard, but has a major issue to be taken into consideration and a few
>> minor issues to be fixed.
>>
>>
>> Major Issue
>>
>> The document doesn't describe allowed characters in Nicks and any
>> normalization that needs to be applied.
>
> I think the document clearly describes the allowed characters in 
> nicknames by making a reference to RFC 4975. In Section 7.1, the 
> syntax of the Use-Nickname header is written as:
>
>                Use-Nickname = "Use-Nickname:" SP nickname
>                nickname = quoted-string
>                ; quoted-string defined in RFC 4975
>
> According to RFC 4975:
>
>    quoted-string = DQUOTE *(qdtext / qd-esc) DQUOTE
>    qdtext = SP / HTAB / %x21 / %x23-5B / %x5D-7E
>                / UTF8-NONASCII
>    qd-esc = (BACKSLASH BACKSLASH) / (BACKSLASH DQUOTE)
>    BACKSLASH = "\"
>    UPALPHA  = %x41-5A
>    ALPHANUM = ALPHA / DIGIT
>
>
> So, I think it is described.
If ABNF is saying that only UTF-8 is allowed, then the current text is Ok.
>
> With respect to normalization, I am not sure if a nickname needs to be 
> normalized and now this normalization should take place. Let me know 
> the text that you are missing and I will add it to the draft.

Have a look at ResourcePrep:
http://datatracker.ietf.org/doc/draft-ietf-xmpp-6122bis/

If you can't wait for Precis to finish, you can also use an older 
version (based on StringPrep):
http://www.rfc-editor.org/rfc/rfc6122.txt