engine-id

Engine ID— A unique identifier for the engine that determined the Selector ID.

The Classification Engine ID defines the context for the Selector ID. The Engine ID is the first eight bits that provide information about the engine that classifies the flow. IANA-L4, CANA-L3, and so on, are some of the engines that can be classified using an engine ID. Note that the Engine ID does not represent the NBAR2 mechanism used to classify the application.

For more information about the engine IDs, see the information available
here: http://tools.ietf.org/html/rfc6759 as also
here: https://tools.ietf.org/html/draft-claise-export-application-info-in-ipfix-03

0 Invalid or reserved.
IANA-L3 1 The IANA protocol (layer 3) number is exported in the Selector ID.
See http://www.iana.org/assignments/protocol-numbers/
CANA-L3 2 Cisco proprietary layer 3 definition. Cisco can still export our own layer 3 protocol numbers, while waiting for IANA to assign it. The Selector ID has got a global significance for all Cisco devices under CANA governance. Hopefully the same IDs will be maintained after the IANA standardization.
IANA-L4 3 IANA layer 4 well-known port number is exported in the application ID. See http://www.iana.org/assignments/port-numbers. Note: as a flow is unidirectional, it contains the destination port in a flow from the client to the server.
CANA-L4 4 Cisco proprietary layer 4 definition. Cisco can still export our own layer 4 port number, while waiting for IANA to assign it. The Selector ID has got a global significance for all Cisco devices under CANA governance. Hopefully the same ID will be maintained after the IANA standardization. Example: IPFIX had the port 4739 pre-assigned in the IETF draft for years. While waiting for the IANA registration, we could use this Selector ID.
NBAR-STANDARD 5 The Selector ID represents the NBAR unique application Id. The Selector ID has got a global significance for all Cisco devices that uses NBAR. This unique Selector ID is equivalent to the NBAR protocol discovery MIB index. THIS ONE WILL TRANSITION TO AN INTERNAL APP ID, SPECIFIC TO THE NBAR IMPLEMENTATION
NBAR-CUSTOM 6 The selector ID represents the NBAR unique custom application Id. The Selector ID has a local significance per Cisco device. The Selector ID is equivalent to the NBAR protocol discovery MIB index.
MIME 7 The MIME type string is exported in the Selector ID.
Note: the MIME type allows the definition of non standardized types, called vendor specific, with a format such as vnd.xxx.
See http://tools.ietf.org/html/rfc2048#section-2.1.2 for reference.
Therefore, there is no point of assigning a classification engine value for Cisco proprietary MIME types.
The selector ID represents a class ID specified by the PSAMP Selection Sequence ID.
PSAMP 8 From the PSAMP protocol specification, the Selection Sequence is specified as:
From all the packets observed at an Observation Point, only a few packets are selected by one or more Selectors.  The Selection Sequence is a unique value per Observation Domain describing the Observation Point and the Selector IDs through which the packets are selected.
The Selector ID has a local significance per router.
MQC-CLASS-ID 9 The selector ID represents the MQC class ID. The Selector ID has a local significance per router. In this case, Selector ID has a local significance per router and the Selector Id value has got the corresponding cbQoSConfigIndex value from the CB-QoS-MIB
SML-STANDARD 10 The selector ID represents the SML unique application Id. The Selector ID has got a global significance for all Cisco devices that uses the SML DPI engine.
SML-CUSTOM 11 The Selector ID represents the SML unique custom application Id.  The Selector ID has a local significance per Cisco device.
CANA-L2 12 The Selector ID represents the layer 2 applications. The Selector ID has a global significance. This regsitry is mainly for the layer2 CISCO-SNAP but we can’t exclude something else!
CANA-L7 13 The Selector ID represents the Cisco unique global application Id. The Selector ID has got a global significance for all Cisco devices
WAAS 14 The Selector ID represents the NAM unique custom application Id. In this case, Selector ID has a local significance per Cisco device IMPORTANT NOTE: application police must try to standardize using this classification engine id
WAAS-CLASS-ID 15 The Selector ID represents the WAAS unique class Id, which is called the WAAS Classifier. In this case, Selector ID has a local significance per Cisco device.
Contact: Mohamed Hassan, Rajiv Raghunarayan
NAM-CLASS-ID 16 The Selector ID represents the NAM unique custom application Id
In this case, Selector ID has a local significance per Cisco device.
Contact: Patrick Wildi
PFR-CLASS-ID 17 The Selector ID represents the PfR unique Traffic Class.
In this case, Selector ID has a local significance per Cisco device (per Border Router).  Note that the Selector ID has got some more structure: see EDCS-909561 for the details.
Contact: Pritam Shah & Yoshiyuki Tsuda
ETHERTYPE 18 The Selector ID represents the well-knonw L2 Ethertype. See http://standards.ieee.org/develop/regauth/ethertype/eth.txt and http://www.iana.org/assignments/ethernet-numbers . Note that the Ethertype is usually expressed in hexa, however the corresponding integer value is used in Selector id. Note2: Ethertype starts at 0x0600, i.e. 1536 integer
Contact: Patrick Wildi & Benoit Claise
LLC 19 The Selector ID represents the well-knonw LLC based applications. See http://standards.ieee.org/develop/regauth/llc/public.html. Note that the Ethertype is usually expressed in hexa, however the corresponding integer value is used in Selector id
Contact: Patrick Wildi & Benoit Claise
PANA-L7-PEN 20 Proprietary layer 7 definition; See RFC 6759
CISCO-PPDK-LOCAL 21 For use by the Protocol Pack development Kit for user defined Ids
255 The classification engine ID 255 is the maximum engine ID.