[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
subschemasubentry attribute usage in rootDSE
Hello,
In reading RFC 2251 and RFC 2252, I have stumbled across a question regarding
the use of the subschemasubentry attribute type.
RFC 2251, in section 3.2.1, indicates that every entry mastered by a server will
have an attribute type included within it called subschemasubentry. This
attribute type's value will be a distinguished name that 'points to' the
subschema entry in the namespace that describes the schema for which the entry
conforms to. Quoting the RFC:
- subschemaSubentry: the Distinguished Name of the subschema entry
(or subentry) which controls the schema for this entry.
RFC 2252 in section 5.1.5, indicates that the subschemasubentry attribute type
is SINGLE-VALUE. Quoting the RFC:
5.1.5. subschemaSubentry
The value of this attribute is the name of a subschema entry (or
subentry if the server is based on X.500(93)) in which the server
makes available attributes specifying the schema.
( 2.5.18.10 NAME 'subschemaSubentry'
EQUALITY distinguishedNameMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 NO-USER-MODIFICATION
SINGLE-VALUE USAGE directoryOperation )
Later on in RFC 2251, Root DSE is described in section 3.4. In this section, it
seems that a slightly different use of subschemasubentry is described. Quoting
the RFC:
- subschemaSubentry: subschema entries (or subentries) known by this
server.
Now my question: The plurarlity in the sentence about subschemasubentry in the
Root DSEsection of RFC 2251 implies that this attribute type is multi-valued in
the Root DSE. Is this the intent? Is it the intent of the RFC that the
subschemasubentry attribute type be allowed to be multi-valued when contained in
the Root DSE, regardless of its definition as being SINGLE-VALUE as defined in
RFC 2252?
Thanks in advance for this clarification,
Tim Hahn
Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388 tie-line: 8/852.6388
fax: 607.752.3681