[DNSOP]Roman Danyliw's No Objection on draft-ietf-dnsop-dnssec-bootstrapping-08: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Sun, 12 May 2024 21:43 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 A1E11C14CE39; Sun, 12 May 2024 14:43:21 -0700 (PDT)
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>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171555020165.28493.11197341718364904094@ietfa.amsl.com>
Date: Sun, 12 May 2024 14:43:21 -0700
Message-ID-Hash: BVVOGVYDKAIBTIQATLETIBRP6FGGNERB
X-Message-ID-Hash: BVVOGVYDKAIBTIQATLETIBRP6FGGNERB
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-dnsop-dnssec-bootstrapping@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Roman Danyliw <rdd@cert.org>
Subject: [DNSOP]Roman Danyliw's No Objection on draft-ietf-dnsop-dnssec-bootstrapping-08: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aF38-MV4ALV3V9PAu_O5rQLgjN4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>
Roman Danyliw has entered the following ballot position for draft-ietf-dnsop-dnssec-bootstrapping-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-dnssec-bootstrapping/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Peter Yee for the GENART review. ** Section 6. Editorial. The level of rigor in Section 4.2 is needed to prevent publication of a half-baked DS RRset Is “half-baked DS RRset” a term-of-art? To improve readability, I recommend not using an idiomatic expression. ** Section 7. Editorial. Per the reference to [draft-ietf-dnsop-dnssec-bootstrapping], this should likely be something like “[This RFC]” and subsequent comment of that string being replaced by the RFC Editor. ** idnits reports: ** Obsolete normative reference: RFC 8499 (Obsoleted by RFC 9499)
- [DNSOP]Roman Danyliw's No Objection on draft-ietf… Roman Danyliw via Datatracker
- [DNSOP]Re: Roman Danyliw's No Objection on draft-… Peter Thomassen