This MIB module defines objects that manages flow cloning
feature. A flow cloning can be described as a hardware or 
software entity, that is responsible to clone (or duplicate)
flows to the specified destination port in the device. These
cloned packets will be sent to an external device for a more
fine-grained analysis of the flows. A typical application of
this MIB module will facilitate cloning media flows. However,
by no means does the definition of this MIB module prevents 
other applications from using it.
        
CLONE PROFILE:
==============                 
At the top level, this MIB module describes the notion of flow
cloning. Further descriptive texts in this MIB will use clone
profile to describe flow cloning. We can think of clone profile
as a container for the traffic flows for which it will clone
packets and send out on the specified egress interface. Because
a device can support more than one clone profile, this MIB
defines cfcCloneProfileTable.
        
TRAFFIC FLOW:
=============
At the next level, this MIB module describes the notion of a
traffic flow associated with the clone profile. A traffic flow
is a unidirectional stream of packets conforming to a
classifier.For example, packets having a particular source
IP address, destination IP address, protocol type, source port
number, and destination port number.
        
CLONE TARGET:
=============
A clone target may represent an entity that the system
provisions with a clone profile.
        
Clone targets include, but are not necessarily limited to, the
system, nodes (i.e., an instance of an operating system),
interfaces, VRF instances, and bridge domains.
        
IMPLEMENTATION GUIDANCE
=======================
It might seem that the concepts presented by this MIB module
lend themselves to a profile-based approach. However, this 
approach provides the most general abstraction and lends itself
to implementations that can fall under two categories: global 
and per-interface.
        
A global level clone profile will clone the specified flows
that are monitored in the whole device. Per interface clone
profile will clone the specified flows that are monitored on
the specified interface.
        
This MIB module can represent the global level clone profile
using the following procedure:
        
o Create a row in the cfcCloneProfileTable having the following
  attributes. Allocate a value for cfcCloneProfileId and a name
  for cfcCloneProfileName. For sake of discussion, let's say 
  the value is <X> and the name is 'XYZ'.
        
  cfcCloneProfileId       = <X>
  cfcCloneProfileName     = <XYZ>
  .
  .
  cfcCloneTargetType      = 'system'
        
o Similarly per interface level clone profile implementation
  can be represented as follows. 
        
  Create a row in the cfcCloneProfileTable having the following
  attributes. Allocate a value for cfcCloneProfileId and a name
  for cfcCloneProfileName. For sake of discussion, let's say
  the value is <Y> and the name is 'ABC'.  
        
  cfcCloneProfileId         = <Y>
  cfcCloneProfileName       = <ABC>
  .
  .
  cfcCloneTargetType        = 'interface'
  cfcCloneTargetIfIndex     = <ifindex>
        
While this example illustrates how an implementation may
represent global and per-interface configuration data, it is
understood that an implementation may have other requirements.
In these cases, use this example as a guide in satisfying these
requirements.