Re: [ldapext] draft charter comment

Ludwig Krispenz <lkrispen@redhat.com> Wed, 08 November 2017 15:17 UTC

Return-Path: <lkrispen@redhat.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C99E512706D for <ldapext@ietfa.amsl.com>; Wed, 8 Nov 2017 07:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 vJIqdNyVo53n for <ldapext@ietfa.amsl.com>; Wed, 8 Nov 2017 07:17:13 -0800 (PST)
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 E7B14127369 for <ldapext@ietf.org>; Wed, 8 Nov 2017 07:17:12 -0800 (PST)
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6BA467E427; Wed, 8 Nov 2017 15:17:12 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 6BA467E427
Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=lkrispen@redhat.com
Received: from [10.36.116.241] (ovpn-116-241.ams2.redhat.com [10.36.116.241]) by smtp.corp.redhat.com (Postfix) with ESMTP id CE9746250D; Wed, 8 Nov 2017 15:17:11 +0000 (UTC)
Message-ID: <5A0320DE.3040204@redhat.com>
Date: Wed, 08 Nov 2017 16:21:02 +0100
From: Ludwig Krispenz <lkrispen@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: =?UTF-8?B?TWljaGFlbCBTdHLDtmRlcg==?= <michael@stroeder.com>
CC: ldapext@ietf.org
References: <1509061159.20220.91.camel@redhat.com> <02ca8531-454c-4034-1402-346a299c331c@highlandsun.com> <59F2DE48.6050905@redhat.com> <13c3dc67-b3c2-64f6-afae-d6df27a485e0@stroeder.com> <59F30B2E.9030807@redhat.com> <59F30BC9.3030603@redhat.com> <df3f0b95-9788-8208-7674-155bf44047fa@stroeder.com>
In-Reply-To: <df3f0b95-9788-8208-7674-155bf44047fa@stroeder.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Wed, 08 Nov 2017 15:17:12 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ldapext/omkNFO82AXWOsDZSnzw3kdeJ-Ds>
Subject: Re: [ldapext] draft charter comment
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Nov 2017 15:17:14 -0000

Hi,

On 11/06/2017 06:23 PM, Michael Ströder wrote:
> Ludwig Krispenz wrote:
>> On 10/27/2017 12:32 PM, Ludwig Krispenz wrote:
>>> On 10/27/2017 10:16 AM, Michael Ströder wrote:
>>>> Ludwig Krispenz wrote:
>>>>> [..] what I am missing is the topics of
>>>>> extending ldap transactions and sync repl - as we discussed in
>>>>> Edinburgh
>>>> Ludwig, could you come up with some text describing this as concrete
>>>> work items? Then we can discuss whether to add that or not.
>>> ok, one is:
>>> extend rfc4533 - Content Synchronization Operation to support ldap
>>> transactions
>> and there is a draft:
>> https://docs.ldap.com/specs/draft-spacek-ldapext-syncrepl-transaction-01.txt
> AFAICS this was never submitted as a I-D to IETF.
> Or did I overlook something?
>
> @Ludwig: Could you please contact the author and clarify whether he's
> still willing to work on this?
the author is now longer working in this area and his new employer also 
isn't interested.
But "if" an ldapserver supports ldap transactions and uses syncrepl for 
replication the txn boundaries get lost in replication unless the spec 
for sync repl is extended. So we may want to find another owner.
>
> Ciao, Michael.
>

-- 
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander