Make use of the :rfc: role in the ARM consistent

Make sure all RFC references in the ARM use the stock :rfc: Sphinx role.

(cherry picked from commit aeb43a45ac0fdff721477755dcd845f3df647869)

diff --git a/doc/arm/general.rst b/doc/arm/general.rst
index 3f478040fe6d0eac081aefe5d505f1d22652b450..a15fb30b62fdeda9374b1988f68b2abfa9ec7a5c 100644 (file)
--- a/doc/arm/general.rst
+++ b/doc/arm/general.rst
@@ -581,7 +581,7 @@ is accepted but not returned in responses.
 [17] Wildcard records are not supported in DNSSEC secure zones.
 
 [18] Servers authoritative for secure zones being resolved by BIND
-9 must support EDNS0 (RFC2671), and must return all relevant SIGs
+9 must support EDNS0 (:rfc:`2671`), and must return all relevant SIGs
 and NXTs in responses, rather than relying on the resolving server
 to perform separate queries for missing SIGs and NXTs.
 

diff --git a/doc/arm/managed-keys.rst b/doc/arm/managed-keys.rst
index ac6424c689060dceda8bacc3cf1ef4945d40bb5e..fa771bebb1707ca7b6bd1fc8cd586e3edfe396ec 100644 (file)
--- a/doc/arm/managed-keys.rst
+++ b/doc/arm/managed-keys.rst
@@ -35,7 +35,7 @@ zone with one of them; this is the "active" KSK. All KSKs which do not
 sign the zone are "stand-by" keys.
 
 Any validating resolver which is configured to use the active KSK as an
-RFC 5011-managed trust anchor takes note of the stand-by KSKs in the
+:rfc:`5011`-managed trust anchor takes note of the stand-by KSKs in the
 zone's DNSKEY RRset, and stores them for future reference. The resolver
 rechecks the zone periodically; after 30 days, if the new key is
 still there, the key is accepted by the resolver as a valid

diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index 02824dafd8da43113451758fa2fe14f9b417b6c5..0a7ae18d29a38c16a8e7f4df9d0b5e0d5233af35 100644 (file)
--- a/doc/arm/reference.rst
+++ b/doc/arm/reference.rst
@@ -1873,7 +1873,7 @@ Boolean Options
    is made. For convenience, TTL-style time-unit suffixes may be used to
    specify the value. It also accepts ISO 8601 duration formats.
 
-   The default ``stale-refresh-time`` is 30 seconds, as RFC 8767 recommends
+   The default ``stale-refresh-time`` is 30 seconds, as :rfc:`8767` recommends
    that attempts to refresh to be done no more frequently than every 30
    seconds. A value of zero disables the feature, meaning that normal
    resolution will take place first, if that fails only then ``named`` will