In FDP-440 the client scenario relies on asymmetric traffic (ICMP echo request from vm4 is going through vm3 while the ICMP echo reply from vm1 is going through vm2). This is currently not supported by OVN. The ICMP echo reply is marked as ct.inv since it is entering from a different OVN port with respect to the one used by the ICMP echo request to reach the destination (so the ICMP request/reply refers to different CT zones). This RFE intends to investigate the possibility to let OVN understand the traffic has been already committed to CT even it is entering/egressing to different OVN ports so it should not be dropped