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

Re: RFC2251: RootDSE subschemasubentry issue



Greetings,

I believe that this was discussed on the mailing list about 6 months ago.
At that time, the general direction seemed to be that  the rootDSE entry
would contain an additional attribute:

subschemasubentries

which would be defined to have distinguishedName syntax.  And while this
does not provide the detailed mapping (offered in Kurt's response), of
associating namingContext values with subschemasubentries values, it also
does not introduce another attribute value format that needs to be parsed.
The X.500 specifications give some guidance on the placement of
subschemasubentry values, namely they are to be placed "just below" the
namingContext and should have object class: top, subentry,
subschemasubentry.

So, I would add a fourth option for the rootDSE:

namingContexts: ou=Sales, o=Widgets
namingContexts: ou=Development, o=Widgets
subschemasubentries: cn=schema, ou=Sales, o=Widgets
subschemasubentries: cn=schema, ou=Development, o=Widgets

Regards,
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