[Stox] Review of -chat

Saúl Ibarra Corretgé <saul@ag-projects.com> Tue, 30 July 2013 14:02 UTC

Return-Path: <saul@ag-projects.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7579F11E81E4 for <stox@ietfa.amsl.com>; Tue, 30 Jul 2013 07:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level:
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VDCVUXiPrcqk for <stox@ietfa.amsl.com>; Tue, 30 Jul 2013 07:01:54 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5CC21F88FB for <stox@ietf.org>; Tue, 30 Jul 2013 07:01:47 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 1D10DB35DF; Tue, 30 Jul 2013 16:01:44 +0200 (CEST)
Received: from dhcp-152d.meeting.ietf.org (dhcp-152d.meeting.ietf.org [130.129.21.45]) by mail.sipthor.net (Postfix) with ESMTPSA id 6C981B017A for <stox@ietf.org>; Tue, 30 Jul 2013 16:01:44 +0200 (CEST)
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F5BB54B-0650-42BA-A599-C5DBBB6326D4@ag-projects.com>
Date: Tue, 30 Jul 2013 16:01:43 +0200
To: "stox@ietf.org" <stox@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Subject: [Stox] Review of -chat
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 14:02:00 -0000

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:juliet@example.com>;gr=balcony" should be "To: <sip:juliet@example.com;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