[#1842] Rewording after review

diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst
index e9776050565e880f8f15a730266f6f16df00d0bd..455576757b11a065114d2f2f8451b06f0e5d2d7b 100644 (file)
--- a/doc/sphinx/arm/dhcp4-srv.rst
+++ b/doc/sphinx/arm/dhcp4-srv.rst
@@ -1250,7 +1250,7 @@ avoid this, use the ``min-max`` notation.
     |                                                             |         | client if it moves to another subnet. Another client in a different subnet will      |
     |                                                             |         | not be assigned an address already assigned to the client in any of the subnets.     |
     +-------------------------------------------------------------+---------+--------------------------------------------------------------------------------------+
-    | Pools that are outside the subnet they are configured under | No      | Startup error: DHCP4_PARSER_FAIL                                                     |
+    | Pools not matching the subnet prefix                        | No      | Startup error: DHCP4_PARSER_FAIL                                                     |
     +-------------------------------------------------------------+---------+--------------------------------------------------------------------------------------+
 
 .. _dhcp4-t1-t2-times:

diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst
index 87439aaf73fa4eea3c612daf41155b8bb1430400..da8ef65df159bb3f020b26d060454f0953463402 100644 (file)
--- a/doc/sphinx/arm/dhcp6-srv.rst
+++ b/doc/sphinx/arm/dhcp6-srv.rst
@@ -1166,9 +1166,12 @@ and which is delegated a prefix from this pool.
     +-------------------------------------------------------------------------------+---------+------------------------------------------------------------------------------------+
     | Overlapping prefix delegation pools in one subnet                             | No      | Startup error: DHCP6_PARSER_FAIL                                                   |
     +-------------------------------------------------------------------------------+---------+------------------------------------------------------------------------------------+
-    | Overlapping prefix delegation pools in different subnets                      | Yes     | Can act as a substitute for a global pool mechanic. When assigning leases from     |
-    |                                                                               |         | one pool, Kea correctly excludes leases given under any pool that overlaps         |
-    |                                                                               |         | with it such that no lease is given twice.                                         |
+    | Overlapping prefix delegation pools in different subnets                      | Yes     | Specifying the same prefix delegation pool in different subnets can be used as an  |
+    |                                                                               |         | equivalent of the global pool. In that case, the server can delegate the same      |
+    |                                                                               |         | prefixes regardless of the client's subnet. If a prefix from such a pool is        |
+    |                                                                               |         | delegated to a client in one subnet, the same prefix will be renewed for this      |
+    |                                                                               |         | client if it moves to another subnet. Another client in a different subnet will    |
+    |                                                                               |         | not be delegated a prefix already delegated to the client in any of the subnets.   |
     +-------------------------------------------------------------------------------+---------+------------------------------------------------------------------------------------+
     | Prefix delegation pools not matching the subnet prefix                        | Yes     | It is common in many deployments to configure the prefix delegation pools not      |
     |                                                                               |         | matching the subnet prefix, e.g. a prefix pool of 3000::/96 within the             |