[Notifications] Reliability

<Zoltan.Ordogh@nokia.com> Thu, 09 August 2007 08:57 UTC

Return-path: <notifications-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJ3pd-0008HC-19; Thu, 09 Aug 2007 04:57:25 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IJ3pb-0008Gx-Pg for notifications-confirm+ok@megatron.ietf.org; Thu, 09 Aug 2007 04:57:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJ3pb-0008Gp-A6 for notifications@ietf.org; Thu, 09 Aug 2007 04:57:23 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJ3pa-0005xB-Fi for notifications@ietf.org; Thu, 09 Aug 2007 04:57:22 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l798vCOT005941 for <notifications@ietf.org>; Thu, 9 Aug 2007 11:57:20 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Aug 2007 11:57:15 +0300
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Aug 2007 11:57:15 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: [Notifications] Reliability
Date: Thu, 09 Aug 2007 11:56:44 +0300
Message-ID: <4C38DC11F6B4FF4FAEA73E30DB5AA157E3F135@esebe199.NOE.Nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Notifications] Reliability
Thread-Index: AcfaYzXihpsbDxx4RmeflLMsErg8ig==
From: Zoltan.Ordogh@nokia.com
To: notifications@ietf.org
X-OriginalArrivalTime: 09 Aug 2007 08:57:15.0903 (UTC) FILETIME=[48A970F0:01C7DA63]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Message Notifications interest group discussion list <notifications.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/notifications>
List-Post: <mailto:notifications@ietf.org>
List-Help: <mailto:notifications-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0051658512=="
Errors-To: notifications-bounces@ietf.org

Hi all,
We have briefly touched the reliability issue during the BoF, but we did not actually go trhough with it.
If this notification is not going to be reliable, what's the use for it? I mean:
You have a new mail, but You don't get a notification - what the use of the whole framework then?
Any thoughts on this?
Thank You.

Best regards: Zoltán Ördögh
E-mail: zoltan dot ordogh at nokia dot com
Phone: +358 50 386 0566


_______________________________________________
Notifications mailing list
Notifications@ietf.org
https://www1.ietf.org/mailman/listinfo/notifications