From: Marcin Siodelski <marcin@isc.org>
Date: Mon, 31 Mar 2014 18:59:26 +0000 (+0200)
Subject: [master] Merge branch 'trac3281'
X-Git-Tag: bind10-1.2.0rc1-release~25
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d90e9a0642fbb16a4e664160b4812f61fb81f1aa;p=thirdparty%2Fkea.git

[master] Merge branch 'trac3281'

Conflicts:
	doc/guide/bind10-guide.xml
---

d90e9a0642fbb16a4e664160b4812f61fb81f1aa
diff --cc doc/guide/bind10-guide.xml
index 6c64525294,b1c4c829b3..6c95e73cb6
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@@ -5016,25 -5047,31 +5052,17 @@@ Dhcp4/dhcp-ddns/qualifying-suffix	"exam
        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>
 -            On startup, the DHCPv4 server does not get the full configuration from
 -            BIND 10.  To remedy this, after starting BIND 10, modify any parameter
 -            and commit the changes, e.g.
 -            <screen>
 -&gt; <userinput>config show Dhcp4/renew-timer</userinput>
 -Dhcp4/renew-timer	1000	integer	(default)
 -&gt; <userinput>config set Dhcp4/renew-timer 1001</userinput>
 -&gt; <userinput>config commit</userinput></screen>
 -          </para>
 -        </listitem>
 -
 -          <listitem>
 -            <simpara>The DHCPv4 server does not support
 -            BOOTP. That is a design choice and the limitation is
 -            permanent. If you have legacy nodes that can't use DHCP and
 -            require BOOTP support, please use the latest version of ISC DHCP,
 -            available from <ulink url="http://www.isc.org/software/dhcp"/>.</simpara>
 +            <simpara>
 +              BOOTP (<ulink url="http://tools.ietf.org/html/rfc951">RFC 951</ulink>)
 +              is not supported.
 +            </simpara>
            </listitem>
            <listitem>
              <simpara>Raw sockets operation is working on Linux
@@@ -6438,47 -6504,39 +6502,39 @@@ Dhcp6/dhcp-ddns/qualifying-suffix	"exam
        yet</quote>, rather than actual limitations.</para>
        <itemizedlist>
  
 -          <listitem> <!-- see tickets #3234, #3281 -->
 +        <listitem> <!-- see tickets #3234, #3281 -->
-           <simpara>
-             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.
-           </simpara>
+             <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>
 -          <para>
 -            On startup, the DHCPv6 server does not get the full configuration from
 -            BIND 10.  To remedy this, after starting BIND 10, modify any parameter
 -            and commit the changes, e.g.
 -            <screen>
 -&gt; <userinput>config show Dhcp6/renew-timer</userinput>
 -Dhcp6/renew-timer	1000	integer	(default)
 -&gt; <userinput>config set Dhcp6/renew-timer 1001</userinput>
 -&gt; <userinput>config commit</userinput></screen>
 -          </para>
 -        </listitem>
 -        <listitem>
 -          <simpara>Temporary addresses are not supported.</simpara>
          </listitem>
          <listitem>
 -          <simpara>Prefix delegation is not supported.</simpara>
 +          <simpara>
 +            The server will allocate, renew or rebind a maximum of one lease
 +            for a particular IA option (IA_NA or IA_PD) sent by a client.
 +            <ulink url="http://tools.ietf.org/html/rfc3315">RFC 3315</ulink> and
 +            <ulink url="http://tools.ietf.org/html/rfc3633">RFC 3633</ulink> allow
 +            for multiple addresses or prefixes to be allocated for a single IA.
 +          </simpara>
          </listitem>
          <listitem>
 -          <simpara>Confirmation (CONFIRM), and duplication report (DECLINE)
 -          are not yet supported.</simpara>
 +          <simpara>Temporary addresses are not supported.</simpara>
          </listitem>
          <listitem>
 -          <simpara>DNS Update is not supported.</simpara>
 +          <simpara>
 +            Confirmation (CONFIRM), duplication report (DECLINE),
 +            stateless configuration (INFORMATION-REQUEST) and client
 +            reconfiguration (RECONFIGURE) are not yet supported.
 +          </simpara>
          </listitem>
 +          <listitem>
 +            <simpara>
 +              The server doesn't act upon expired leases. In particular,
 +              when a lease expires, the server doesn't request removal of
 +              the DNS records associated with it.
 +            </simpara>
 +          </listitem>
        </itemizedlist>
      </section>