IETF Logo Mail Archive

Re: [Notifications] Use cases

Cullen Jennings <fluffy@cisco.com> Wed, 15 August 2007 00:53 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 1IL78t-0004kg-4M; Tue, 14 Aug 2007 20:53:47 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IL78r-0004fi-Ss for notifications-confirm+ok@megatron.ietf.org; Tue, 14 Aug 2007 20:53:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IL78r-0004eT-Hk for notifications@ietf.org; Tue, 14 Aug 2007 20:53:45 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IL78r-0000nw-6m for notifications@ietf.org; Tue, 14 Aug 2007 20:53:45 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 14 Aug 2007 17:53:45 -0700
X-IronPort-AV: i="4.19,262,1183359600"; d="scan'208"; a="513571723:sNHT48721092"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l7F0riCm017279; Tue, 14 Aug 2007 17:53:44 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82]) by sj-core-5.cisco.com (8.12.10/8.12.6) with SMTP id l7F0rciG014932; Wed, 15 Aug 2007 00:53:38 GMT
In-Reply-To: <46C21AC1.4060003@it.su.se>
References: <4C38DC11F6B4FF4FAEA73E30DB5AA157D77DC3@esebe199.NOE.Nokia.com> <46AA4560.8040408@isode.com> <46AA4241.1060104@dcrocker.net> <953beacc0707301019l6170c84frff03cd14c8b39580@mail.gmail.com> <8377A826-8354-4784-B96F-A297AAAAB6AC@cisco.com> <46C17DC7.6070209@it.su.se> <8906B4EA-89A4-4C03-9A73-873F742696AF@cisco.com> <46C21AC1.4060003@it.su.se>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <3AA8838A-2743-4385-A2EF-9121B18A306E@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Notifications] Use cases
Date: Tue, 14 Aug 2007 17:52:20 -0700
To: Leif Johansson <leifj@it.su.se>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1154; t=1187139224; x=1188003224; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20[Notifications]=20Use=20cases |Sender:=20; bh=lVJ0RQv0hewxJPnLJFpHlxFIyvt0kkvCEbIiumxlK1k=; b=mZF7qOFH7J783zMrD5gDFvbZMGOZ36wEKRr3oso0FdwbScao5sv9zq2iNUsUg99LrW6amkmJ xwoCy1c60lkyVyhjVaymTxEtLd3Cn/UPGZzaP7rowKi5PyUJo0JVWtjZ;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: Rohan Mahy <rohan@ekabal.com>, notifications@ietf.org
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>
Errors-To: notifications-bounces@ietf.org

On Aug 14, 2007, at 2:12 PM, Leif Johansson wrote:

> Cullen Jennings wrote:
>>
>> On Aug 14, 2007, at 3:02 AM, Leif Johansson wrote:
>>
>>> Cullen Jennings wrote:
>>>>
>>>> It seems like this use case was pretty much outside the email
>>>> notifications scope we were trying to do for first version. Is  
>>>> this is
>>>> the you have have to have it , or the could wait till later  
>>>> category?
>>>>
>>>> On Jul 30, 2007, at 10:19 AM, Rohan Mahy wrote:
>>>>
>>>>
>>> Why? It sounds to me like a (relatively) straightforward
>>> combination of sieve and some notification mechanism
>>> running over the existing IM/Presence framework on
>>> the phone.
>>>
>>> Imo it nicely illustrates the need for multiple transports
>>> and why existing implementations of pubsub will be a
>>> natural point of integration.
>>>
>>>     Cheers Leif
>>
>> Ok - fair enough. However, if we start dealing with use case outside
>> of mail stores, I probably have over 100. I just failed to see how
>> this one involved a mail store.
> Isn't the the mailstore typically where sieve runs?

yes - you are right

>
>     Cheers Leif


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

v2.23.0 | Report a Bug | By Email