Flow statistics don't show up on the same flow id, if flow uses IPv6 match with subnet mask

When user installs the flows where it uses the ipv6 match as follows, it fails to store the flow statistics at the same flow id, because flow comparison fails for the destination match.

<match>
<ethernet-match>
<ethernet-type>
<type>34525</type>
</ethernet-type>
</ethernet-match>
<ipv6-source>FE80::2ACF:E9FF:FE21:6431/128</ipv6-source>
<ipv6-destination>AABB:1234:2ACF:0000:0000:0000:0000:5D99/64</ipv6-destination>
</match>

Comparison fails because switch actually returns the masked destination (AABB:1234:2ACF:0000:0000:0000:0000:0000/64). Ideally statistics manager should compare on the normalized ipv6 address and that will solve these issues.