Re: people CN

A.Macpherson@bnr.co.uk Sun, 29 November 1992 13:17 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04551; 29 Nov 92 8:17 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04547; 29 Nov 92 8:17 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa05140; 29 Nov 92 8:18 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.01561-0@haig.cs.ucl.ac.uk>; Sun, 29 Nov 1992 12:47:20 +0000
Via: uk.ac.uknet-relay; Sun, 29 Nov 1992 12:47:15 +0000
Received: from eros.uknet.ac.uk by ben.uknet.ac.uk via UKIP with SMTP (PP) id <sg.19336-0@ben.uknet.ac.uk>; Sun, 29 Nov 1992 12:47:10 +0000
Received: from eurogate.bnr.co.uk by eros.uknet.ac.uk via UKIP with SMTP (PP) id <26796-0@eros.uknet.ac.uk>; Sun, 29 Nov 1992 12:47:17 +0000
Received: from bnr.co.uk by eurogate.bnr.co.uk with SMTP (PP) id <05438-0@eurogate.bnr.co.uk>; Sun, 29 Nov 1992 12:46:50 +0000
Received: from bnr.co.uk by innergate.bnr.co.uk with SMTP (PP) id <14539-0@innergate.bnr.co.uk>; Sun, 29 Nov 1992 12:46:40 +0000
Message-Id: <9211291246.9776@bhars79.bnr.co.uk>
Received: from bhars2.bnr.co.uk on bhars79.bnr.co.uk over SMTP (5.61++/UK-2.1-MX(bhars79)-19aug92.1); Sun, 29 Nov 92 12:46:37 GMT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: A.Macpherson@bnr.co.uk
Subject: Re: people CN
To: osi-ds@cs.ucl.ac.uk, wg-nap@rare.nl
Date: Sun, 29 Nov 92 12:46:35 GMT
In-Reply-To: <199211270838.AA12254@mitsou.inria.fr>; from "Christian Huitema" at Nov 27, 92 9:37 am
Organisation: BNR Europe Ltd, London Road, HARLOW, Essex England, CM17 9NA
Phone: +44 279 402423

Christian Huitema writes:
| 
| May I suggest that using a "Role" attribute would, in general, 
| be "a good thing"?
| Something like:
| 
| 	cn=Jacques Martin + Role=Director, O=FooBar, C=FR
| 
| would look quite reasonable, I think.
|

While it does indeed look reasonable, is human-acceptable .... It is a
nightmare to maintain.

A simple attribute such as "Department" (OU) within any organisation I
have worked is liable to change O(year/2), and role almost as
frequently.  Much as we would like to use this sort of thing for our
internal mail system, we find that the personal organizational # is the
only thing that gives mediun term stability.  Medium term stability is
essential where users of the service will cache a lookup ...  It's also
required for the case where an agent rather than the user directly or
semi-interactively will be making the search.

-- 
A.Macpherson@bnr.co.uk  - or -  andrew@bnr.ca  - or -  Post@bnr.co.uk
"Quot homines, tot sententiae"