MD-SAL app cannot create a flow entry which adds a VLAN tag with the specified VLAN ID into untagged frame.

MD-SAL applications cannot correctly create a flow entry which adds a VLAN tag with the specified VLAN ID into untagged ethernet frame.
I mean that there is no MD-SAL action which is translated by the MD-SAL OF plugin into the above semantic for both OF 1.0 and OF 1.3.

If a MD-SAL application uses set-vlan-id-action, the MD-SAL OF plugin translates it into SET_VLAN_ID action for OF 1.0 switch (this is OK), and translates it SET_FIELD(VLAN_VID) action for OF 1.3 switch (this is NG).
It means that the MD-SAL application successfully create a flow entry into OF 1.0 switches as intended, but MD-SAL application fails on OF 1.3 switches.

(Please note that OF 1.3 flow entry that adds a VLAN tag with the specified VLAN ID into untagged ethernet frame needs to contain PUSH_VLAN action before SET_FIELD(VLAN_VID) action.)

I pointed out this issue in the mail on openflowplugin-dev ML.
https://lists.opendaylight.org/pipermail/openflowplugin-dev/2014-July/001617.html

Consequently VTN Manager does not work correctly with OF 1.3 switches.
It fails to install a flow entry that adds a VLAN tag with the specified VLAN ID into untagged ethernet frame.
(Please note that VTN Manager is a AD-SAL application, but it indirectly uses the MD-SAL OF plugin via sal-compaitbility. So VTN Manager is an indirect MD-SAL application)

VTN project requests that this issue is fixed by Milestone 5 of Helium release.