Set up release notes for BIND 9.18.9

diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst
index e10f3f03ef2a2ffe64e4abf1ac61d33c84289117..79b66041c7c80a13642ed75173263ac7901dad39 100644 (file)
--- a/doc/notes/notes-current.rst
+++ b/doc/notes/notes-current.rst
@@ -9,7 +9,7 @@
 .. See the COPYRIGHT file distributed with this work for additional
 .. information regarding copyright ownership.
 
-Notes for BIND 9.18.8
+Notes for BIND 9.18.9
 ---------------------
 
 Security Fixes
@@ -20,30 +20,13 @@ Security Fixes
 Known Issues
 ~~~~~~~~~~~~
 
-- Upgrading from BIND 9.16.32, 9.18.6, or older, may require a manual
-  configuration change. The following configurations are affected:
-
-  - :any:`type primary` zones configured with :any:`dnssec-policy` but without
-    either :any:`allow-update` or :any:`update-policy`
-  - :any:`type secondary` zones configured with :any:`dnssec-policy`
-
-  In these cases please add :namedconf:ref:`inline-signing yes;
-  <inline-signing>` to individual zone configuration(s). Without applying this
-  change :iscman:`named` will fail to start. For more details see
-  https://kb.isc.org/docs/dnssec-policy-requires-dynamic-dns-or-inline-signing
-
-- BIND 9.18 does not support dynamic updates forwarding (see
-  :any:`allow-update-forwarding`) in conjuction with zone transfers
-  over TLS (XoT). :gl:`#3512`
+- None.
 
 New Features
 ~~~~~~~~~~~~
 
 - None.
 
-- :iscman:`named` now logs the supported cryptographic algorithms during
-  startup and in the output of :option:`named -V`. :gl:`#3541`
-
 Removed Features
 ~~~~~~~~~~~~~~~~
 
@@ -54,19 +37,7 @@ Feature Changes
 
 - None.
 
-- The ability to use pkcs11 via engine_pkcs11 has been restored, by only using
-  deprecated APIs in OpenSSL 3.0.0. BIND needs to be compiled
-  with '-DOPENSSL_API_COMPAT=10100' specified in the CFLAGS at
-  compile time. :gl:`!6711`
-
-- Add support for parsing and validating ``dohpath`` to SVBC records.
-  :gl:`#3544`
-
 Bug Fixes
 ~~~~~~~~~
 
-- An assertion failure was fixed in ``named`` that was caused by aborting the statistics
-  channel connection while sending statistics data to the client.  :gl:`#3542`
-
-- Changing just the TSIG key names for primaries in catalog zones' member
-  zones was not effective. :gl:`#3557`
+- None.