A directory information tree (DIT) content rule defines which attributes an entry can contain. A rule can specify:
The SDX schema contains a number of auxiliary object classes that extend structural object classes. Some of the auxiliary object classes, such as SaeAuxClass and corbaObjectReference, are associated with a single structural object class; other auxiliary object classes are associated with many structural object classes. The auxiliary object classes attached to more than one structural object class are:
The X.500 standard (1993), defines four type of object classes. The SDX schema uses structural object classes, auxiliary object classes, and a small number of abstract object classes.
The auxiliary object class dlm1PhysicalElementLocationAuxClass can provide information about the location of a device to the following structural object classes:
Content rules 3 and 15 permit attachment of dlm1PhysicalElementLocationAuxClass.
The auxiliary object classes dlm1PhysicalElementLocationAuxClass and snmpInfoAuxClass can also be attached to the structural object class umcVirtualRouter. Content rule 2 specifies the association of virtual routers to specific service scopes, as well as the addition of SNMP information to virtual routers.
The SDX software lets you assign schedules to services. The scheduleAuxClass auxiliary object class provides time-based policy information. This auxiliary object class can be used in the following structural object classes:
Content rules 27 and 28 permit attachment of scheduleAuxClass.
You can store additional information for structural object classes through the auxiliary object class moreInformationAuxClass. This auxiliary object class can be used in the following structural object classes:
Content rules 3 and 4 permit the attachment of moreInformationAuxClass.
Policy parameters let you provide symbolic names in the place of literal values when you define policies. These symbolic names are bound to values at runtime before the policies are downloaded to the router. The parameter values are collected from different objects. Parameters are associated with the entries by attaching the auxiliary object class parameterAuxClass.
Parameters can be used in the following structural object classes through the auxiliary object class parameterAuxClass:
Content rules 1, 4, 6 –13, and 15 permit the attachment of the parameter attributes that are defined in parameterAuxClass.
Plug-ins are software programs that extend the capabilities of existing programs and make them more flexible. SDX plug-ins provide authentication, authorization, and tracking capabilities. The auxiliary object class pluginAuxClass provides a description of a plug-in. This auxiliary object class can be used in the following classes:
Content rules 2, 7, and 15 permit attachment of pluginAuxClass.
The object state manager (OSM) locks specific objects during transactions. To enable locking, the auxiliary object class transactionalObjectAuxClass is attached to all structural object classes that are inherited from the abstract object class umcServiceProfile. The following structural object classes can be associated with the auxiliary object class transactionalObjectAuxClass:
Content rules 10 through 16 permit attachment of transactionalObjectAuxClass.
The directory eventing system marks specified entries as deleted without deleting that object from the directory. The auxiliary object class umcDeletionAuxClass, which has a Boolean attribute deleted, can be attached to the following structural object classes:
Content rules 4, 6, 8, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 21, 22, and 28 permit attachment of umcDeletionAuxClass.
The SDX software attaches the auxiliary object class umcSubscriber to residential and enterprise subscribers to identify these objects as subscribers. The auxiliary object class is created when the subscriber is added to the directory. This class holds general information about the subscriber, such as contact and billing information.
The SDX software detects residential or enterprise subscribers by querying the directory with the key objectClass=umcSubscriber. The following structural object classes require the attachment of umcSubscriber:
Content rules 4, 10–13, and 15 permit attachment of umcSubscriber to these structural object classes.
Information about policy conditions and policy actions is stored in attributes that belong to structural object classes—policyRuleConditionAssociation for policy conditions and policyRuleActionAssociation for policy actions. The policyRule structural object class specifies the folder that contains policy rule structural objects.
Numerous auxiliary object classes extend these policy structural object classes. When attached to policyRuleConditionAssociation or policyRuleActionAssociation, the auxiliary object classes must also be attached to an associated policy rule structural object classes. Content rule 5
allows these kind of attachments.
Policies are organized in a specific type of folder. As a result, you can mark objects from type organization and organizationalUnit as a policyFolder object by attaching the appropriate auxiliary object class. See content rules 3 and 4.
Content rule 23 specifies that an auxiliary object class can be attached to a policyRuleActionAssociation structural object class, and content rule 24 specifies that an auxiliary object class can be attached to a policyRuleCondition. The policy rule association with conditions is used when the policy rule has more than one condition, and the policy rule association with actions is used when the policy rule has more than one action.