From: Michał Kępień Date: Thu, 4 Feb 2021 11:07:40 +0000 (+0100) Subject: Use :rfc:`` references in release notes X-Git-Tag: v9.16.12~1^2~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=33a9c70ecbffec35b01d092e516d41a87330e62b;p=thirdparty%2Fbind9.git Use :rfc:`` references in release notes --- diff --git a/doc/notes/notes-9.16.0.rst b/doc/notes/notes-9.16.0.rst index e3e52c85ae1..2fb936c723d 100644 --- a/doc/notes/notes-9.16.0.rst +++ b/doc/notes/notes-9.16.0.rst @@ -36,7 +36,7 @@ New Features When used with the keyword ``initial-key``, ``trust-anchors`` has the same behavior as ``managed-keys``, i.e., it configures a trust anchor - that is to be maintained via RFC 5011. + that is to be maintained via :rfc:`5011`. When used with the new keyword ``static-key``, ``trust-anchors`` has the same behavior as ``trusted-keys``, i.e., it configures a @@ -51,8 +51,8 @@ New Features As with the ``initial-key`` and ``static-key`` keywords, ``initial-ds`` configures a dynamic trust anchor to be maintained via - RFC 5011, and ``static-ds`` configures a permanent trust anchor. [GL - #6] [GL #622] + :rfc:`5011`, and ``static-ds`` configures a permanent trust anchor. + [GL #6] [GL #622] - ``dig``, ``mdig`` and ``delv`` can all now take a ``+yaml`` option to print output in a detailed YAML format. [GL #1145] @@ -64,7 +64,8 @@ New Features - ``dig`` now accepts a new command line option, ``+[no]expandaaaa``, which causes the IPv6 addresses in AAAA records to be printed in full - 128-bit notation rather than the default RFC 5952 format. [GL #765] + 128-bit notation rather than the default :rfc:`5952` format. + [GL #765] - Statistics channel groups can now be toggled. [GL #1030] @@ -74,10 +75,10 @@ Feature Changes - When static and managed DNSSEC keys were both configured for the same name, or when a static key was used to configure a trust anchor for the root zone and ``dnssec-validation`` was set to the default value - of ``auto``, automatic RFC 5011 key rollovers would be disabled. This - combination of settings was never intended to work, but there was no - check for it in the parser. This has been corrected, and it is now a - fatal configuration error. [GL #868] + of ``auto``, automatic :rfc:`5011` key rollovers would be disabled. + This combination of settings was never intended to work, but there + was no check for it in the parser. This has been corrected, and it is + now a fatal configuration error. [GL #868] - DS and CDS records are now generated with SHA-256 digests only, instead of both SHA-1 and SHA-256. This affects the default output of @@ -91,7 +92,7 @@ Feature Changes - ``named`` will now log a warning if a static key is configured for the root zone. [GL #6] -- A SipHash 2-4 based DNS Cookie (RFC 7873) algorithm has been added +- A SipHash 2-4 based DNS Cookie (:rfc:`7873`) algorithm has been added and made default. Old non-default HMAC-SHA based DNS Cookie algorithms have been removed, and only the default AES algorithm is being kept for legacy reasons. This change has no operational impact diff --git a/doc/notes/notes-9.16.11.rst b/doc/notes/notes-9.16.11.rst index e00b93a787f..9d0c09bd5ea 100644 --- a/doc/notes/notes-9.16.11.rst +++ b/doc/notes/notes-9.16.11.rst @@ -32,7 +32,7 @@ Feature Changes without making it bogus in the process; changing to ``dnssec-policy none;`` also causes CDS and CDNSKEY DELETE records to be published, to signal that the entire DS RRset at the parent must be removed, as - described in RFC 8078. [GL #1750] + described in :rfc:`8078`. [GL #1750] - When using the ``unixtime`` or ``date`` method to update the SOA serial number, ``named`` and ``dnssec-signzone`` silently fell back to diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index e201ccf4b23..73fba49d2b3 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -81,9 +81,9 @@ Feature Changes - The default value of ``max-stale-ttl`` has been changed from 12 hours to 1 day and the default value of ``stale-answer-ttl`` has been changed from 1 - second to 30 seconds, following RFC 8767 recommendations. [GL #2248] + second to 30 seconds, following :rfc:`8767` recommendations. [GL #2248] -- As part of an ongoing effort to use RFC 8499 terminology, +- As part of an ongoing effort to use :rfc:`8499` terminology, ``primaries`` can now be used as a synonym for ``masters`` in ``named.conf``. Similarly, ``notify primary-only`` can now be used as a synonym for ``notify master-only``. The output of ``rndc