On Tue, 25 Jul 1995 11:01:59 EDT, "Donald E. Eastlake 3rd" said:
telephone numbers. And they avoid being the privacy-violating huge
piles of data the DNs are forced to become in their strenuous effort
to assemble perfect globabl uniqueness out of existing non-unique
data.
Amen.
When we set up our X.500 server, we automatically loaded all the payroll
information into it (we use the X.500 server as the source for addresses
for sending W-2 forms and the printed phonebook, among other things).
We had to hand-code a special case because we had a collision on the DN
c=US(_at_)o=Virginia Tech(_at_)ou=Dining Services(_at_)ou=Owens Dining
Hall(_at_)cn=Mary J. Smith
Yes, there were *two* Mary J Smiths, both working as food servers in the
same dining hall. We disambiguated them for the directory's sake by
reigstering 'cn=Mary Smith' and 'cn=Mary J Smith', but there's still no
good way for people outside Owens to tell which is which.
Given that the v3 certificates allow rfc822 entities, I'd have to say that
'mjsmith(_at_)vt(_dot_)edu' and 'mjsmith2(_at_)vt(_dot_)edu' is just as
ambiguous, and won't
induce carpal tunnel syndrome....
Valdis Kletnieks
Computer Systems Engineer
Virginia Tech