From ldapext-bounces@ietf.org Fri Jul 21 15:56:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G416P-0001NC-7k; Fri, 21 Jul 2006 15:56:01 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G416N-0001Ft-CT for ldapext@ietf.org; Fri, 21 Jul 2006 15:55:59 -0400 Received: from mxout7.cac.washington.edu ([140.142.32.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G413d-0002Is-Ka for ldapext@ietf.org; Fri, 21 Jul 2006 15:53:10 -0400 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.6+UW06.06/8.13.6+UW06.03) with ESMTP id k6LJr8Ir012052 for ; Fri, 21 Jul 2006 12:53:08 -0700 X-Auth-Received: from D-140-142-21-219.dhcp4.washington.edu (D-140-142-21-219.dhcp4.washington.edu [140.142.21.219]) (authenticated authid=rlmorgan) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.03) with ESMTP id k6LJr85l001500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 21 Jul 2006 12:53:08 -0700 Date: Fri, 21 Jul 2006 12:53:40 -0700 (PDT) From: "RL 'Bob' Morgan" X-X-Sender: rlmorgan@perf.cac.washington.edu To: IETF ldapext WG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [ldapext] RFC 4533 implementations? 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 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. Thanks, - RL "Bob" _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext