Re: [ldapext] referencing attribute types

Michael Ströder <michael@stroeder.com> Wed, 08 November 2017 23:02 UTC

Return-Path: <michael@stroeder.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 E5F32126C22 for <ldapext@ietfa.amsl.com>; Wed, 8 Nov 2017 15:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ctq2153yo_7b for <ldapext@ietfa.amsl.com>; Wed, 8 Nov 2017 15:02:12 -0800 (PST)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99319124B0A for <ldapext@ietf.org>; Wed, 8 Nov 2017 15:02:11 -0800 (PST)
Received: from mail1.hv.local (mail.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 02E3731D; Thu, 9 Nov 2017 00:02:07 +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 mail1.hv.local (Postfix) with ESMTPS id A7AE97A; Thu, 9 Nov 2017 00:02:07 +0100 (CET)
To: =?UTF-8?Q?Dieter_Kl=c3=bcnter?= <dk@sys4.de>, ldapext@ietf.org
References: <e47f76a5-a589-71de-3de2-e85c2f089748@sys4.de>
From: =?UTF-8?Q?Michael_Str=c3=b6der?= <michael@stroeder.com>
Openpgp: id=43C8730E84A20E560722806C07DC7AE36A8BC938
Message-ID: <e7f961a5-cb26-7153-2f16-e47d63002679@stroeder.com>
Date: Thu, 9 Nov 2017 00:02:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 SeaMonkey/2.49.1
MIME-Version: 1.0
In-Reply-To: <e47f76a5-a589-71de-3de2-e85c2f089748@sys4.de>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms050803050302070606060003"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ldapext/JbdWZnXvWaCJULl7kODYFglOGeo>
Subject: Re: [ldapext] referencing attribute types
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: Wed, 08 Nov 2017 23:02:14 -0000

Dieter Klünter wrote:
> As we are going to restructure schemas and attribute types,

Huh? Which text in the ldapext draft charter indicates that we are
"going to restructure schemas and attribute types"?

The work item "inetOrgPerson 2.0 schema" is meant to just update or
replace RFC 2798. No more, no less. And I'd be willing to work on this one.

> I would suggest to adopt X.520 structure of attribute types. That is
If you want to add work items you should come up with precise text for
ldapext draft charter describing what to do. And you should commit
yourself to work on it.

> I propose to map following attribute type originating from X.520 to a
> ldap schema:
> 
> dnQualifier and organizationIdentifier.

Personally I see no use for 'dnQualifier'. And 'organizationIdentifier'
would be more suitable in a update for RFC 4519 which we do *not* have
on our list yet.

Again:
Just mentioning ideas here is not enough.
You guys have to come up with charter text and put your name on work items!

Ciao, Michael.