IETF Logo Mail Archive

Re: [Notifications] Use cases

Dave Crocker <dhc@dcrocker.net> Fri, 27 July 2007 19:06 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 1IEV97-0007Ec-Uj; Fri, 27 Jul 2007 15:06:41 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IEV96-0007EV-BW for notifications-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 15:06:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEV96-0007EN-1T for notifications@ietf.org; Fri, 27 Jul 2007 15:06:40 -0400
Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEV95-0004eF-KT for notifications@ietf.org; Fri, 27 Jul 2007 15:06:39 -0400
Received: from [172.28.169.71] ([67.97.210.2]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l6RJ6EId006372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <notifications@ietf.org>; Fri, 27 Jul 2007 12:06:15 -0700
Message-ID: <46AA4241.1060104@dcrocker.net>
Date: Fri, 27 Jul 2007 14:06:41 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
CC: notifications@ietf.org
Subject: Re: [Notifications] Use cases
References: <4C38DC11F6B4FF4FAEA73E30DB5AA157D77DC3@esebe199.NOE.Nokia.com> <46AA4560.8040408@isode.com>
In-Reply-To: <46AA4560.8040408@isode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: dhc@dcrocker.net
X-Spam-Score: 1.6 (+)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dcrocker@bbiw.net
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


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

v2.23.0 | Report a Bug | By Email