Re: [ldapext] draft charter comment

William Brown <wibrown@redhat.com> Thu, 02 November 2017 07:53 UTC

Return-Path: <wibrown@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 0F09F13FA64 for <ldapext@ietfa.amsl.com>; Thu, 2 Nov 2017 00:53:55 -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 F04jGwDkYMD8 for <ldapext@ietfa.amsl.com>; Thu, 2 Nov 2017 00:53:53 -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 3D5DD13F9F5 for <ldapext@ietf.org>; Thu, 2 Nov 2017 00:53:53 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id BDC76356C2 for <ldapext@ietf.org>; Thu, 2 Nov 2017 07:53:52 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com BDC76356C2
Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=wibrown@redhat.com
Received: from rei.prd.blackhats.net.au (vpn2-54-19.bne.redhat.com [10.64.54.19]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B8BC8600D2; Thu, 2 Nov 2017 07:53:51 +0000 (UTC)
Message-ID: <1509609229.19153.48.camel@redhat.com>
From: William Brown <wibrown@redhat.com>
To: Ludwig Krispenz <lkrispen@redhat.com>, ldapext@ietf.org
Date: Thu, 02 Nov 2017 17:53:49 +1000
In-Reply-To: <59F30BC9.3030603@redhat.com>
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>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-IrLWB0T2LrXS4kJftoaw"
Mime-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 02 Nov 2017 07:53:52 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ldapext/3Gvo5TgUXk5lXI8Wtnq1QeUXAwY>
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: Thu, 02 Nov 2017 07:53:55 -0000

On Fri, 2017-10-27 at 12:34 +0200, 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
> > 
> > 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.
> > > 
> 

Hey Michael,

Did you want to add these two comments to the charter? 

What date are we calling as the cut off and submission? 

Have we updated our list of glorious participants on the charter?

Thanks so much for pushing this forwards :) 

-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Australia/Brisbane