[ldapext] Next LDAPExt draft charter...
Ludovic Poitou <email@example.com> Tue, 24 November 2015 07:46 UTC
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C771A034F for <firstname.lastname@example.org>; Mon, 23 Nov 2015 23:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([188.8.131.52]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqVSzI2Dq25c for <email@example.com>; Mon, 23 Nov 2015 23:46:10 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 3C6631A034C for <firstname.lastname@example.org>; Mon, 23 Nov 2015 23:46:10 -0800 (PST)
Received: by wmuu63 with SMTP id u63so84280217wmu.0 for <email@example.com>; Mon, 23 Nov 2015 23:46:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:subject:mime-version:content-type; bh=68yaloODn2Q3ew4/DOgsBxyjU+CYvoEpnf6uO2SJCu0=; b=wOC/yt+FHI/6brPjwok653TMe7U9JOZGLlGqHmzqXeTAxSxIFNyObyAL67fWC6zqUe NVGygrvUclUyNdRLKU9XFvDVj5ffQEN5T2lDfeiuCdNj2QpXk23RA+rWgvYEYbG5iiHW dAMB4YEl6SIulmJCONXPPIrkurz4BbIZFiwnkHWBuNnIIVTARE4SeTQJ9ps2jCkt6s6Q FSGE84xJuepa6nFvlgdSPQqcWzzjfxSL+KfaIvXmiMFlJSr4Mrs/dmMaX91m7DFMKNkY AB1MAkXPx22d64PZglN4N9VCbWQm4Zxp80imQOYpAZP3L2em2uOiLymBYYPOw07zBtxc c7GA==
X-Received: by 10.28.51.135 with SMTP id z129mr20868366wmz.19.1448351168764; Mon, 23 Nov 2015 23:46:08 -0800 (PST)
Received: from lpm.local (cro38-1-82-236-150-92.fbx.proxad.net. [184.108.40.206]) by smtp.gmail.com with ESMTPSA id h67sm16714218wmf.17.2015.11.23.23.46.07 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 Nov 2015 23:46:07 -0800 (PST)
Date: Tue, 24 Nov 2015 08:46:06 +0100
From: Ludovic Poitou <firstname.lastname@example.org>
To: Barry Leiba <email@example.com>, Howard Chu <firstname.lastname@example.org>
X-Mailer: Airmail Beta (337)
Content-Type: multipart/alternative; boundary="565415be_19692e66_1b08"
Subject: [ldapext] Next LDAPExt draft charter...
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2015 07:46:13 -0000
Hi Barry, Please find below, the initial draft charter for a new working group at IETF on the trail of the LDAPEXT working group (I don’t know if we can reuse the name of a closed WG). As it’s been discussed on the ldapext mailing list already, the DBIS work has been left out of the draft charter, but possibly could be integrated within the first work element. Please let us know if this draft charter is acceptable or needs to be adapted to lead to the creation of the Working Group as soon as possible. Kind regards, Ludovic. --- Working Group Name: LDAP Extension (ldapext) IETF Area: Applications and Real-Time (ART) Area Chair(s): Howard Chu (email@example.com) Ludovic Poitou (firstname.lastname@example.org) Applications and Real-Time (ART) Area Director(s): Ben Campbell (email@example.com) Alissa Cooper (firstname.lastname@example.org) Barry Leiba (email@example.com) Responsible Area Director: Barry Leiba (firstname.lastname@example.org) Mailing Lists: General Discussion:email@example.com To Subscribe: https://www.ietf.org/mailman/listinfo/ldapext Archive: http://www.ietf.org/mail-archive/web/ldapext/ Description of Working Group: The LDAPExt working group is charter to standardize extensions to LDAPv3 (RFC 4510) standards. Some years ago, under the umbrella of a former ldapext WG or as individual submissions, several extensions were proposed in the form of experimental RFCs and Internet Drafts. Although not finalized, these specifications have been implemented by different vendors, with various interpretations leading to subtle interoperability issues. The working group will do the following: Finish existing and implemented Internet Drafts and publish them as Proposed Standards: * An Approach for Using LDAP as a Network Information Service (RFC 2307) was published as an Experimental RFC. Soon after, revisions appeared as draft-howard-rfc2307bis. The objective is to conclude this work in compliance with the IANA guide-lines, but preserving interoperability with existing implementations. * Define an information model and protocol to support Password Policy for LDAP Directories, based on previous work described in draft-behera-ldap-password-policy, considering the issues raised in draft-zeilenga-ldap-passwords but preserving interoperability with existing implementations. Define new extensions: * An inetOrgPerson 2.0 schema to aggregate the needs and changes for entries representing Persons in a Directory. * Resolve issues with the representation of Groups in LDAP. draft-findlay-ldap-groupofentries * Define utility schema descriptions widely used: draft-stroeder-namedobject and draft-stroeder-mailboxrelatedobject * Define an informational document that describes the various representations of hashed password values in the 'userPassword' attribute. draft-stroeder-hashed-userpassword-values Goals and Milestones: Jan 2016 Issue new versions of Groups in LDAP, Utility Schemas and Hashed Password Values. Apr 2016 Issue first revision Internet-Draft of inetOrgPerson 2.0. Issue first revision Internet-Draft on RFC 2307 revision. Issue first revision Internet-Draft on password policy. Jul 2016 Submit Groups in LDAP, Utility Schemas and Hashed Password Values to IESG for publication as an RFC. Oct 2016 Submit inetOrgPerson 2.0 schema to IESG for publication as an RFC. Achieve consensus on RFC 2307 Revision and Password Policy for LDAP. Jan 2017 Submit RFC 2307 Revision and Password Policy to IESG for consideration as a Proposed Standard. -- Ludovic Poitou http://ludopoitou.com
- [ldapext] Next LDAPExt draft charter... Ludovic Poitou