From ldapext-bounces@ietf.org Mon Jan 15 12:55:06 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6W2K-00073A-6c; Mon, 15 Jan 2007 12:54:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6W2J-0006ws-0g for ldapext@ietf.org; Mon, 15 Jan 2007 12:54:23 -0500 Received: from ns1.sys-net.it ([194.244.21.114] helo=mail.sys-net.it) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6W2F-0002NB-Ht for ldapext@ietf.org; Mon, 15 Jan 2007 12:54:20 -0500 Received: from [131.175.154.35] (mbdyn-pm.aero.polimi.it [131.175.154.35]) (authenticated bits=0) by mail.sys-net.it (8.13.5.20060308/8.13.3) with ESMTP id l0FHrVCW023251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Jan 2007 18:53:31 +0100 Message-ID: <45ABBFDE.6000705@sys-net.it> Date: Mon, 15 Jan 2007 18:54:38 +0100 From: Pierangelo Masarati User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: "RL 'Bob' Morgan" Subject: Re: [ldapext] RFC 4533 implementations? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.5 required=4.5 tests=BAYES_00,SPF_FAIL autolearn=no version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on www.sys-net.it X-Spam-Score: 0.1 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: IETF ldapext WG X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ldapext-bounces@ietf.org RL 'Bob' Morgan wrote: > > Among the many recent LDAP related RFCs is: > > 4533 The Lightweight Directory Access Protocol (LDAP) Content > Synchronization Operation. K. Zeilenga, J.H. Choi. June 2006. > (Format: TXT=73895 bytes) (Status: EXPERIMENTAL) > > I'm aware that OpenLDAP has included implementations of both client and > server sides of this protocol for a while now. I'm curious whether > there are any other implementations, in particular implementations that > might support content synchronization between an (Open)LDAP directory > and non-directory contexts such as Java- or Windows-based application > systems. I have recently committed to OpenLDAP's HEAD code an independent client-side implementation of RFC 4533 which is basically a C-API that is intended to allow client-side content synchronization, i.e. to maintain a local cache of partial data, possibly updated live in case of refreshAndPersist mode. As such, it's pure RFC 4533, while slapd's built-in client side contains some implementor-specific extension to improve replication performances. I guess it doesn't really count as another implementation, since it's part of OpenLDAP, though. p. _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-bounces@ietf.org Mon Jan 15 13:31:02 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6WbO-0007Qe-Su; Mon, 15 Jan 2007 13:30:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6WbN-0007QY-I7 for ldapext@ietf.org; Mon, 15 Jan 2007 13:30:37 -0500 Received: from skunk.mtbrook.bozemanpass.com ([69.145.82.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6WbK-0007bz-74 for ldapext@ietf.org; Mon, 15 Jan 2007 13:30:37 -0500 Received: from [69.145.82.218] (unknown [69.145.82.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by skunk.mtbrook.bozemanpass.com (Postfix) with ESMTP id 3DF945582E2; Mon, 15 Jan 2007 10:30:25 -0800 (PST) Message-ID: <45ABC8C7.6000709@boreham.org> Date: Mon, 15 Jan 2007 11:32:39 -0700 From: David Boreham User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pierangelo Masarati , IETF ldapext WG Subject: Re: [ldapext] RFC 4533 implementations? References: <45ABBFDE.6000705@sys-net.it> In-Reply-To: <45ABBFDE.6000705@sys-net.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: david_list@boreham.org List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ldapext-bounces@ietf.org Does anyone know if it is possible to proxy Active Directory's sync protocol (dirsync) to RFC4533 ? If it is then it would be interesting/useful to build such a proxy because it would make AD compatible with RFC4533 clients. I know quite a bit about dirsync, having implemented two different sync products that use it, but I know next to nothing about 4533 at this point so excuse me if I'm floating off in space... a quick read of the rfc draft tells me that they're at least superficially semantically similar. I do see a fair but of un-met interest in an open source general purpose LDAP sync tool. Wider support for 4533 I think would help. _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext