[3281] Corrected bind10-guide DHCP server limitation sections.

diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index 39c62d7e673388c9897f2b8e50f1891c49465b2c..b1c4c829b3c3fab927e0d2aa8f3011444354d397 100644 (file)
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -3848,7 +3848,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com"   string
       </para>
       </section>
 
-      <section>
+      <section id="ipv4-subnet-id">
       <title>IPv4 Subnet Identifier</title>
       <para>
         Subnet identifier is a unique number associated with a particular subnet.
@@ -5047,19 +5047,11 @@ Dhcp4/dhcp-ddns/qualifying-suffix       "example.com"   string
       yet</quote>, rather than actual limitations.</para>
       <itemizedlist>
           <listitem> <!-- see tickets #3234, #3281 -->
-            <para>
-              On-line configuration has some limitations. Adding new subnets or
-              modifying existing ones work, as is removing the last subnet from
-              the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if
-              there are 4 subnets configured) will cause issues. The problem is
-              caused by simplistic subnet-id assignment. The subnets are always
-              numbered, starting from 1. That subnet-id is then used in leases
-              that are stored in the lease database. Removing non-last subnet will
-              cause the configuration information to mismatch data in the lease
-              database. It is possible to manually update subnet-id fields in
-              MySQL database, but it is awkward and error prone process. A better
-              reconfiguration support is planned.
-            </para>
+            <simpara>
+              Removal of a subnet during server reconfiguration may cause renumbering
+              of auto-generated subnet identifiers, as described in section
+              <xref linkend="ipv4-subnet-id"/>.
+            </simpara>
           </listitem>
           <listitem>
           <para>
@@ -5338,7 +5330,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix   "example.com"   string
       </para>
     </section>
 
-    <section>
+    <section id="ipv6-subnet-id">
       <title>IPv6 Subnet Identifier</title>
       <para>
         Subnet identifier is a unique number associated with a particular subnet.
@@ -6513,19 +6505,11 @@ Dhcp6/dhcp-ddns/qualifying-suffix       "example.com"   string
       <itemizedlist>
 
           <listitem> <!-- see tickets #3234, #3281 -->
-            <para>
-              On-line configuration has some limitations. Adding new subnets or
-              modifying existing ones work, as is removing the last subnet from
-              the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if
-              there are 4 subnets configured) will cause issues. The problem is
-              caused by simplistic subnet-id assignment. The subnets are always
-              numbered, starting from 1. That subnet-id is then used in leases
-              that are stored in the lease database. Removing non-last subnet will
-              cause the configuration information to mismatch data in the lease
-              database. It is possible to manually update subnet-id fields in
-              MySQL database, but it is awkward and error prone process. A better
-              reconfiguration support is planned.
-            </para>
+            <simpara>
+              Removal of a subnet during server reconfiguration may cause renumbering
+              of auto-generated subnet identifiers, as described in section
+              <xref linkend="ipv6-subnet-id"/>.
+            </simpara>
           </listitem>
 
         <listitem>