RE: [Simple] Advanced IM Reqs: Delivery status reporting

hisham.khartabil@nokia.com Wed, 25 February 2004 06:57 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01606 for <simple-archive@ietf.org>; Wed, 25 Feb 2004 01:57:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvszO-0005gT-00 for simple-archive@ietf.org; Wed, 25 Feb 2004 01:57:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvsyS-0005YW-00 for simple-archive@ietf.org; Wed, 25 Feb 2004 01:56:53 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Avsxg-0005RW-00; Wed, 25 Feb 2004 01:56:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avsxe-0002GQ-Up; Wed, 25 Feb 2004 01:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvsxV-0002Fl-FK for simple@optimus.ietf.org; Wed, 25 Feb 2004 01:55:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01489 for <simple@ietf.org>; Wed, 25 Feb 2004 01:55:51 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvsxS-0005Q2-00 for simple@ietf.org; Wed, 25 Feb 2004 01:55:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Avswc-0005Gy-00 for simple@ietf.org; Wed, 25 Feb 2004 01:54:59 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1Avsvk-00056S-00 for simple@ietf.org; Wed, 25 Feb 2004 01:54:04 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1P6rqK11711; Wed, 25 Feb 2004 08:53:52 +0200 (EET)
X-Scanned: Wed, 25 Feb 2004 08:53:25 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i1P6rPVj021373; Wed, 25 Feb 2004 08:53:25 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 007ds0Q2; Wed, 25 Feb 2004 08:53:25 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1P6rO727493; Wed, 25 Feb 2004 08:53:24 +0200 (EET)
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 25 Feb 2004 08:53:20 +0200
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Simple] Advanced IM Reqs: Delivery status reporting
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7017977CA@esebe019.ntc.nokia.com>
Thread-Topic: [Simple] Advanced IM Reqs: Delivery status reporting
Thread-Index: AcP7JE1XEl15NqAPRPy+JWENsEPSbwARvOBw
To: vkg@lucent.com
Cc: jdrosen@dynamicsoft.com, cboulton@ubiquity.net, simple@ietf.org
X-OriginalArrivalTime: 25 Feb 2004 06:53:20.0694 (UTC) FILETIME=[0E07D560:01C3FB6C]
Content-Transfer-Encoding: quoted-printable
Sender: simple-admin@ietf.org
Errors-To: simple-admin@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/simple/>
Date: Wed, 25 Feb 2004 08:53:20 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable


> -----Original Message-----
> From: ext Vijay K. Gurbani [mailto:vkg@lucent.com]
> Sent: 25.February.2004 00:18
> To: Khartabil Hisham (Nokia-TP-MSW/Helsinki)
> Cc: jdrosen@dynamicsoft.com; cboulton@ubiquity.net; simple@ietf.org
> Subject: Re: [Simple] Advanced IM Reqs: Delivery status reporting
> 
> 
> 
> hisham.khartabil@nokia.com wrote:
> 
> > I see use cases for both: report-on-failure and report-on-delivery. 
> 
> Problem with affirmitive delivery notification is that it
> may cause notification storms when an IM is sent to a large
> list.  Not all users will remember to turn delivery
> notification _off_ when sending the IM to a large audience.
> 
> > Some people rely on the latter to learn when a recipient actually 
> > received (not necessarily read) the IM.  
> 
> I can't argue with that, to be sure; but is that the norm?
> 
> It appears that there are two cases to consider: a) where
> the IM system is tied to a presence system, and b) where
> it is not.  In (a), a sender can be reasonably sure when
> he sends the message that the recipient got it.  A
> confirmation for each message would simply be too awkward,
> given the volume of IMs that can be potentially exchanged.
> (b) is more akin to email; the sender sends a message
> not expecting an immediate response.  If the undelying
> network fails to deliver the message, it should let the
> sender know.  Otherwise, no further communications are
> needed.
> 
> > An natural extension to that is to learn when the IM was actually 
> > read.
> 
> I can see this as providing a utility in case (b) above.
> 
> > BTW, I don't see IM and SMTP as a fair comparison. 
> 
> For store-and-forward IM, I think SMTP is a good comparison.
> For real time interactive IM, I agree, it is not.
> 
> > IM and SMS is a better comparison.
> 
> I think we can -- and must -- do better than SMS.  AFAIK,
> if a SMS message is not delivered, the sender is not
> notified (correct me if I am wrong).  Once a sender sends
> a SMS, they generally assume that it will be delivered.
> We can do one better than SMS by notifying the sender if
> the IM could NOT be delivered.  If it is delivered (which
> will be a majority of the case), no notification needed.

SMS has delivery reports. If we want to do better, then we need allow both delivery report and failure report.

To answer your concern about the notification storm, there is some work going on right now in sipping to handle this situation. See the links below.

http://www.ietf.org/internet-drafts/draft-camarillo-sipping-transac-package-00.txt

/Hisham

> 
> Thanks.
> 
> - vijay
> -- 
> Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
> Wireless Networks Group/Internet Software and Services
> Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
> Naperville, Illinois 60566     Voice: +1 630 224 0216
> 

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple