Re: AW: Follow-up on Naming of Subentries

Fantou Patrick wrote:
> 
> Hi Mark,
> 
> I cannot follow too much the reason of your requirement
> to use another naming attribute as cn for a subentry.
> In fact a good administrator will choose a name for a subentry which says something
> about the content of the subentry, for instance
> cn=subschemaSubentry or cn=accesscontrolSubentry,
> independantly of the naming attribute used, and this , more than the naming attribute itself
> would avoid conflicts.

The difficulty comes when subentries and object entries are being 
automatically created by two different applications.  These applications
would need to have some algorithmic ways of coming up with attribute values.
But this doesn't seem appropriate to use 'cn' for such things if there is 
some other attribute type that better describes what the application wants
to use.  Forcing them to use cn with a value which is perhaps some string
encoding of a GUID/UUID seems to counter the benefit of having typed RDNs.


Mark Wahl
Sun Microsystems Inc.