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

Kurt Zeilenga <Kurt.Zeilenga@Isode.com> Mon, 09 November 2009 15:37 UTC

Return-Path: <Kurt.Zeilenga@Isode.com>
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 BFF3928C145 for <ldap-dir@core3.amsl.com>; Mon, 9 Nov 2009 07:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level:
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599]
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 rWBU3ItzjzcK for <ldap-dir@core3.amsl.com>; Mon, 9 Nov 2009 07:37:19 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id C2C3728C13A for <ldap-dir@ietf.org>; Mon, 9 Nov 2009 07:37:18 -0800 (PST)
Received: from [192.168.1.101] ((unknown) [75.141.233.128]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <Svg3QgAJmYOT@rufus.isode.com>; Mon, 9 Nov 2009 15:37:44 +0000
X-SMTP-Protocol-Errors: NORDNS
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
In-Reply-To: <4AF82FDF.1050704@pearlcrescent.com>
Date: Mon, 09 Nov 2009 07:37:01 -0800
Message-Id: <245FDEAF-ABA7-42BF-B048-F466F60BB7D2@Isode.com>
References: <7A57206D08E2483A8136B7AEA627CEB1@china.huawei.com> <4AD62F79.6090703@isode.com> <4AF777ED.1040206@it.su.se> <EA6268A4-29F1-488B-87FB-C07C042F1C2A@Isode.com> <4AF7C809.6040001@sunet.se> <4AF82FDF.1050704@pearlcrescent.com>
To: Mark Smith <mcs@pearlcrescent.com>
X-Mailer: Apple Mail (2.1076)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Cc: Spencer Dawkins <spencer@wonderhamster.org>, LDAP Directorate <ldap-dir@ietf.org>, Lisa Dusseault <lisa.dusseault@gmail.com>, Leif Johansson <leifj@it.su.se>, 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 15:37:19 -0000

On Nov 9, 2009, at 7:06 AM, Mark Smith wrote:

> I believe that the line between some content synchronization  
> scenarios and some event notification scenarios is blurry.

While I agree that the line between scenarios can be blurry, I do  
think it reasonable possible to categorize whether a mechanism is a  
general purpose content synchronization mechanism or a general purpose  
event notification mechanism.  The latter would typically include  
broad support for notification of events which didn't result in change  
the content(*) (such as non-update requests, failed update requests)  
and the former would not.

* While a failed operation might be recorded in the directory (such as  
in an audit log, or even in operational attributes of the target  
entry), failed operations are not (per directory specifications) alter  
directory content.  In categorize mechanisms, one should look only at  
truly "user application" content (content not maintained by the  
directory service).

-- Kurt