RE: [Notifications] Use cases

<Zoltan.Ordogh@nokia.com> Fri, 27 July 2007 19:59 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 1IEVxq-0003cs-2i; Fri, 27 Jul 2007 15:59:06 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IEVxo-0003ck-Im for notifications-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 15:59:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEVxo-0003cP-91 for notifications@ietf.org; Fri, 27 Jul 2007 15:59:04 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEVxn-0005Mq-Fh for notifications@ietf.org; Fri, 27 Jul 2007 15:59:04 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l6RJwriI011698; Fri, 27 Jul 2007 22:58:56 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Jul 2007 22:58:53 +0300
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Jul 2007 22:58:53 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
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: [Notifications] Use cases
Date: Fri, 27 Jul 2007 22:58:29 +0300
Message-ID: <4C38DC11F6B4FF4FAEA73E30DB5AA157D77DF3@esebe199.NOE.Nokia.com>
In-Reply-To: <46AA4241.1060104@dcrocker.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Notifications] Use cases
Thread-Index: AcfQgWMK+d6p5l07SCGCsVyrbDWxWgAA0lkA
References: <4C38DC11F6B4FF4FAEA73E30DB5AA157D77DC3@esebe199.NOE.Nokia.com><46AA4560.8040408@isode.com> <46AA4241.1060104@dcrocker.net>
From: Zoltan.Ordogh@nokia.com
To: dcrocker@bbiw.net
X-OriginalArrivalTime: 27 Jul 2007 19:58:53.0114 (UTC) FILETIME=[8EAC61A0:01C7D088]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: 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

Oh, so it would be good to agree beforehand because I had completely different ideas.
Like:

Scenario
Joe wants to turn on his coffee machine in the morning so that when he wakes up, the coffee is already waiting...

Actors:
IMAP Server, Notification Server, Client (Joe's coffee machine), Joe

Pre-conditions
1. Joe goes to sleep but before doing so, He schedules a future mail delivery for Himself, 0600 in the morning (subject: coffee "1 big decaf +milk"; no body).
2. Client (Joe' coffee machine) is subscribed to Joe's mail events, particularly to the an event when an email arrives from Himself.
3. Client is configured to ingore all other mails that those from Joe with "coffee" in the subject line, and the hardware configuraton is satisfactory (has coffee, electricity, water, cups, etc).
4. The Notification Server supports sender and subject fields.
5. IMAP Server has AfterBLAST support.

Flow:
1. Future delivery is triggered at 0600 in the morning, therefore a new mail arrive to Joe from Himself.
2. IMAP Server BLASTs some info to the Notification Server.
3. Notification Server informs the Client.
4. Client validates conditions and prepares Joe's coffee, as instructed by the subject field -> a big decaf coffee with milk.
5. As instructed by Joe's SIEVE script (that is triggered AfterBLAST), the unnecessary email is removed from the mailbox after the information was BLASTED to the Notification Server.

Alternate flow:
 - two coffees, one for the wife as well, using the same Client - using the same event.
 - two coffees, one for the wife as well, using the same Client - using different events.

Expected results:
 - the coffee conforms to the requested parameters.
 - Joe is a happy IMAPCoffee customer enjoying the benefits of his well-spent investment.

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

 

>-----Original Message-----
>From: ext Dave Crocker [mailto:dhc@dcrocker.net] 
>Sent: 27 July, 2007 22:07
>Cc: notifications@ietf.org
>Subject: Re: [Notifications] Use cases
>
>
>
>Alexey Melnikov wrote:
>> Zoltan.Ordogh@nokia.com wrote:
>> 
>>> Hello everyone,
>>> is there some sort of use case template available that we 
>should use, 
>>> or is it freestyle?
>>>
>> I think it is freestyle.
>
>
>Yeah, but as long as the question got asked, here are the 
>kinds of things I try to answer with a use case:
>
>
>Scenario:
>
>    What is it that someone wants to do, that they cannot 
>current do.  This is 
>a non-technical, user-level description.  Probably no acronyms 
>and certainly 
>no implementation choices.  (User-level can refer to 
>end-users, sysadmin, or 
>anyone else that is the consumer of the service.)
>
>
>Problem:
>
>    What prevents using existing tools for accomplishing this?
>
>
>Market:
>
>    Who needs this and should we believe they need it immediately?
>
>
>d/
>
>-- 
>
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>
>
>_______________________________________________
>Notifications mailing list
>Notifications@ietf.org
>https://www1.ietf.org/mailman/listinfo/notifications
>


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