ISG introduces support for two basic policy types:
Traffic policies define the handling of data packets and consist of a traffic class, which defines the packet-based criteria
for which the policy is applicable, and one or more traffic actions, which are functional instances that perform specific
operations on a data stream and are often referred to as features
. The traffic actions configured within a traffic policy are invoked for data packets that meet the criteria defined by the
Network-forwarding policies are a specific type of traffic policy, for which the action is a network-forwarding action, such
as to route packets using a specific virtual routing and forwarding instance (VRF) or to forward packets over a Layer 2 connection.
Network-forwarding policies are “classless” in that it is not possible to refine the criteria for which the forwarding action
Control policies define the handling of system events and consist of one or more control policy rules and a decision strategy
that governs how the constituent policy rules are evaluated. A control policy rule consists of a control class (a flexible
condition clause), an event for which the condition is evaluated, and one or more control actions. Control actions are general
system functions, such as “authenticate” or “activate a service.”
Control policies may be activated on various targets, such as interfaces or ATM virtual circuits (VCs), and typically control
the extraction and authentication of subscriber identity and the activation of services on sessions. Traffic policies may
be activated only on sessions and are typically (though not always) applied through service activation.
Control policies are a structured replacement for feature-specific configuration commands and allow configurable functionality
to be expressed in terms of an event, a condition, and an action. Control policies represent an intuitive and extensible framework
for specifying system behavior. As additional functionality is added to the system, an administrator just has to learn what
new events and actions can be included in a control policy, not a completely new set of configuration commands.