Re: [ldapext] inetOrgPerson 2.0

Dieter Klünter <dk@sys4.de> Tue, 07 November 2017 11:22 UTC

Return-Path: <dk@sys4.de>
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 E041713FDDD for <ldapext@ietfa.amsl.com>; Tue, 7 Nov 2017 03:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sys4.de
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 GuQDdMJB-kiz for <ldapext@ietfa.amsl.com>; Tue, 7 Nov 2017 03:22:31 -0800 (PST)
Received: from mail.sys4.de (mail.sys4.de [194.126.158.132]) (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 B7CEC13FDD9 for <ldapext@ietf.org>; Tue, 7 Nov 2017 03:22:31 -0800 (PST)
Received: from pink.fritz.box (p5DD6F954.dip0.t-ipconnect.de [93.214.249.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.sys4.de (Postfix) with ESMTPSA id 3yWRpZ0xPVz1dK7 for <ldapext@ietf.org>; Tue, 7 Nov 2017 12:21:58 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sys4.de; s=dk-sys4-de-201501; t=1510053718; bh=lD/dEK8xqXFbb6InclwAF4sOE4BtBwVc6xnfjK6ddJE=; h=Subject:To:References:From:Date:In-Reply-To; b=JIUXihZNpugiqqyNYBYz7+qwwf95q/Vl6MJKfPxUrsZAp3B+M6GoJPDBIGluwtPVm XMQgoHGqpqilpwE7kw64ZwgOSE3jCv9L5QdfxH5wVAxwJKhRXcGKgp/MVgIICL6K6G 6WlcG/QB8+QHRwaSq2SroWpXHD9gu1tISiXduO+F1zUUFPudfVo5/zv3K/sGKTgeAO EyuLj26rwlrbLTGx840jAFDTjCeSpcP5u0bo3oi5Hqj0t8vbphuWBVtr9LWKqKmoXQ RHlbSn10KC2COYm3XF3KfaQEWp1r0UCXkdwvCFyIdR189ZXZhYNExu/W7Y1jZzkcNp uc1DcYnPAwSDw==
To: ldapext@ietf.org
References: <1509061159.20220.91.camel@redhat.com> <20171107092304.GM25671@slab.skills-1st.co.uk> <9246dd86-5e02-38d8-5425-a0c48199ffa4@stroeder.com>
From: =?UTF-8?Q?Dieter_Kl=c3=bcnter?= <dk@sys4.de>
Message-ID: <e4bcf6a4-3a6d-46be-e61c-840ae52b5a16@sys4.de>
Date: Tue, 7 Nov 2017 12:22:32 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <9246dd86-5e02-38d8-5425-a0c48199ffa4@stroeder.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: de-DE
X-Sigh: S/MIME sigh milter - version 1607.1.5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ldapext/zNTQVqNmgJDfz127FFlJdXvueIA>
Subject: Re: [ldapext] inetOrgPerson 2.0
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: Tue, 07 Nov 2017 11:22:35 -0000

Am 07.11.2017 um 10:53 schrieb Michael Ströder:
> Andrew Findlay wrote:
>> On Fri, Oct 27, 2017 at 09:39:19AM +1000, William Brown wrote:
>>
>>> https://mailarchive.ietf.org/arch/msg/ldapext/4fEh3Y9adJEl24r2F0598bnXrcg/?qid=f94a915c2574190c029541bc1d190a5e
>> Looks good to me, and I am certainly willing to do some of the work.
> Glad to hear that.
>
>> What was inetOrgPerson 2.0 all about?
> Missing attributes we all add later by defining yet another custom
> person object class.
>
> Possible examples:
> birthName, birthPlace, buildingName, businessTitle, c (alias
> countryName), dateOfBirth, delegatesTo, employeeType, gender, nickName,
> organizationalStatus, personalTitle, serialNumber, uniqueIdentifier,
> userClass
>
> I'm pretty sure many of us have other attributes to add.
> We could try to build up on the schema work in the higher-education
> community but should carefully try avoid bloat.
>
> We could also consider to deprecate use of some attributes in new
> deployments. As recommendation for local profiles we might even define
> DIT content rules with NOT as formal but optional deprecation spec.
>
> Possibe deprecation examples:
> internationaliSDNNumber
> photo (Fax syntax!)
> x500UniqueIdentifier
We should have a look at X500 and X520 latest edition (2016) first. 
There are some new attribute types, which might be of interest.


-Dieter