Re: [Notifications] Statement of interest, and comments on scope

Chris Newman <Chris.Newman@Sun.COM> Sat, 11 August 2007 01: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 1IJfbW-0006bi-SC; Fri, 10 Aug 2007 21:17:22 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IJfbV-0006bd-BV for notifications-confirm+ok@megatron.ietf.org; Fri, 10 Aug 2007 21:17:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJfbU-0006bT-Dd for notifications@ietf.org; Fri, 10 Aug 2007 21:17:20 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJfbO-0002ha-5s for notifications@ietf.org; Fri, 10 Aug 2007 21:17:20 -0400
Received: from fe-amer-04.sun.com ([192.18.108.178]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l7B1HDPl003938 for <notifications@ietf.org>; Sat, 11 Aug 2007 01:17:13 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JML006013YZ5K00@mail-amer.sun.com> (original mail from Chris.Newman@Sun.COM) for notifications@ietf.org; Fri, 10 Aug 2007 19:17:13 -0600 (MDT)
Received: from [10.0.1.21] ([10.1.110.5]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JML00M8Z4WM2L50@mail-amer.sun.com>; Fri, 10 Aug 2007 19:17:13 -0600 (MDT)
Date: Fri, 10 Aug 2007 18:17:22 -0700
From: Chris Newman <Chris.Newman@Sun.COM>
Subject: Re: [Notifications] Statement of interest, and comments on scope
In-reply-to: <46BAD5F7.8040501@ninebynine.org>
To: Graham Klyne <GK@ninebynine.org>, Leif Johansson <leifj@it.su.se>
Message-id: <BDA54FE536ECCB7677576D8E@446E7922C82D299DB29D899F>
MIME-version: 1.0
X-Mailer: Mulberry/3.1.6 (Mac OS X)
Content-type: text/plain; format="flowed"; charset="us-ascii"
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <46B853C5.1040807@ninebynine.org> <46B98D7F.6090403@it.su.se> <46BAD5F7.8040501@ninebynine.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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

Graham Klyne wrote on 8/9/07 9:53 +0100:
> (a) an abstract notification model, presumably based on pub-sub, that can be
> layered over existing (and new) protocols and is not of itself specific to
> email (even though it does not take account of wider requirements), and
> (b) an email-specific part that addresses how email notifications can be
> conveyed by such a framework.

I consider it unlikely an IETF WG could reach closure on an abstract model on 
this topic.  However, the point you're trying to make about modularity of 
design is an important one.  Mail store implementers usually don't want to be 
experts about notification systems and notification system implementers usually 
don't want to be experts about mail stores.  A good design is likely to take 
that into account.

                - Chris



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