[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: objectclass of a subschemasubentry
At 08:49 AM 8/11/99 -0400, Ella Paton Bassett wrote:
>The subschema object class remains auxiliary. RFC 2252 should include
>the subentry object class. Entries for the subschema would include the
>object identifier for both the subschema object class and the subentry
>object class.
Thanks for the clarification (I misread your previous post... I
inadvertently s/subentry/subschema/ when I read it).
I also noticed that the LDUP specifications rely on an LDAPsubentry
structural object class. This seems more usable to me as it
doesn't require substreeSpecification attribute. The single valueness
of subtreeSpecifiation would disallows a subschemaSubentry from
being used to define rules for multiple namingContexts (which our
server currently supports).
I believe the LDAP RFCs should be clarified which structural
object class should be used for subschema subentries
and how a client may determine which subschema subentry
(listed in the RootDSE) applies to which namingcontexts.
X.500 gives one approach. Another would be use LDAPsubentry
as the structural object class for subentries. As clients
can determine which subschema rules applies on a per DSE
basis already, listing of such in the subschemaSubentry is
not needed.
Has an OID been assigned to the LDAPsubentry object class?
On a related note, of what structural class should the rootDSE be?
Kurt