Classify tables and sessions contain relative node indexes:

hit_next_index, miss_next_index and opaque_index (in case it is a node).

Management agent like Honeycomb, needs to use node names instead (indexes might change after vpp restart).
Therefore node name <-> relative index conversion is needed.

For the conversion to be supported, management agent needs to know what is the base node for the classify table.

Possible solution:
add base_node_index to classify_table_info_reply and classify_add_del_table

Consequences:

• node that uses classify table is specified at table creation time and can't be changed
  (at least using binary API)
• sharing classify tables becomes impossible