tIPv6FilterScope

This textual convention determines some aspects of an item's behavior
regarding creation and use, unused entry garbage collection, and
automated promulgation by Element Management System to other systems
in the service domain.
          
TFilterScope is an extension of the textual convention TItemScope.
          
exclusive:
          
   When the scope of an item is defined as exclusive, the item can
   only be applied once, for example to a single SAP.  Attempting
   to assign the policy to a second SAP is not allowed and will
   result in an error.  If the item is removed from the exclusive
   SAP, it will become available for assignment to another
   exclusive SAP.
          
   A non-applied exclusive scope policy is a candidate to be removed
   from the system by a TBD garbage collection command.
          
   The system default policies cannot be put into the exclusive scope.
   An error will be generated if scope exclusive is executed in
   any policies with a policy-id equal to 1.
          
template:
          
   When the scope of an item is defined as template, the item can be
   applied any number of times.  Policies with template scope
   will not be considered for deletion by a TBD garbage collection
   command; all items of scope 'template' must be deleted explicitly.
          
   The system default policies will always be scope template.
   An error will occur if a policy-id 1 is attempted to be
   set to scope exclusive.
          
embedded:
          
   When the scope of a filter is defined as embedded, this indicates
   that the filter may be embedded in other non-embedded filters.
   An embedded filter may not be applied anywhere in the system.
   Attempting to set scope to embedded for a filter which is
   already applied will be rejected by the system.
          
system:
          
   When the scope of a filter policy is defined as system, the filter
   policy can be used as a common system filter policy only.
          
   The policy cannot be applied directly anywhere in the system.
   In order to activate the policy it must be configured as the active
   system filter policy in tFilterSystemFilterTable.
          
   All other 'exclusive' and 'template' IP / IPv6 filter policies may
   be chained to the active system policy by setting the
   tIPFilterChainToSystemFilter or tIPv6FilterChainToSystemFilter
   object to 'true(1)'.
          
   When an IP / IPv6 filter policy is chained to the system filter
   policy, system filter policy's rules are executed first before
   any rules of the activating filter policy are executed.
          
   The scope of a filter policy can be set to/from this value only
   when the policy does not contain any entry.
          
cpm:
          
   When the scope of a filter is defined as cpm, this indicates
   that the filter can be used as cpm filter only.
          
   Cpm filter cannot be applied directly anywhere in the system.
   In order to activate the cpm-filter it must be configured as the active
   cpm filter policy in tmnxCpmHwFilterObjs.