[Stox] Review of -chat

[Saúl Ibarra Corretgé <[e-mail]>]

Hi,

Here is my review of the -chat document.


- What should a gateway do when it gets a message with XHTML-IM body? I guess send it with content-type text/html, but is there any translation required?

- Section 4 mentions what should happen if no formal sessions are used, but doesn't say anything of the opposite. Should we say that those are out of the scope of this specification?

- I think we should define a mapping between XMPP chatstates (XEP-0085) and the iscomosing indication (RFC 3994) particularly, the "gone" state in XMPP should trigger a BYE on the SIP side, and vice versa.

- Should we add text to map MSRP reports to XMPP receipts (XEP-0184)? They do map very well semantically. Now, XEP-0184 says that the ack may not be sent if "The recipient simply does not wish to return a receipt for the content message.", which pretty much renders it useless. Anyway, I think we do need some text explaining how MSRP success and failure ports should be dealt with.

- In general: we don't have any example using CPIM, not sure if we should say anything about it.


* Editorial nits

- Examples (multiple): the gr parameter is a URI parameter, not a header parameter, so: "To: <sip:[e-mail]>;gr=balcony" should be "To: <sip:[e-mail];gr=balcony>". This applies to both To and Contact headers.

- Sec 1: "using the SIP INVITE and SEND request" -> "using the SIP INVITE and MSRP SEND request"


Cheers,

--
Saúl Ibarra Corretgé
AG Projects