Mention TLS certs verification in the CHANGES and Release Notes

This commit adds points to the CHANGES and the release notes about
supporting remote TLS certificates verification and support for Strict
and Mutual TLS transport connections verification.

diff --git a/CHANGES b/CHANGES
index dc6429a66df94eeb3e4a7aee72f5ceb103c71d16..71b31cd4daafe6b01dcb9b771d15d6071f99dfca 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,8 @@
+5839.  [func]          Add support for remote TLS certificates
+                       verification, both to BIND and dig, making it possible
+                       to implement Strict and Mutual TLS authentication,
+                       as described in RFC 9103, Section 9.3. [GL #3163]
+
 5838.  [cleanup]       When modifying a member zone in a catalog zone, and it
                        is detected that the zone exists and was not created by
                        the current catalog zone, distinguish the two cases when

diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst
index 16ec7999ddf1c0815c7877c43a16cf1e4afaea60..ca90a971b9bafda2bd4ad43c3dddf90b2f3886b3 100644 (file)
--- a/doc/notes/notes-current.rst
+++ b/doc/notes/notes-current.rst
@@ -60,6 +60,10 @@ New Features
   specify a journal file to read when loading the zone to be verified or
   signed. :gl:`#2486`
 
+- Add support for remote TLS certificates verification, both to BIND
+  and ``dig``, making it possible to implement Strict and Mutual TLS
+  authentication, as described in RFC 9103, Section 9.3. :gl:`#3163`
+
 Removed Features
 ~~~~~~~~~~~~~~~~