IETF Logo Mail Archive

Re: [Stox] Review on -im

Saúl Ibarra Corretgé <saul@ag-projects.com> Wed, 31 July 2013 15:23 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 9FF9021F9E27 for <stox@ietfa.amsl.com>; Wed, 31 Jul 2013 08:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.827
X-Spam-Level:
X-Spam-Status: No, score=-0.827 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3, SARE_MLH_Stock1=0.87]
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 iqIeBPkEes08 for <stox@ietfa.amsl.com>; Wed, 31 Jul 2013 08:23:20 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 282E621F9E3A for <stox@ietf.org>; Wed, 31 Jul 2013 08:23:19 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id CD4D1B35DF; Wed, 31 Jul 2013 17:23:17 +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 30D59B017A; Wed, 31 Jul 2013 17:23:17 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <51F92992.4070802@stpeter.im>
Date: Wed, 31 Jul 2013 17:23:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <00DCCF5E-1D4B-4BFE-8986-A1B3B5682FF0@ag-projects.com>
References: <7AE79F98-B222-4BBC-BC02-1606AF8F34A9@ag-projects.com> <51F9238D.106@stpeter.im> <4DFDCC4B-9568-4BA9-A3F5-C466E8549DCE@ag-projects.com> <51F92992.4070802@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1508)
Cc: "stox@ietf.org" <stox@ietf.org>
Subject: Re: [Stox] Review on -im
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: Wed, 31 Jul 2013 15:23:26 -0000

>> 
> 
> Well, the sender might really really want to know if the message was
> delivered to the recipient. :-)
> 

Unfortunately there is no way to do that with a SIP MESSAGE. Unless we invent a special payload for acknowledging reception of a given SIP MESSAGE, but I think that is really out of the scope of what we are doing in the IM document.

> My feeling about message receipts is that we leave them out for now and
> maybe define a mapping for them in another specification, but I am open
> to persuasion on the topic.
> 

As I said above we have no way to use them in the -im document, but there is a clear equivalence between the receipt and the MSRP REPORT chunk which we use in -chat. If the SIP endpoint requests success and failure reports, we'd need to fool it by always sending a report, regardless of the acknowledgement of the message (in case receipts are supported). I can live with that if we add some text clarifying she a REPORT should be sent.

--
Saúl Ibarra Corretgé
AG Projects

v2.23.0 | Report a Bug | By Email