What format DUID accept ROS DHCPv6 server? Tested with version 5.14 and 5.9

I have CPE with wide-dhcp6 client, DUID file content is 00:03:00:06:00:27:22:39:E5:B7 (DUID Based on Link-layer Address [DUID-LL]). But ROS isn't working:

echo: dhcp,debug,packet recv server1 fe80::227:22ff:fe39:e5b7 -> ff02::1:2
echo: dhcp,debug,packet solicit
echo: dhcp,debug,packet transaction-id: f0fbfa
echo: dhcp,debug,packet -> clientid: 000600
echo: dhcp,debug,packet -> elapsed_time: 386
echo: dhcp,debug,packet -> ia_pd:
echo: dhcp,debug,packet t1: 0
echo: dhcp,debug,packet t2: 0
echo: dhcp,debug,packet id: 0x0
echo: dhcp,debug bad client DUID

If duid file content is only 00:06:00:27:22:39:E5:B7, ROS debug message:

echo: dhcp,debug,packet recv server1 fe80::227:22ff:fe39:e5b7 -> ff02::1:2
echo: dhcp,debug,packet solicit
echo: dhcp,debug,packet transaction-id: 28a7ad
echo: dhcp,debug,packet -> clientid: 00272239 e5b7
echo: dhcp,debug,packet -> elapsed_time: 0
echo: dhcp,debug,packet -> ia_pd:
echo: dhcp,debug,packet t1: 0
echo: dhcp,debug,packet t2: 0
echo: dhcp,debug,packet id: 0x0
echo: dhcp,debug bad client DUID

Thanks.

On dhcp client you can see what DUID it has generated.

I know, what DUID client generate. I wrote it in this thread. My question is about SERVER.

From RFC 3315:

Clients and servers MUST treat DUIDs as opaque values and MUST only
compare DUIDs for equality. Clients and servers MUST NOT in any
other way interpret DUIDs. Clients and servers MUST NOT restrict
DUIDs to the types defined in this document, as additional DUID types
may be defined in the future.

But if I have DUID with 4 bytes DUID TYPE and HARDWARE TYPE, in mikrotik DHCPv6 server I see only last 6 bytes of duid. It's wrong.

And as first (and last) clause of RFC3315 citation: dhcp server must accept ANY format. So 8 bytes raw DUID (length + e.g. MAC) must accept too. But mikrotik is NOT. For example wide-dhcp6 accept everything.

please contact support.