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

Re: objectclass of a subschemasubentry



Kurt:

The subschema object class remains auxiliary. RFC 2252 should include
the subentry object class. Entries for the subschema would include the
object identifier for both the subschema object class and the subentry
object class.

Ella

"Kurt D. Zeilenga" wrote:
> 
> At 02:22 PM 8/10/99 -0400, Ella Paton Bassett wrote:
> 
> >>From X.501:
> >13.2.1 The Subentry object class
> >The subentry object class is a structural object class and is defined as
> >follows:
> >subentry OBJECT-CLASS ::= {
> >       SUBCLASS OF             { top }
> >       KIND                    structural
> >       MUST CONTAIN    { commonName | subtreeSpecification }
> >       ID                              id-sc-subentry }
> >
> 
> I take it that's it's your opinion that RFC2252 then is in error
> and that the subschema object class should be STRUCTURAL.   Do
> others agree with this?