Re: I-D Action: draft-ietf-simple-chat-17.txt

AFAICT, this draft has addressed all the concerns I previously raised.
In looking through it, I came across some small editorial issues:

Figure 1, near the bottom, has a dangling "|".

In section 4.1:

    Nicknames:   Whether the chat room accepts users to be recognized
       with a nickname.  See Section 7, Section 7.1, and Section 8 for
       details.  Also, the scope of uniqueness of the nickname: the chat
       room (conference instance), a real or domain, a server, etc.

Something is wrong in the last sentence - "a real" *what*?

Section 5.2: s/The chat room them uses/The chat room then uses/

Section 6.2: in the last paragraph, at the end, s/URI.m/URI./

	Thanks,
	Paul

On 11/17/12 11:30 AM, Miguel A. Garcia wrote:
> Hi:
>
> So, the long awaited version -17 of the MSRP chat draft has been posted.
> This version addresses all the comments received in the IESG review and
> various directorates that also took a look at the draft. Among others,
> these are the most relevant changes.
>
> - Added definitions of "identifier" and "to log in".
> - New Section 4.1 lists all the Policy Attributes of the chat room in a
> single section.
> - Clarified that congestion can occur due to the chat room application
> or due to some other application.
> - Clarified that the MSRP switch should learn the recipient's
> capabilities through the 'accept-wrapped-types' in SDP. Procedures as
> for what to do if the MSRP switch is aware that a recipient does not
> support a given media type.
> - Quite a few clarifications around chunked messages. It was clarified
> when the MSRP switch has to delete the temporarily stored state. Also,
> how to deal with situations where the connection is broken before the
> reception of the last chunk.
> - Added a length limit to MSRP nicknames: they must be between 1 and
> 1023 octets, after UTF-8 encoding.
> - Fixed a bug: the error result code is 425 rather than 423 in the
> examples.
> - Added more security considerations around the usage of TLS, policies
> to preserve a nickname once the use logs off, confusable nicknames,
> rendering of nicknames that contain scripts or code, and anonymity when
> using TLS with certificates.
>
>  From the authors' perspective, we believe the draft is ready. I will
> contact the IESG members to verify that the current version satisfies
> their comments.
>
> /Miguel
>
> On 17/11/2012 17:06, [email protected] wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>   This draft is a work item of the SIP for Instant Messaging and
>> Presence Leveraging Extensions Working Group of the IETF.
>>
>>     Title           : Multi-party Chat Using the Message Session Relay
>> Protocol (MSRP)
>>     Author(s)       : Aki Niemi
>>                            Miguel A. Garcia-Martin
>>                            Geir A. Sandbakken
>>     Filename        : draft-ietf-simple-chat-17.txt
>>     Pages           : 42
>>     Date            : 2012-11-17
>>
>> Abstract:
>>     The Message Session Relay Protocol (MSRP) defines a mechanism for
>>     sending instant messages within a peer-to-peer session, negotiated
>>     using the Session Initiation Protocol (SIP) and the Session
>>     Description Protocol (SDP).  This document defines the necessary
>>     tools for establishing multi-party chat sessions, or chat rooms,
>>     using MSRP.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-simple-chat
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-simple-chat-17
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-simple-chat-17
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> Simple mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/simple
>>
>>
>