[ldapext] Content Synchronization Operation + Transactions

Petr Spacek <pspacek@redhat.com> Wed, 03 June 2015 07:35 UTC

Return-Path: <pspacek@redhat.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC7211B35F2 for <ldapext@ietfa.amsl.com>; Wed, 3 Jun 2015 00:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.012
X-Spam-Level:
X-Spam-Status: No, score=-5.012 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y2monHwkSiJ9 for <ldapext@ietfa.amsl.com>; Wed, 3 Jun 2015 00:35:37 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C06DE1B35EE for <ldapext@ietf.org>; Wed, 3 Jun 2015 00:35:37 -0700 (PDT)
Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id 678EF8E694 for <ldapext@ietf.org>; Wed, 3 Jun 2015 07:35:37 +0000 (UTC)
Received: from pspacek.brq.redhat.com (pspacek.brq.redhat.com [10.34.128.7]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t537ZZYh026334 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ldapext@ietf.org>; Wed, 3 Jun 2015 03:35:36 -0400
Message-ID: <556EAE47.10406@redhat.com>
Date: Wed, 03 Jun 2015 09:35:35 +0200
From: Petr Spacek <pspacek@redhat.com>
Organization: Red Hat
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: ldapext@ietf.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/TWei-Z2bP28J2fuyT-8bHLG5c0E>
Subject: [ldapext] Content Synchronization Operation + Transactions
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2015 07:35:39 -0000

Hello,

it seems to me that LDAP Transactions (RFC 5805) are not perfectly integrated
into Content Synchronization Operation (RFC 4533).

Mainly the client has no idea what changes were part of single transaction. As
a result, client cannot replicate transactions reliably, especially when
connection drops in the middle of persist phase of Content Synchronization
Operation.

Also some clients could use the information where LDAP transaction
started/ended for application-level transactions (if the application uses the
data in real-time) or possibly some optimizations (if some application-level
work needs to be done after each group of updates).

I'm going to sketch -00 draft which will attempt to address this, probably by
adding new messages to indicate where transaction started and ended.
Naturally, this makes sense only for persist phase.


I would welcome early feedback about this idea even before the -00 is published.

Thank you very much for your time!

-- 
Petr Spacek  @  Red Hat