Miscellaneous Object Classes

The following object classes are used to create directory entries that create the DIT. The are:

country

organization

domainRelatedObject

organizationalUnit

domain

labeledURIObject

The country object class may be used to create the root suffix entry of the primary DIT. If the primary tree has a single component suffix, that suffix is comprised of the top and country object classes. The object class is defined as follows:

( OID - TBD 

NAME 'country' 

MUST ( 

	countryName $ objectClass 

) 

MAY ( 

	description $ searchGuide 

	)

)

organization Object Class

The organization object class may be used to create the root suffix entry of the primary DIT. If the primary suffix has two components, that suffix is comprised of the top, organization and domainRelatedObject object classes. If the primary tree has single component suffix (e.g. c=us) then the second level nodes in the tree are created from top, organization and domainRelatedObject object classes. The object class is defined as follows:

( OID - TBD 

NAME 'organization' 

MUST ( 

	organizationName $ objectClass 

) 

MAY ( 

	businessCategory $ description $ destinationIndicator $ 

	facsimileTelephoneNumber $ internationaliSDNNumber $ 

	locality $ physicalDeliveryOfficeName $ postOfficeBox $     

	postalAddress $ postalCode $ preferredDeliveryMethod $      

	registeredAddress $ searchGuide $ seeAlso $ state $      

	streetAddress $ telephoneNumber $     

	teletexTerminalIdentifier $ telexNumber $ userPassword $     

	x121Address 

	)

)

domainRelatedObject Object Class

The domainRelatedObject object class may be used to create the root suffix entry of the primary DIT. If the primary suffix has two components, that suffix is comprised of the top, organization and domainRelatedObject object classes. If the primary tree has single component suffix (e.g. c=us) then the second level nodes in the tree are created from top, organization and domainRelatedObject object classes. The object class is defined as follows:

( OID - TBD 

NAME 'domainRelatedObject' 

MUST ( 

associatedDomain $ objectClass 

) 

MAY ( 

	)

)

organizationalUnit Object Class

The organizationalUnit object class is used to create the container entries of the primary DIT. These entries are the organizational unit containers corresponding to an OSI tree based on geography (east, west, UK, Russia, etc), functional units (engineering, marketing, etc). The OU entry is created by using top and organizationalUnit object classes. Each one of these organization units is required to have three more OU entries people, groups, and services. The object class is defined as follows:

( OID - TBD 

NAME 'organizationalUnit' 

MUST ( 

	objectClass $ organizationalUnitName 

	) 

MAY ( 

	businessCategory $ description $ destinationIndicator 

	$ facsimileTelephoneNumber $ internationaliSDNNumber $ 

	locality $ physicalDeliveryOfficeName $ postOfficeBox $     

	postalAddress $ postalCode $ preferredDeliveryMethod $      

	registeredAddress $ searchGuide $ seeAlso $ state $      

	streetAddress $ telephoneNumber $     teletexTerminalIdentifier $ 

	telexNumber $ userPassword $     x121Address 

	)

)

domain Object Class

The domain object class is used to create the container entries of the secondary DIT. These entries are the domain component containers corresponding to a DNS suffix. The DC entry is created by using top, domain and labeledURIObject object classes. The object class is defined as follows:

( OID - TBD 

NAME 'domain' 

MUST ( 

	dc $ objectClass 

	) 

MAY ( 

	associatedName $ businessCategory $ description $ 

	destinationIndicator $ facsimileTelephoneNumber $ 

	internationaliSDNNumber $ locality $ organizationName $ 

	physicalDeliveryOfficeName $ postOfficeBox $ postalAddress $ 

	postalCode $ preferredDeliveryMethod $ registeredAddress $ 

	searchGuide $ seeAlso $ state $ streetAddress $ 

	telephoneNumber $ teletexTerminalIdentifier $ telexNumber $ 

	userPassword $ x121Address 

	)

)

labeledURIObject Object Class

The labeledURIObject object class is used to create the container entries of the secondary DIT. These entries are the domain component containers corresponding to a DNS suffix. The DC entry is created by using top, domain and labeledURIObject object classes. The object class is defined as follows:

( OID - TBD 

NAME 'labeledURIObject' 

MUST ( 

	objectClass 

	) 

MAY ( 

	labeledURI 

	)

)