DHCPv6 "remote-id" without IAID
When a DHCPv6 relay agent forwards a DHCPv6 message from a client to a DHCP server it may add "Remote ID" (option-37) information to its encapsulated message.
If so configured, for example by using the "mac-sources": [ "remote-id" ] or by using the flex-id , Kea can be told to use the remote-id as an identifier for clients instead of using the clients UUID.
In cases where a client is changed but the "remote-id" remains unchanged, clients may be differentiated by the IAID field in the client request. Kea saves the IAID field with the lease data
There may be situations where users would like to retain the same lease-to-remote-id binding, either loosely or permanently with a reservation, even after an IAID changes.
This could be implemented by removing the IAID data from ingress packets. The IAID data must then be re-attached to egress packets.