Policy-Driven Routing Management Using CIM - Computer Network Security - page 263

- Every CIM class generates a new XML element.
- Every CIM generalization (inheritance) generates the declaration of a new
XML extension element.
- Every CIM key property generates a new XML <key> (or <unique>) element,
which allows the unique identification of each XML element (i.e., CIM
instance).
- Every CIM association is expressed in XML as entry references; this is the
most suitable general-purpose mechanism currently available.
- A single XML database will host no more than one CIM implementation, and
therefore the namespace is the same for all CIM instances stored in this
database.
An example of the output of the mapping for a routing policy is presented in
section 5.

4 Policy-Driven Routing Management System

We propose a policy-based routing management as depicted in Figure 3. This
architecture was designed as an evolution of the IETF approach to policies, but
providing some new features, as the complete use of XML-related technologies and
tools in the policy life cycle.

Border Router CIM-based Route Server Policy Repository

Distributio n Access

PDP

PEP

Notification and
monitoring

Access

PMT

Definition

Policy
Console

Fig. 3. CIM modeling levels

This architecture is composed by these four main functional elements:
- Policy Management Tool (PMT) that allows the administrator to develop
routing policies making use of the Policy Console.
- Policy Repository that is used by the management tool (PMT) to store the
policies and by the decision points (PDPs) to get them. The IETF suggests the
use of a Lightweight Directory Access Protocol (LDAP). Due to our proposal