I have always wondered about directories that have included objectClass top
in every entry even though practically any usefull objectClass inherits
from top eventually.
Apparantly RFC2256 5.1 requests this:
The values of the objectClass attribute describe the kind of object
which an entry represents. The objectClass attribute is present in
every entry, with at least two values. One of the values is either
"top" or "alias".
( 184.108.40.206 NAME 'objectClass' EQUALITY objectIdentifierMatch
SYNTAX 220.127.116.11.4.1.1418.104.22.168.38 )
It seems RFC4512 addresses the matter in:
A.3. Changes to RFC 2256
This document incorporates Sections 5.1, 5.2, 7.1, and 7.2 of RFC
Section 5.1 of RFC 2256 provided the definition of the 'objectClass'
attribute type. This was integrated into Section 2.4.1 of this
document. The statement "One of the values is either 'top' or
'alias'" was replaced with statement that one of the values is
as entries belonging to 'alias' also belong to 'top'.
So this means objectClass top is still compulsory in every entry as in:
which means somehting like the following would be illegal:
Can anybody comment on the rationale why this is needed ?
I somehow completely fail to see the purpose.
Christian Kratzer CK Software GmbH
Email: ck(a)cksoft.de Wildberger Weg 24/2
Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden
Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart
Geschaeftsfuehrer: Christian Kratzer