Content Rules

A DIT content rule is a comprehensive way of defining precisely what attributes can be in an entry, without having to either register new object class definitions and their associated object identifiers, or let anarchy reign through the unregistered object class mechanism.

A DIT content rule specifies the following entries of a particular structural object class:

• Additional mandatory attributes that the entries must contain
• Additional optional attributes that the entry may contain
• Set of additional auxiliary object classes that these entries can be members of
• Any optional attributes from the structural and auxiliary object class definitions that the entries must not contain

A DIT content rule is the overriding subschema element that actually controls which attributes can appear in an entry.

In the sections the purpose of attaching auxiliary classes to structural object classes is explained.

The SDX component detects any kind of subscribers (that is, residential and enterprise) by querying the directory against the key objectClass=umcSubscriber. The objects from the types umcUser, umcEnterprise, umcSite, and umcAccessServiceProfile must include umcSubscriber as an additional objectClass value. This is done by attaching the auxiliary class umcSubscriber to those objects. The DIT content rules Cr10 to Cr13 allow this attachment.

With the introduction of policy parameterization, the operator has the ability to provide symbolic names in place of literal values when defining policies. These symbolic names are bound to values at run time before the policies are downloaded to the router. The parameter values are collected from different objects. These objects are actual entries in the directory where the parameters get associated with the entries by attaching the auxiliary class parameterAuxClass. The following are the type of objects where parameters can be used: dlm1Chassis, policyGroup, sspService, sspServiceProfile, locality, umcUser, umcSite, umcEnterprise, and umcAccessServiceProfile. The DIT content rules Cr1 and Cr6 through Cr13 permit the attachment of the parameter attributes that are defined in the class parameterAuxClass.

The SDX component DES marks entries from special types as deleted without actually deleting that object, should any DES client perform a deletion operation. The auxiliary class umcDeletionAuxClass with its Boolean attribute deleted is available for the object classes organizationalUnit, policyGroup, sspServiceProfile, umcUser, umcSite, umcEnterprise, umcAccessServiceProfile, umcRadiusPerson, umcRetailer, umcGlobalParameter, umcComponent, umcTrap and umcUrl. The DIT content rules Cr4, Cr6, Cr8, Cr10, Cr11, Cr12, Cr13, Cr14, Cr15, Cr17, Cr18, Cr19, and Cr20 permit the attachment of the auxiliary class umcDeletionAuxClass.

The OSM locks specific objects during transactions. This is accomplished by attaching the auxiliary object class transactionalObjectAuxClass to all classes inherited from the abstract class umcServiceProfile. All classes can be associated with the auxiliary object class umcSubscriber and umcRetailer objects. The DIT content rules Cr10 through Cr16 allow this kind of operation.

Information about policy conditions and policy actions is stored in attributes that belong to auxiliary classes that represent the supported actions and conditions. The auxiliary classes must be attached to policy rules. The DIT content rule Cr5 allows these kind of attachments. Policies are organized in a specific kind of folder. As a result, objects from type organization and organizationalUnit can be marked as a policyFolder object by attaching the appropriate auxiliary class. See Cr3 and Cr4.

Operators might like to store additional information not provided by the classes organization and organizationalUnit in those types of entries. This is accomplished by attaching the auxiliary class moreInformationAuxClass, which is permitted by Cr3 and Cr4.

DIT content rule Cr2 allows adding SNMP information to virtual routers, as well as associating virtual routers with specific service scopes, by attaching the auxiliary classes dlm1PhysicalElementLocationAuxClass and snmpInfoAuxClass to the structural class umcVirtualRouter.

Interface classifications are attached to objects representing router devices. Cr1 allows attaching the class umcClassificationProfile to dlm1Chassis in addition to the previously mentioned attachment of parameter classes.

Content Rules Table

A table of content rules is provided in HTML format. This hyperlinked table is located in the subdirectory contentRules located on your SDX software CD in the directory folder SDK/doc/ldap. The table provides the content rule ID, the content rule for structural object class, the auxiliary class, and a description of each content rule.