Re: [Ldap-dir] DLAP Directorate review request for draft-dawkins-ldapext-subnot

Leif Johansson <leifj@sunet.se> Mon, 09 November 2009 07:42 UTC

Return-Path: <leifj@sunet.se>
X-Original-To: ldap-dir@core3.amsl.com
Delivered-To: ldap-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EAEE3A6B12 for <ldap-dir@core3.amsl.com>; Sun, 8 Nov 2009 23:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BuTuL7R-1mr5 for <ldap-dir@core3.amsl.com>; Sun, 8 Nov 2009 23:42:54 -0800 (PST)
Received: from smtp.su.se (smtp2.su.se [130.237.164.53]) by core3.amsl.com (Postfix) with ESMTP id 4D9603A6B13 for <ldap-dir@ietf.org>; Sun, 8 Nov 2009 23:42:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.su.se (Postfix) with ESMTP id 4DFB18198B; Mon, 9 Nov 2009 08:43:19 +0100 (CET)
X-Virus-Scanned: by amavisd-new at av-in.su.se
Received: from smtp.su.se ([127.0.0.1]) by localhost (smtp2.su.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FKO8NNZoqVYN; Mon, 9 Nov 2009 08:43:18 +0100 (CET)
Received: from [133.93.19.61] (host-19-61.meeting.ietf.org [133.93.19.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.su.se (Postfix) with ESMTPSA id A3A518197C; Mon, 9 Nov 2009 08:43:16 +0100 (CET)
Message-ID: <4AF7C809.6040001@sunet.se>
Date: Mon, 09 Nov 2009 08:43:05 +0100
From: Leif Johansson <leifj@sunet.se>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
References: <7A57206D08E2483A8136B7AEA627CEB1@china.huawei.com> <4AD62F79.6090703@isode.com> <4AF777ED.1040206@it.su.se> <EA6268A4-29F1-488B-87FB-C07C042F1C2A@Isode.com>
In-Reply-To: <EA6268A4-29F1-488B-87FB-C07C042F1C2A@Isode.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Spencer Dawkins <spencer@wonderhamster.org>, Leif Johansson <leifj@it.su.se>, LDAP Directorate <ldap-dir@ietf.org>, Lisa Dusseault <lisa.dusseault@gmail.com>, Xun Peng <xunpeng@huawei.com>
Subject: Re: [Ldap-dir] DLAP Directorate review request for draft-dawkins-ldapext-subnot
X-BeenThere: ldap-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Directorate <ldap-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldap-dir>, <mailto:ldap-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ldap-dir>
List-Post: <mailto:ldap-dir@ietf.org>
List-Help: <mailto:ldap-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldap-dir>, <mailto:ldap-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 07:42:55 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kurt Zeilenga wrote:
> It seems to me we that we have "good enough" content synchronization
> mechanisms in LDAP, but don't have any (formalized) event notification
> mechanism.
> 
> For instance, consider an intrusion detection system which wants
> notification of all password change requests, including information
> about the requestor and the outcome of the request.  At present, such
> systems tend to rely on vendor-specific audit logs.

Right.

> 
> I could support an effort to analysis requirements for event
> notification and, then, build a mechanism specifically designed to met
> these requirements.
> 
> What I don't support is designing yet another "content synchronization"
> mechanism.
> 
> But what does 3GPP want?  It seems to me they were more after content
> synchronization than event notification.

Quite often the two notions get mixed up in requirements and maybe
that is the case here too. I'd volunteer to help clean up the reqs
with Spencer and anyone else who are interested.

> 
> It's not clear to me whether you are after content synchronization than
> event notification.

I don't know about 3gpp but for the metadirectory applications I've
seen I think notification would get you quite far.
	
	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkr3yAkACgkQ8Jx8FtbMZnc3lwCeK7WTG9Eu3wkjYCvA0rQfa0NG
v30An13z3SUDY7eV2m7Bp4m9mc9Xj+uL
=Ia1J
-----END PGP SIGNATURE-----