[Notifications] Enterprise MWI Use Case

Cullen Jennings <fluffy@cisco.com> Fri, 27 July 2007 22:17 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 1IEY7p-00014X-NM; Fri, 27 Jul 2007 18:17:33 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IEY7n-00014H-N7 for notifications-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 18:17:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEY7n-000148-DP for notifications@ietf.org; Fri, 27 Jul 2007 18:17:31 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEY7n-0000xr-2T for notifications@ietf.org; Fri, 27 Jul 2007 18:17:31 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 27 Jul 2007 15:17:30 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CALsLqkarR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,590,1175497200"; d="scan'208"; a="168532162:sNHT40530438"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6RMHUgw007821 for <notifications@ietf.org>; Fri, 27 Jul 2007 15:17:30 -0700
Received: from [130.129.21.174] (rtp-vpn3-416.cisco.com [10.82.217.162]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l6RMGdTf018889 for <notifications@ietf.org>; Fri, 27 Jul 2007 22:17:29 GMT
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <0F4D841F-40E2-464E-AF1A-986012C41FCE@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: notifications@ietf.org
From: Cullen Jennings <fluffy@cisco.com>
Date: Fri, 27 Jul 2007 17:17:26 -0500
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=918; t=1185574650; x=1186438650; c=relaxed/simple; s=sjdkim2002; 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:=20Enterprise=20MWI=20Use=20Case |Sender:=20; bh=+LaQV+C3JuvGqDxOgVFYX2a/sow8YJrClGazzeGlBWU=; b=RYT9Uu0RcryCxJeCKUAymb8VnsSaVNIBALILBjbJDhvetYZOMROEQnjOUFkfiUNsBEeBGtku 4EkzHV+IIe8RSQZ/myXjv6JfbnhNl7N6ZAfS1+dzBS9ztiOUtzuU+MML;
Authentication-Results: sj-dkim-2; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [Notifications] Enterprise MWI Use Case
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

Phase 1:

Enterprise phones have a little red light on them. This light should  
be on if, and only if, the the email store as any unseen message that  
contain voicemails. I don't really know the precise term for "unseen"  
or "voicemail" mean in this context so hopefully someone can provide  
the right term. On average, this light changes state less than a 6  
times per day. A large system would have less than 100,000 phones  
receiving notifications. The network environment is typically 100Mbps  
although sometimes remote offices with a less than 500 phones will be  
on a slower WAN link. When the state on the email store changes, the  
red light needs to change in less than 10 seconds and changing in  
under 2 seconds is desirable. If a phone is power cycled, the state  
of the red light after the power cycle needs to be correct and can  
not wait for the next time the state changes.








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