IETF Logo Mail Archive

Re: [ldapext] LDAP work at IETF...

Michael Ströder <michael@stroeder.com> Fri, 23 January 2015 16:22 UTC

Return-Path: <michael@stroeder.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 BF41C1A9126 for <ldapext@ietfa.amsl.com>; Fri, 23 Jan 2015 08:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level:
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_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 V3MhrRdZBAwn for <ldapext@ietfa.amsl.com>; Fri, 23 Jan 2015 08:22:31 -0800 (PST)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 678E81A8AE7 for <ldapext@ietf.org>; Fri, 23 Jan 2015 08:22:31 -0800 (PST)
Received: from srv4.stroeder.local (srv4.stroeder.local [10.1.1.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.stroeder.local", Issuer "stroeder.com Server CA no. 2009-07" (not verified)) by srv1.stroeder.com (Postfix) with ESMTPS id 309961D475 for <ldapext@ietf.org>; Fri, 23 Jan 2015 17:22:28 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by srv4.stroeder.local (Postfix) with ESMTP id F347B1DB07 for <ldapext@ietf.org>; Fri, 23 Jan 2015 17:22:26 +0100 (CET)
X-Virus-Scanned: amavisd-new at stroeder.local
Received: from srv4.stroeder.local ([127.0.0.1]) by localhost (srv4.stroeder.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dZEajAsCS3BQ for <ldapext@ietf.org>; Fri, 23 Jan 2015 17:22:20 +0100 (CET)
Received: from nb2.stroeder.local (nb2.stroeder.local [10.1.1.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by srv4.stroeder.local (Postfix) with ESMTPS id 8322A1CE25 for <ldapext@ietf.org>; Fri, 23 Jan 2015 17:22:18 +0100 (CET)
Message-ID: <54C2753A.8030902@stroeder.com>
Date: Fri, 23 Jan 2015 17:22:18 +0100
From: Michael Ströder <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 SeaMonkey/2.32
MIME-Version: 1.0
To: ldapext@ietf.org
References: <etPan.54c26d68.175dfcf0.1f2@lpm.local>
In-Reply-To: <etPan.54c26d68.175dfcf0.1f2@lpm.local>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms050809080804080903080409"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/nvyWGJhUKXAc64YnGdKnbWzPEms>
Subject: Re: [ldapext] LDAP work at IETF...
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: Fri, 23 Jan 2015 16:22:33 -0000

Ludovic Poitou wrote:
> Please find below the list of documents that have been considered for the
> working group to finalise and get published (in no specific order):

For a WG we probably have to write a charter.
Who's willing to draft one?

> draft-stroeder-namedobject 
> draft-stroeder-hashed-userpassword-values (informational
> draft-stroeder-mailboxrelatedobject 

Obviously I'm interested to proceed with these drafts under the umbrella of a
new/revived LDAP WG within IETF.

> RFC2307bis 

Recent work also raised my interested to get this in a really good shape as a
possible base line for more sophisticated approaches like DBIS or Æ-DIR (TBR).
So I'd be willing to act as an editor if Howard does not have the time for it.
Kurt recently raised the bar regarding IANA considerations though.

> draft-behera-ldap-password-policy

We already shortly discussed this at LDAPcon 2013. Anyone here?

> inetOrgPerson 2.0

This will be surely a larger work item with a lot of different opinions
(although most people are missing the same things).

Ciao, Michael.

v2.23.0 | Report a Bug | By Email