cosine.schema missing attributes for 'domain' (ITS#955)

[jimd@dutton3.it.siu.edu]

Full_Name: Jim Dutton
Version: 2.0.7
OS: FreeBSD-4.1
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (131.230.6.142)


cosine.schema entry for 'domain' makes comments about organizationalUnit
and associatedName, but fails to define them. Since no superior
object contains these objects, new object with 'domain' and no
other objectclass which includes 'o' or 'associatedName' will fail
as shown below:

adding new entry "dc=siu,dc=edu,o=SIUC,c=US"
ldap_add: Object class violation
        additional info: attribute not allowed


Jan  9 16:27:12 <local4.debug> dutton3 slapd[38344]:
 Entry (dc=siu,dc=edu,o=SIUC,c=US), attr "o" not allowed
Jan  9 16:27:12 <local4.debug> dutton3 slapd[38344]:
 conn=0 op=5 RESULT tag=105
 err=65 text=attribute not allowed
Jan  9 16:27:12 <local4.debug> dutton3 slapd[38344]:
 conn=0 op=6 UNBIND
Jan  9 16:27:12 <local4.debug> dutton3 slapd[38344]:
 conn=-1 fd=9 closed
class_violation_error: new file: 34 lines, 1933 characters.


cosine.schema 'domain' entry:
# 8.3.7.  Domain
#
#  The Domain object class is used to define entries which represent DNS
#  or NRS domains.  The domainComponent attribute should be used for
#  naming entries of this object class.  The usage of this object class
#  is described in more detail in [3].
#
#    domain OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            domainComponent}
#        MAY CONTAIN {
#            associatedName,
#            organizationName,
#            organizationalAttributeSet}
#    ::= {pilotObjectClass 13}
#
## from RFC 2247, we presume that organizationalAttributeSet
## should be expanded as below.
objectclass ( 0.9.2342.19200300.100.4.13 NAME 'domain'
        SUP top STRUCTURAL
        MUST domainComponent
        MAY ( userPassword $ searchGuide $ seeAlso $
                businessCategory $ x121Address $ registeredAddress $
                destinationIndicator $ preferredDeliveryMethod $
                telexNumber $ teletexTerminalIdentifier $  
                telephoneNumber $ internationaliSDNNumber $
                facsimileTelephoneNumber $ street $ postOfficeBox $
                postalCode $ postalAddress $
                physicalDeliveryOfficeName $
                stateOrProvinceName $ localityName $ description )
        )


Actual RFC2247 'domain' entry:
5.2. The domain object class

   If the entry does not correspond to an organization, organizational
   unit or other type of object for which an object class has been
   defined, then the "domain" object class can be used.  The "domain"
   object class requires that the "DC" attribute be present, and permits
   several other attributes to be present in the entry.

   The entry will have as its structural object class the "domain"
   object class.

( 0.9.2342.19200300.100.4.13 NAME 'domain' SUP top STRUCTURAL
 MUST dc
 MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $
 x121Address $ registeredAddress $ destinationIndicator $
 preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $
 telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $
 street $ postOfficeBox $ postalCode $ postalAddress $
 physicalDeliveryOfficeName $ st $ l $ description $ o $
 associatedName ) )