Subject naming

["Steiner Viktor, GD-IT453" <Viktor.Steiner@xxxxxxxxxxxxxxxx>]

Doesn't it come down to "Computer vs. Person"?  Shyh-Wei - like all of
us - grew up with computers which required us to use unambiguous keys.
And most of us accept this subservience.  

Later - and I think that is the idea behind the DNs (doesn't that mean
'Distinguished Name' - think about it!) of X.500 - some people felt
computers should be servants and not masters; we are after all persons,
living in a personal society, and we have the right to identify each
other (and the organisations we deal with) by names, rather than IDs.

"I saw Dave yesterday."
"Dave?"
"Yes, Dave Smith, you know."
"In Marketing?"
"No, he sits on the third floor above the canteen."
"Oh, the one with the beard?"
"Yes, that's right."

We're not interested that his ID is 6271534.  Let the computer worry
about unambiguous fields, but let me name entities with NAMES, where
necessary qualified by additional attributes to resolve ambiguities.
Mit freundlichen Grüssen / Meilleures salutations / Kind regards
Viktor Steiner, IT453

>If you are registered with Department of Commerce as SUID 19970001 today,
>then
>some other successful Dave Kemp can register as 20070001 10 years later,
>because the ACL's won't inadvetantly grant your accesses to SUID 20070001.
>
>> What precisely is the advantage of SUIDs over unique terminal RDN's?
>
>advantages:
>
>(1) explicitness in what field is going to be persistent and temporally
>unique
>(2) DN's do not need to be persistent and temporally unique and can be
>simpler
>(3) the SUID scheme is not tied to the X500-type of names
>
>Shyh-Wei
>
>