[master] removed references to obsolete versions in documentation

diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml
index 5843ed1d4fdd54eadfc5a9ac79b115df837d9c94..dbe6c6cf2832f5089941a6360a378fabc8f9a44e 100644 (file)
--- a/doc/arm/Bv9ARM-book.xml
+++ b/doc/arm/Bv9ARM-book.xml
@@ -2340,8 +2340,6 @@ options {
          <para>
            The logged error reads "insecurity proof failed" and
            "got insecure response; parent indicates it should be secure".
-           (Prior to BIND 9.7, the logged error was "not insecure".
-           This referred to the zone, not the response.)
          </para>
        </note>
       </section>
@@ -11428,8 +11426,8 @@ example.com                 CNAME   rpz-tcp-only.
            A <command>managed-keys</command> statement contains a list of
            the keys to be managed, along with information about how the
            keys are to be initialized for the first time.  The only
-           initialization method currently supported (as of
-           <acronym>BIND</acronym> 9.7.0) is <literal>initial-key</literal>.
+           initialization method currently supported is
+           <literal>initial-key</literal>.
            This means the <command>managed-keys</command> statement must
            contain a copy of the initializing key.  (Future releases may
            allow keys to be initialized by other methods, eliminating this

diff --git a/doc/arm/dnssec.xml b/doc/arm/dnssec.xml
index f8e14a3c5a7049ad3de735aa86b61f6fdf6bfc5e..5c8e7e340ecf560372a250e293dd25b7324f8eb2 100644 (file)
--- a/doc/arm/dnssec.xml
+++ b/doc/arm/dnssec.xml
@@ -9,9 +9,6 @@
 <!-- Converted by db4-upgrade version 1.0 -->
 <section xmlns:db="http://docbook.org/ns/docbook" version="5.0" xml:id="dnssec.dynamic.zones"><info><title>DNSSEC, Dynamic Zones, and Automatic Signing</title></info>
 
-  <para>As of BIND 9.7.0 it is possible to change a dynamic zone
-  from insecure to signed and back again. A secure zone can use
-  either NSEC or NSEC3 chains.</para>
   <section><info><title>Converting from insecure to secure</title></info>
 
   </section>

diff --git a/doc/arm/managed-keys.xml b/doc/arm/managed-keys.xml
index 342a72efe6160ee4636f1b3ce67c45379581a1d1..a3e9ab8d525b89e6efd50bb53deb684444769fa8 100644 (file)
--- a/doc/arm/managed-keys.xml
+++ b/doc/arm/managed-keys.xml
@@ -9,11 +9,13 @@
 <!-- Converted by db4-upgrade version 1.0 -->
 <section xmlns:db="http://docbook.org/ns/docbook" version="5.0" xml:id="rfc5011.support"><info><title>Dynamic Trust Anchor Management</title></info>
 
-  <para>BIND 9.7.0 introduces support for RFC 5011, dynamic trust
-  anchor management. Using this feature allows
-  <command>named</command> to keep track of changes to critical
-  DNSSEC keys without any need for the operator to make changes to
-  configuration files.</para>
+  <para>
+    BIND is able to maintain DNSSEC trust anchors using RFC 5011 key
+    management. This feature allows <command>named</command> to keep track
+    of changes to critical DNSSEC keys without any need for the operator to
+    make changes to configuration files.
+  </para>
+
   <section><info><title>Validating Resolver</title></info>
 
     <!-- TODO: command tag is overloaded for configuration and executables -->