[Stox] Review on -presence

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

Return-Path: <saul@ag-projects.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id F172E21E80B7 for <stox@ietfa.amsl.com>; Tue, 30 Jul 2013 08:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YFld1gGLpBmV for <stox@ietfa.amsl.com>; Tue, 30 Jul 2013 08:33:20 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info []) by ietfa.amsl.com (Postfix) with ESMTP id 19DF721F9974 for <stox@ietf.org>; Tue, 30 Jul 2013 08:33:20 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 7A418B35DD; Tue, 30 Jul 2013 17:33:19 +0200 (CEST)
Received: from dhcp-152d.meeting.ietf.org (dhcp-152d.meeting.ietf.org []) by mail.sipthor.net (Postfix) with ESMTPSA id CC3A6B017C for <stox@ietf.org>; Tue, 30 Jul 2013 17:33:18 +0200 (CEST)
From: =?windows-1252?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-Id: <0CB65FBA-7262-4189-8852-5FC08A34D50D@ag-projects.com>
Date: Tue, 30 Jul 2013 17:33:18 +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 on -presence
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 15:33:26 -0000


Here is my review of the -presence document:

- Sec 3.3.2 suggests that if the subscription is maintained but we have no presence state, a PIDF would be generated with a basic status of closed, but what would be the tuple ID, if we don't know any resource for this user anymore? We could also send an empty NOTIFY, which would achieve the same goal.

- Sec 3.3.2 specifies how to handle the case when a gateway translated a SIP subscription into an XMPP subscription and then the SIP side decided to end it, but doesn't mention what to do in case the XMPP side decides to end it. It should send a NOTIFY with Subscription-State: terminated;reason=rejected.

- Sec 4.1, "Instant Message URI of the form <pres:user@domain>" - shouldn't this be "Presence URI of the form…" ?

- Using ID-123kdklejd doesn't seem to work as a valid xs:ID, TID-1234 does work though, so we could use TID- as the prefix for tuple identifiers in examples and such.

- Table 6 suggests that the Call-ID header should be matched to the presence stanza id, but the called won't change throughout the whole dialog, so we should use something else, which changes for each SIP transaction, what about the Via branch? Table 7 uses CSeq, FWIW.

- Table 6 suggests that priority is translated as the PIDF priority for a tuple, but that's an attribute of the contact element, which we don't mention, but I guess we should. Also, the priority in PIDF is a float between 0 and 1, is it the same for XMPP?

- Sec 4.3, the translated XMPP stanza contains the full JID of Juliet, but where did we get the resource from? Shouldn't it go to the bare JID?

* Editorial nits:

- Many example requests lack a To header
- Sec 3.2.3: "gateway SHOULD a presence stanza" -> "gateway SHOULD send a presence stanza"


Saúl Ibarra Corretgé
AG Projects