[DNSOP] Roman Danyliw's No Objection on draft-ietf-dnsop-dns-catalog-zones-08: (with COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Fri, 30 December 2022 23:16 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 703F8C14CEEA; Fri, 30 Dec 2022 15:16:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dnsop-dns-catalog-zones@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com, tjw.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <167244220245.48131.16320131444907522967@ietfa.amsl.com>
Date: Fri, 30 Dec 2022 15:16:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_goe8NrYkzWltmh4T_Z2nplklOc>
Subject: [DNSOP] Roman Danyliw's No Objection on draft-ietf-dnsop-dns-catalog-zones-08: (with COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Dec 2022 23:16:42 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-dnsop-dns-catalog-zones-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-catalog-zones/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Catherine Meadows for the SECDIR review.

I support Murray Kucherawy DISCUSS position.

** Section 3.
Catalog consumers MUST ignore any RR in the catalog zone which is
   meaningless to or otherwise not supported by the implementation.

Can “meaningless” be more formally described?  Are there specific RR which
shouldn’t be in the catalog?

** Section 3.  Editorial.

The content of catalog zones may not be
   accessible from any recursive nameserver.

Can the intent of this be clarified?  Is it saying that the “contents of the
catalog zone may _not necessarily_ be accessible from _all or some_ recursive
nameservers”? or the “contents of the catalog zone _should not be/must not be_
accessible from any recursive nameserver”?