push vlan rules in table=220 are creating a different vlan header than the incoming one

When working with a vlan provider external network, those are the rules which are created

In table 0, we pop the vlan=805:
cookie=0x8000000, duration=9604.760s, table=0, n_packets=152, n_bytes=10102, priority=10,in_port=1,dl_vlan=805 actions=pop_vlan,write_metadata:0x130000000001/0xffffff0000000001,goto_table:17

In table 220, when we output to the external gateway, we set the same VID but with an extra DEI/CFI bit (bit 13):
cookie=0x8000007, duration=9604.716s, table=220, n_packets=50, n_bytes=2430, priority=7,reg6=0x1300 actions=push_vlan:0x8100,set_field:4901->vlan_vid,output:1

Seems to be originated in the openflowplugin code which is used in netvirt:
In FlowConvertor.injectPushActionToInstruction()

pushVlanActionBuilder.setCfi(new VlanCfi(1))
.setVlanId(setVlanIdActionCase.getSetVlanIdAction().getVlanId())
.setEthernetType(PUSH_VLAN)
.setTag(PUSH_VLAN);
pushVlanActionCaseBuilder.setPushVlanAction(pushVlanActionBuilder.build());