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

Lars Eggert via Datatracker <noreply@ietf.org> Thu, 22 December 2022 12:22 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 658DDC1516F8; Thu, 22 Dec 2022 04:22:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lars Eggert 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: Lars Eggert <lars@eggert.org>
Message-ID: <167171172540.31397.4134994372980589132@ietfa.amsl.com>
Date: Thu, 22 Dec 2022 04:22:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/p-XXq4ZC_SSFhZ3tCTvmKLa8HUQ>
Subject: [DNSOP] Lars Eggert'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: Thu, 22 Dec 2022 12:22:05 -0000

Lars Eggert 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:
----------------------------------------------------------------------

# GEN AD review of draft-ietf-dnsop-dns-catalog-zones-08

CC @larseggert

Thanks to Russ Housley for the General Area Review Team (Gen-ART) review
(https://mailarchive.ietf.org/arch/msg/gen-art/V-jMkADwNBpUN-H4TyNcC_RdTwg).

## Comments

### Section 3, paragraph 2
```
     Catalog consumers MUST ignore any RR in the catalog zone which is
     meaningless to or otherwise not supported by the implementation.
```
Russ Housley raised this in his Gen-ART review: What is meant
by "meaningless" here?

### Too many authors

The document has seven authors, which exceeds the recommended author limit. Has
the sponsoring AD agreed that this is appropriate?

## Nits

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

### Grammar/style

#### "Table of Contents", paragraph 1
```
tent of a DNS zone is synchronized amongst its primary and secondary nameserv
                                   ^^^^^^^
```
Do not mix variants of the same word ("amongst" and "among") within a single
text.

#### Section 4.1, paragraph 3
```
ord in the collection. <unique-N> has an unique value in the collection. When
                                      ^^
```
Use "a" instead of "an" if the following word doesn't start with a vowel sound,
e.g. "a sentence", "a university".

#### Section 5.1, paragraph 7
```
dure described in Section 4.4.1. Otherwise a migration of a member zone from
                                 ^^^^^^^^^
```
A comma may be missing after the conjunctive/linking adverb "Otherwise".

#### Section 5.2, paragraph 2
```
 yet (because of a lost packet or down time or otherwise), but did already se
                                  ^^^^^^^^^
```
This word is normally spelled as one. Did you mean "downtime"?

#### Section 6, paragraph 1
```
 to enumerate the contents of a multi-valued property (such as the list of m
                                ^^^^^^^^^^^^
```
This word is normally spelled as one.

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments
[IRT]: https://github.com/larseggert/ietf-reviewtool