[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Policy Components

The policy management architecture is fully compliant with Internet Engineering Task Force (IETF) policy management standards. The SRC policy management system uses a distributed architecture with the following components:

Figure 11 shows the components of the policy management system. As shown:

  1. Policy Editor is used to create policies and maintain policy data in the policy repository.
  2. The policy repository distributes policy data to policy engines that are located on SAEs throughout the network.
  3. The policy engine uses the policy data to instruct the policy enforcement points to apply appropriate policies to subscriber traffic in the network.

Figure 11: Policy Management Components

Policy Editor

Policy Editor is the application that you use to define policies. It dynamically changes the panes that it provides to you, based on your input. It can show or hide policy object attributes as you interact with it. For example, when you choose the TCP or UDP protocols, the source and destination ports are shown; otherwise, they are not shown.

Policy Editor also allows you to store policy data in a directory server or in files. By storing data in files, you can create a backup of the repository or transfer policies from one repository to another.

See Chapter 7, Using Policy Editor.

Policy Engine

The policy engine acts as a policy decision point (PDP) and is responsible for making decisions about the deployment of policies on the router or the CMTS device. The policy engine runs as part of the SAE.

Policy Repository

The policy repository is a directory that stores policies and distributes policies to policy engines.

Policy Enforcement Point

The policy enforcement point is the policy management component of the router that is responsible for enforcing the deployed policies. In cable networks, the policy enforcement point is the CMTS device.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]