Logging inconsistency between dhcp4.packets and dhcp6.packets

This log for DHCPv4:

[kea-dhcp4.packets/2921701.140031672309504] DHCP4_QUERY_DATA [hwtype=1 00:00:00:ff:ff:ff], cid=[00:00:00:00:ff:ff:ff:ff:ff:ff:ff], tid=0x8eabb73f, packet details: local_address=1.2.3.4:67, remote_address=1.2.3.5:68, msg_type=DHCPREQUEST (3), transid=0x8eabb73f,

contains the msg_type while the DHCPv6 counterpart does not:

[kea-dhcp6.packets/3264085.139762203666176] DHCP6_QUERY_DATA duid=[00:00:00:00:ff:ff:ff:ff:ff:ff:ff], tid=0x5f541f, packet details: localAddr=[1:1:1:1::1]:0 remoteAddr=[2:2:2:2::2]:547

Similar inconsistency in these two log messages:

[kea-dhcp4.packets/2921701.140031535531776] DHCP4_RESPONSE_DATA [hwtype=1 00:00:00:ff:ff:ff], cid=[00:00:00:00:ff:ff:ff:ff:ff:ff:ff], tid=0xfe456e5f: responding with packet DHCPACK (type 5), packet details: local_address=1.2.3.4:67, remote_address=1.2.3.5:68, msg_type=DHCPACK (5), transid=0xfe456e5f,

and

[kea-dhcp6.packets/3264085.139762070353664] DHCP6_RESPONSE_DATA responding with packet type 7 data is localAddr=[1:1:1:1::1]:547 remoteAddr=[2:2:2:2::2]:547

Perhaps this is this way for a reason? There are, of course, differences between DHCPv4 and DHCPv6.

SF1375