| Subject: | An existing IA is lost when its IAID+DUID roams to a new network |
The server tracks IAs by IAID+DUID, which means if that tuple moves to a new network, an existing IA is simply dropped without proper cleanup or logging and the behavior prohibits the tuple from holding IAs in more than one network.
This issue was initially reported by Bluecat, #10833, and in for their particular customer's situation was mitigated by implementing an EUI-64 based allocation scheme under #43927.
That ticket however did not address the original issue for normal dynamic allocation. At this point the following courses of action are available:
1. Do nothing, as Kea supports the same client holding IAs in more than one network.
2. Detect when an IAID-DUID has roamed to a new subnet, and properly release the IA on the old subnet. Currently we just drop them on the floor.
3. Support IAs on mulitple subnets for an IAID-DUID. IAs on a given subnet expire naturally.
4. Support both 2 & 3, selectable via global configuration parameter
Any changes made would apply only to 4.4.0