From: Francis Dupont Date: Wed, 22 May 2019 08:40:52 +0000 (+0200) Subject: [295-min-max-lease-time-configuration-options] Updated documentation X-Git-Tag: Kea-1.6.0-beta2~239 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e738ffc4f6713791dddcf2ae139b906bc9a4ba9d;p=thirdparty%2Fkea.git [295-min-max-lease-time-configuration-options] Updated documentation --- diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index 238c34a83a..d2816f9b09 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -229,15 +229,27 @@ use it for 4000 seconds. (Note that integer numbers are specified as is, without any quotes around them.) renew-timer and rebind-timer are values (also in seconds) that define T1 and T2 timers that govern when the client will begin the renewal and -rebind procedures. Both renew-timer and -rebind-timer are optional. The server will only send -rebind-timer to the client, via DHCPv4 option code 59, if it is less than -valid-lifetime; and it will only send renew-timer, via DHCPv4 option code 58, -if it is less than rebind-timer (or valid-lifetime if rebind-timer was not -specified). In their absence, the client should select values for T1 and T2 -timers according to RFC 2131. -See section for more details on +rebind procedures. + +From Kea 1.6.0 the lease valid lifetime is extended from a +single value to a triplet with minimum, default and maximum values using +min-valid-lifetime, valid-lifetime and +max-valid-lifetime. When the client does not specify +a lifetime the default value is used, when it specifies using a DHCP option +code 51 this value is used if it is not lesser than the minimum (in this case +the minimum is returned) or greater than the maximum (in this case the +maximum is used). + +Both renew-timer +and rebind-timer are optional. The server will only +send rebind-timer to the client, via DHCPv4 option code 59, if it is +less than lease valid lifetime; and it will only send renew-timer, via +DHCPv4 option code 58, if it is less than rebind-timer (or lease valid +lifetime if rebind-timer was not specified). In their absence, the +client should select values for T1 and T2 timers according +to RFC 2131. See +section for more details on generating T1 and T2. The interfaces-config map specifies the server diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml index c9290b7bca..b332b9a5eb 100644 --- a/doc/guide/dhcp6-srv.xml +++ b/doc/guide/dhcp6-srv.xml @@ -2046,6 +2046,7 @@ should include options from the new option space:
Controlling the Values Sent for T1 and T2 Times + According to RFC 8415, section 21.4, the recommended T1 and T2 values are 50% and 80% @@ -2054,7 +2055,41 @@ should include options from the new option space: percentages of the preferred lease time. The server's behavior is governed by combination of configuration parameters, two of which have already been mentioned. - + + From Kea 1.6.0 lease preferred and valid lifetime are extended from + single values to triplets with minimum, default and maximum values using: + + + min-preferred-lifetime - specifies the minimal preferred lifetime (optional). + + + + preferred-lifetime - specifies the default preferred lifetime. + + + + max-preferred-lifetime - specifies the maximal preferred lifetime (optional). + + + + min-valid-lifetime - specifies the minimal valid lifetime (optional). + + + + valid-lifetime - specifies the default valid lifetime. + + + + max-valid-lifetime - specifies the maximal valid lifetime (optional). + + + + When the client does not specify lifetimes the default is used. When + it specifies a lifetime using IAADDR or IAPREFIX sub option with not + zero values these values are used when they are between configured + minimal (lower values are round up) and maximal (larger values are + round down) bounds. + To send specific, fixed values use the following two parameters: