renew-timer should not be accepted in configuration if it is greater then rebind-timer (and vice versa)
Currently it is possible to specify e.g. renew-timer=1500 and rebind-timer=1000, ie. the former is bigger than latter. Kea accepts such configuration. Expected behaviour is that a warning or en error is raised to Kea administrator.
Still, in such case, in ACK packet from Kea only rebind-timer field is present ie. renew-timer will be skipped as it is bigger than rebind-timer.
The configuration was set via cb-cmds. It was not verified if the behaviour is the same in case of config from json file.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information