Possible race with v6 BLQ extended info tables
v6 BLQ extended info tables are subject to race because they are not managed in the same transaction as the lease6 table.
For instance it is possible to retrieve by relay or remote ID some leases which in fact no longer have the corresponding extended info. Three ways to handle (or not) this issue:
- do nothing i.e. move this ticket to Outstanding
- add a warning in the doc explaining the issue and recommending to use small page sizes (configurable in the hook) to limit the race window
- check leases in the hook before returning them (i.e. add soem code after the type and expire checks)
My current opinion is for the first solution: the race is very unlikely so it is enough to know it.