[DNSOP] Opsdir ietf last call partial review of draft-ietf-dnsop-rfc8624-bis-09
Nabeel Cocker via Datatracker <noreply@ietf.org> Mon, 14 April 2025 19:20 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from [10.244.8.129] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 7D3221BE2B75; Mon, 14 Apr 2025 12:20:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Nabeel Cocker via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174465840535.1140913.7319759953755231962@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Mon, 14 Apr 2025 12:20:05 -0700
Message-ID-Hash: ZVACT26QPYL3RYDWK22QHRIWDKS5Z3HL
X-Message-ID-Hash: ZVACT26QPYL3RYDWK22QHRIWDKS5Z3HL
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: dnsop@ietf.org, draft-ietf-dnsop-rfc8624-bis.all@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Nabeel Cocker <ncocker@redhat.com>
Subject: [DNSOP] Opsdir ietf last call partial review of draft-ietf-dnsop-rfc8624-bis-09
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/OW5PiygAcM0KGEPmcOhxJeXc0z4>
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>
Review is partially done. Another assignment may be needed to complete it. Document: draft-ietf-dnsop-rfc8624-bis Title: DNSSEC Cryptographic Algorithm Recommendation Update Process Reviewer: Nabeel Cocker Review result: Has Nits First many thanks to the authors for working on this. A couple of nits: Section 1.2, paragraph 3: ========================== "This will allow for deprecated algorithms to become used less and less over time." Perhaps say it like "This ensures that the use of deprecated algorithms decreases over time." Section 2: =========== The last paragraph states The "Implement for" column values are transcribed from [RFC8624]. The "Use for" columns are set to the same values as the "implement for" ... "implement for" has a lower case "i". Section 2: ---------- The last paragraph states: The "Implement for" column values are transcribed from [RFC8624]. The "Use for" columns are set to the same values as the "implement for" values since the general interpretation to date indicates they have been treated as values for both "implementation" and "use". We note that the values for "Implement for" and "Use for" may diverge in the future. The above text indicates that the "Implement for" and "Use for" columns should have identical values. However, when I look at Table 2, there are differences between the values in the "Implement for" and the "Use for" for number 5, 7, 8, 10 and 13, For example, in number 5 where Use for DNSSEC Validation is "RECOMMEND" but the Implement for DNSSEC Validation is "MUST" |5 |RSASHA1 |NOT |RECOMMENDED|NOT |MUST | | | |RECOMMENDED| |RECOMMENDED| | Is this intentional or am I misreading? If so, there does not seem to be any text explaining this (or I missed it?). Otherwise, the document is very well written. Many thanks to the authors! Regards, Nabeel
- [DNSOP] Opsdir ietf last call partial review of d… Nabeel Cocker via Datatracker
- [DNSOP] Re: Opsdir ietf last call partial review … Wes Hardaker
- [DNSOP] Re: [OPS-DIR]Re: Opsdir ietf last call pa… Nabeel Cocker
- [DNSOP] Re: [OPS-DIR]Re: Opsdir ietf last call pa… Nabeel Cocker
- [DNSOP] Re: [OPS-DIR]Re: Opsdir ietf last call pa… Wes Hardaker