The following errata report has been held for document update for RFC9432,
"DNS Catalog Zones"

--------------------------------------
You may review the report below and at:
https://errata.rfc-editor.org/eid9180/

--------------------------------------

Status: Held for Document Update
Type: Technical
Reported by: Antun Jurkovikj <[email protected]>
Date Reported: Sept. 15, 2026, 9:05 p.m.
Held by: Mohamed Boucadair (IESG)

Section 7 and 9.1 says:

Original Text
-------------
As catalog zones are transmitted using DNS zone transfers, it is
RECOMMENDED that catalog zone transfers be protected from unexpected
modifications by way of authentication, e.g., by using a Transaction
Signature (TSIG) [RFC8945] or Strict or Mutual TLS authentication
with DNS zone transfer over TLS or QUIC [RFC9103].

Use of DNS UPDATE [RFC2136] to modify the content of catalog zones
SHOULD similarly be authenticated.

Zone transfers of member zones SHOULD similarly be authenticated.
TSIG shared secrets used for member zones SHOULD NOT be mentioned in
the catalog zone data.  However, key identifiers may be shared within
catalog zones.

Catalog zones reveal the zones served by their consumers, including
their properties.  To prevent unintentional exposure of catalog zone
contents, it is RECOMMENDED to limit the systems able to query them
and to conduct catalog zone transfers confidentially [RFC9103].

Corrected Text
--------------
As catalog zones are transmitted using DNS zone transfers, it is
RECOMMENDED that catalog zone transfers be protected from unexpected
modifications by way of authentication, e.g., by using a Transaction
Signature (TSIG) [RFC8945] or Strict or Mutual TLS authentication
with DNS zone transfer over TLS or QUIC [RFC9103] [RFC9250].

Use of DNS UPDATE [RFC2136] to modify the content of catalog zones
SHOULD similarly be authenticated.

Zone transfers of member zones SHOULD similarly be authenticated.
TSIG shared secrets used for member zones SHOULD NOT be mentioned in
the catalog zone data.  However, key identifiers may be shared within
catalog zones.

Catalog zones reveal the zones served by their consumers, including
their properties.  To prevent unintentional exposure of catalog zone
contents, it is RECOMMENDED to limit the systems able to query them
and to conduct catalog zone transfers confidentially [RFC9103]
[RFC9250].

Notes
-----
== Original Submitter Notes

RFC 9103 specifies DNS zone transfer over TLS. RFC 9250 specifies
DNS over QUIC, including AXFR and IXFR in Section 5.7. Its Section
5.1 retains RFC 9103's authentication requirements for zone transfer.

Section 7 already includes QUIC. Adding RFC 9250 supplies its defining
reference while retaining RFC 9103. This does not change the existing
authentication or confidentiality recommendations.

Add the following entry to Section 9.1 (Normative References):

[RFC9250]  Huitema, C., Dickinson, S., and A. Mankin, "DNS over
           Dedicated QUIC Connections", RFC 9250,
           DOI 10.17487/RFC9250, May 2022,
           <https://www.rfc-editor.org/info/rfc9250>.

== Verifier's notes 

RFC9103 is one way to achieve the behavior recommended in Section 7. In the 
meantime, RFC9250 says that it mimics RFC9103 for these matters. Citing RFC9250 
and RFC9103 as normative (as suggested above) is questionable as the main 
recommendation is independent of the transport. This can be figured out in a 
future update.

--------------------------------------
RFC9432 (draft-ietf-dnsop-dns-catalog-zones)
--------------------------------------
Title               : DNS Catalog Zones
Publication Date    : July 2023
Author(s)           : P. van Dijk, L. Peltan, O. SurĂ½, W. Toorop, C.R. 
Monshouwer, P. Thomassen, A. Sargsyan
Category            : Proposed Standard
Source              : dnsop (ops)
Stream              : IETF
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to