... | ... | @@ -544,7 +544,7 @@ The TLS parameters are self-explanatory. |
|
|
|
|
|
RFC 6926/Sec 6.2.7, talks about lease states of "available" or "remote" when they are unassigned based upon whether or not they are currently in scope for (i.e. held by) the server responding to the LeaseQuery.
|
|
|
|
|
|
Unlike ISC DHCP, Kea does track which server in an HA configuration currently holds a free lease, nor is there an efficient way for a server to know if such a lease is in the server's scope, outside of the HA hook library. As this differentiation in state is not required by the RFC, Kea will not be implementing it as this time.
|
|
|
Unlike ISC DHCP, Kea does track which server in an HA configuration currently holds a free lease, nor is there an efficient way for a server to know if such a lease is in the server's scope, outside of the HA hook library. One avenue to consider would be to store the server-id of the server making the lease state change in the user-context. Servers responding the a bulk lease query could toggle local/remote based on whether or not it matches the lease's server-id. Since this differentiation in state is not required by the RFC, Kea will not be implementing it as this time.
|
|
|
|
|
|
### Lease Store Concurrency
|
|
|
|
... | ... | |