Forward Open Forwarding and Config Assembly Data

It is not clear how Forward Open Forwarding and Config Assembly Data go together. At least the documentation at this point is insufficient, maybe the software is buggy.

In an ExtendedConfig Scenario with config assemblies, configuration data is appended to the connection path. If FwOpen-Forwarding is not used, then this works with a connection path (ExtendedConfigExample) like 200424662C642C6580040000000000000000.

If FwOpen-Forwarding is enabled, then this same connection path leads to a refused FwOpen with code "Path destination unknown". Instead, if no configuration data is appended to the connection path, then the connection can be established.

Is the forward-open-forward-handler responsible for interpreting the config data? This would be the only meaningful explanation. Documentation also doesn't give such a hint. This is a strong indicator for a bug in these scenarios.

Also: Document which packets must be handled if the forward open forwarding is enabled by means of the corresponding parameter: EIP_OBJECT_LFWD_OPEN_FWD_IND, EIP_OBJECT_FWD_CLOSE_FWD_IND, EIP_OBJECT_FWD_OPEN_FWD_COMPLETION_IND, ... That is mandatory! Does not become clear from the current manual.