Subentries in the Lightweight Directory Access Protocol (LDAP)

Lightweight Directory Access Protocol (LDAP): Directory Information Models

“…Subentries are used in Directory to hold for administrative and operational purposes as defined in [X.501]. Their use in LDAP is detailed in [RFC3672].…”

“…The term "(sub)entry" in this specification indicates that servers implementing X.500(93) models are, in accordance with X.500(93) as described in [RFC3672], to use a subentry and that other servers are to use an object entry belonging to the appropriate auxiliary class normally used with the subentry (e.g., 'subschema' for subschema subentries) to mimic the subentry. This object entry's RDN SHALL be formed from a value of the 'cn' (commonName) attribute [RFC4519] (as all subentries are named with 'cn').…”

“…If so, they MUST do so in accordance with [RFC3672]. Servers that do not support subentries SHOULD use object entries to mimic subentries as detailed in Section 3.2.…”

The Lightweight Directory Access Protocol (LDAP) Content Synchronization Operation

“…The Subentries Control is used with the search operation "to control the visibility of entries and subentries which are within scope" [RFC3672]. When used with the Sync Operation, the subentries control and other factors (search scope, filter, etc.)…”

Collective Attributes in the Lightweight Directory Access Protocol (LDAP)

“…An entry collection consists of all entries within scope of a collective attributes subentry [RFC3672]. An entry can belong to several entry collections.…”