[Date Prev][Date Next] [Chronological] [Thread] [Top]

RFC2251: RootDSE subschemasubentry issue

As previously noted <8525679B.003DD02B.00@D51MTA04.pok.ibm.com>,
RFC 2251 states subschemaSubentry attribute type within the
Root DSE may contain multiple values though the attribute type
is single valued.

I do not believe it necessary to provide a mechanism to allow
clients to obtain a complete list of subschema entries (or
subentries) known to this server.  This list could be quite
large and, IMO, rather useless.  Applications need to known
which subschema controls which entries.

I suggest that applications obtain the DN of the subschema entry
(subentry) from either the entry(ies) they intend to access or
from the entry at the root of the naming context. 

To resolve this issue, I suggest:

RFC 2251, 3.4 "--subsubschemaSubentry" subsection be removed
and that a note be added to the end of the section:

  Note: the subsubschemaSubentry attribute type, if
  present, contains the Distinguished Name of the
  subschema entry (or subentry) which controls the
  schema for the Root DSE.

Comments?

	Kurt