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

Leif Johansson <leifj@it.su.se> Thu, 09 August 2007 14:20 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 1IJ8sc-0008H6-12; Thu, 09 Aug 2007 10:20:50 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IJ8sa-0008H0-RV for notifications-confirm+ok@megatron.ietf.org; Thu, 09 Aug 2007 10:20:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJ8sa-0008Gs-HU for notifications@ietf.org; Thu, 09 Aug 2007 10:20:48 -0400
Received: from smtp3.su.se ([130.237.93.228]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJ8sY-0002rU-U2 for notifications@ietf.org; Thu, 09 Aug 2007 10:20:48 -0400
Received: from localhost (localhost [127.0.0.1]) by smtp3.su.se (Postfix) with ESMTP id C7C683BF12; Thu, 9 Aug 2007 16:20:43 +0200 (CEST)
Received: from smtp3.su.se ([127.0.0.1]) by localhost (smtp3.su.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14702-01-21; Thu, 9 Aug 2007 16:20:43 +0200 (CEST)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.su.se (Postfix) with ESMTP id 664663BEA8; Thu, 9 Aug 2007 16:20:43 +0200 (CEST)
Message-ID: <46BB22CE.5090007@it.su.se>
Date: Thu, 09 Aug 2007 16:21:02 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
Subject: Re: [Notifications] Statement of interest, and comments on scope
References: <46B853C5.1040807@ninebynine.org> <46B98D7F.6090403@it.su.se> <46BAD5F7.8040501@ninebynine.org>
In-Reply-To: <46BAD5F7.8040501@ninebynine.org>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at smtp.su.se
X-Spam-Status: No, hits=-2.28 tagged_above=-99 required=7 tests=[AWL=0.032, BAYES_00=-2.312]
X-Spam-Level:
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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

>
> So what does my request amount to in practical terms?  Given that the proto-WG
> is aiming to produce specifications for email event notifications that can work
> with existing notification protocols, I'd like to see that teased apart into two
> layers:
> (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.
>
>   
+1 - it seems realistic although it is important that the wg is able to
put some meat on (a) so that it has implications for interoperability.
> I hope this helps to clarify my position.
>
>   
At least for me it does.

    Cheers Leif



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