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

Ludovic Poitou <ludovic.poitou@gmail.com> Thu, 05 February 2015 09:48 UTC

Return-Path: <ludovic.poitou@gmail.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 45CCA1A01A9 for <ldapext@ietfa.amsl.com>; Thu, 5 Feb 2015 01:48:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.815
X-Spam-Level:
X-Spam-Status: No, score=0.815 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=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 A90KxdHG-Hiq for <ldapext@ietfa.amsl.com>; Thu, 5 Feb 2015 01:48:29 -0800 (PST)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74E5B1A0166 for <ldapext@ietf.org>; Thu, 5 Feb 2015 01:48:29 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id k14so6499259wgh.10 for <ldapext@ietf.org>; Thu, 05 Feb 2015 01:48:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type; bh=jtW0y7ZsgLK335/rL1kNXslsGqMa+seGb8Ue4LvJakk=; b=zc8jVg9PDXspl92g1F7yyZvzK2TRED0A6KSIrq95XtxzRWPOm/jZicQK2xq5dx1Nyf 3317nAOQjemVlYxEd8MjZNEbxevh5xSFfCLWrGMRBNI1fSfJFLnosFER8FMfJLM0h3nL dlKd3wXaNib+oAsJ0bjBa2GlfqSblEJgkeYhHnXHl/JzL/GRkxuc8F4sjnqdpGvc76jN gvoO/fWBcZTrdpRLiUhhC29Zdl2AnctSuZYqbVG22fiKqvHpjhVum2fiF0SIs2VMALBb 4DLUyIxFfRAXOmeOcuW3YGuGiTnDUFgJHsBGyumnr8u61NUjh4o046EeyniB4hnm5Wqq lq6w==
X-Received: by 10.194.108.162 with SMTP id hl2mr5938411wjb.134.1423129708154; Thu, 05 Feb 2015 01:48:28 -0800 (PST)
Received: from lpm.local ([2a01:e35:2ec9:65c0:59ae:c20e:fe6:cb69]) by mx.google.com with ESMTPSA id bv16sm16495686wib.0.2015.02.05.01.48.25 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Feb 2015 01:48:26 -0800 (PST)
Date: Thu, 5 Feb 2015 10:48:24 +0100
From: Ludovic Poitou <ludovic.poitou@gmail.com>
To: =?utf-8?Q?Michael_Str=C3=B6der?= <michael@stroeder.com>, =?utf-8?Q?Cl=C3=A9ment_OUDOT?= <clem.oudot@gmail.com>
Message-ID: <etPan.54d33c68.1190cde7.8230@lpm.local>
In-Reply-To: <CAK_oV4_WSDvJrqRgoiQX4ccT0KtVNeugyiX7uwYRNCBFX1R=JQ@mail.gmail.com>
References: <etPan.54c553b0.19e21bb2.1f2@lpm.local> <CAPcb_GJpf=KGYbfhfyU92Ea3Dvvvw_hb08z0US75SzUCd9iukQ@mail.gmail.com> <54C55A27.8020903@stroeder.com> <CAK_oV4_pJUZrrgaA0RzkJPGVPNG+EtYS0aQe-RRbJfbyA7dG+A@mail.gmail.com> <54C56900.8010105@stroeder.com> <CAK_oV4_WSDvJrqRgoiQX4ccT0KtVNeugyiX7uwYRNCBFX1R=JQ@mail.gmail.com>
X-Mailer: Airmail Beta (289)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="54d33c68_66ef438d_8230"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/OdhsBRHQPg_mReWnSgfP8X_0B0s>
Cc: LDAP Extensions list <ldapext@ietf.org>
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: Thu, 05 Feb 2015 09:48:31 -0000

Hi Clement,

There was a general consensus that the current password policy draft needs to be split in multiple documents to separate the configuration of it, the internal state representation and the management side of it (controls and possible extended operations).

Ludo
-- 
Ludovic Poitou
http://ludopoitou.com

On 5 Feb 2015 at 09:51:26, Clément OUDOT (clem.oudot@gmail.com) wrote:

2015-01-25 23:06 GMT+01:00 Michael Ströder <michael@stroeder.com>om>:
> Clément OUDOT wrote:
>> 2015-01-25 22:03 GMT+01:00 Michael Ströder <michael@stroeder.com>om>:
>>> Gavin Henry wrote:
>>>>> I would also like to hear about volunteers to work on those documents, either contributing text or reviewing them carefully.
>>>>
>>>> I would like to help where I can.
>>>
>>> Glad to here that. Do you have any particular interest.
>>>
>>> Everybody can start reviewing existing stuff. Which could also mean that you
>>> simply ask questions if something is not clear enough.
>>>
>>> For inetOrgPerson 2.0 it would help if we collect a wish list and then compile
>>> a realistic requirement list from that.
>>
>> I am also volunteer to help, especially on the password policy draft.
>
> Would you be willing to act as an editor?
>
> If yes, then simply start a new e-mail thread.
>
> A good start would be to agree on a goal.
>
> IMHO we should try to mainly document current state of implementations of
> draft-behera-ldap-password-policy, but also have a closer look on Appendix A
> of http://tools.ietf.org/html/draft-zeilenga-ldap-passwords-00
>
> Digging the list archives could also help here.


Hi,

thanks for the inputs, I will do my best to work on this. I'll try to
start on new thread on the subject.


Clément OUDOT.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext