> On Aug 19, 2017, at 2:48 AM, Francis Dupont via RT wrote: > > On Fri Aug 18 23:56:30 2017, philipp@redfish-solutions.com wrote: >> Hi. >> >> I was going through the sources of 4.3.5, in particular, how the >> DUID_LL is generated, and it seems wrong. >> >> Quoting the RFC, we have: >> >> 4. DUID-UUID Format > > => DUID LL and DUID UUID are different formats. DUID LLT and LL > are supported, UUID is not but you can use the raw value. > Salut Francis! Seigneur, ca fait quoi? Vignt ans ou plus? Tu vas bien? So, as I understand it then, there’s currently no support for RFC 6355? Because I see the “diid-uuid” string in common/tables.c mapping to DUID_UUID… I just don’t see DUID_UUID being used anywhere in the sources. Would you accept a fix for DUID-UUID based on an MD5 (or SHA1) hash of the MAC address? We have an application where we need to provision IPv6 leases for assigned addresses (of course) in real-time as boxes get rolled out in the field, and the operations teams are told by installers in the field radioing in MAC addresses as they pull boxes out of their van. -Philip