Skip to main content

Last Call Review of draft-ietf-dnsop-dns-catalog-zones-08
review-ietf-dnsop-dns-catalog-zones-08-dnsdir-lc-blacka-2022-12-27-00

Request Review of draft-ietf-dnsop-dns-catalog-zones
Requested revision No specific revision (document currently at 09)
Type Last Call Review
Team DNS Directorate (dnsdir)
Deadline 2022-12-13
Requested 2022-11-29
Authors Peter van Dijk , Libor Peltan , Ondřej Surý , Willem Toorop , Kees Monshouwer , Peter Thomassen , Aram Sargsyan
I-D last updated 2022-12-27
Completed reviews Dnsdir Last Call review of -08 by David Blacka (diff)
Genart Last Call review of -08 by Russ Housley (diff)
Secdir Last Call review of -08 by Catherine Meadows (diff)
Assignment Reviewer David Blacka
State Completed
Request Last Call review on draft-ietf-dnsop-dns-catalog-zones by DNS Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/dnsdir/7v58S0wA1G5KfiwTrrEdYAqT73w
Reviewed revision 08 (document currently at 09)
Result Ready w/nits
Completed 2022-12-27
review-ietf-dnsop-dns-catalog-zones-08-dnsdir-lc-blacka-2022-12-27-00
Reviewer: David Blacka
Review Result: Ready with Nits

Hi, I'm the designated DNS Directorate (dnsdir) reviewer for this document.
Overall, I think this draft is in pretty good shape.  I have a nit and a few
overall comments.

First, a small typo that could be fixed.  In section 7,

> As catalog zones are transmitted using DNS zone transfers, it is
   RECOMMENDED that catalog zone transfer are protected from unexpected
   modifications by way of authentication,

should be:

> As catalog zones are transmitted using DNS zone transfers, it is
   RECOMMENDED that catalog zone transfers are protected from unexpected
   modifications by way of authentication,

That is, "transfer" should be "transfers".

Second, some comments:

This draft is not quite definitive on whether or not Catalog Zones are directly
queryable.  Instead, it strongly discourages them from being queried, but
usually using non-normative language. (The exception: the security
considerations RECOMMEND limiting who can query the zone.)  I wonder if the
document would be better served with a more up-front statement on this issue?

An appendix showing a full example catalog zone would be a nice addition to the
document.  There are examples throughout the text demonstrating specific
concepts, however, so it isn't clear that such an appendix is strictly
necessary.

Catalog zones appear to be intentionally not fully interoperable between
completely un-coordinated instances.  Is this interpretation correct?  I think
my basic confusion arises from not seeing what can be done with catalog zones
*without* custom properties.