Re: [ldapext] draft charter comment

Ludwig Krispenz <lkrispen@redhat.com> Fri, 27 October 2017 10:31 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 A5DA613B13B for <ldapext@ietfa.amsl.com>; Fri, 27 Oct 2017 03:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 CozwqCUPZsjq for <ldapext@ietfa.amsl.com>; Fri, 27 Oct 2017 03:31:20 -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 6FE1B13A5A3 for <ldapext@ietf.org>; Fri, 27 Oct 2017 03:31:20 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2062560177 for <ldapext@ietf.org>; Fri, 27 Oct 2017 10:31:20 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 2062560177
Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=lkrispen@redhat.com
Received: from [10.36.117.23] (ovpn-117-23.ams2.redhat.com [10.36.117.23]) by smtp.corp.redhat.com (Postfix) with ESMTP id B0AE05D96D for <ldapext@ietf.org>; Fri, 27 Oct 2017 10:31:19 +0000 (UTC)
Message-ID: <59F30BC9.3030603@redhat.com>
Date: Fri, 27 Oct 2017 12:34:49 +0200
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: 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>
In-Reply-To: <59F30B2E.9030807@redhat.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Fri, 27 Oct 2017 10:31:20 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ldapext/SEgwGqaSn9faaqv5HjLHQnBaSEY>
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: Fri, 27 Oct 2017 10:31:22 -0000

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
>
> the other one was raised at ldapcon2015 by ChristianHollenstein to 
> extend rfc 5805  - LDAP transaction to allow a client to define the 
> txn id and to allow to omit the txn control after a txn was started. 
> Howard said he also had the need for some extensions to the protocol, 
> but I do not remember what exactly. So I have some difficulties to 
> find the right wording
>>
>> 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