IETF Logo Mail Archive

[DNSOP] Re: Opsdir telechat review of draft-ietf-dnsop-must-not-sha1-06

Wes Hardaker <wjhns1@hardakers.net> Mon, 21 April 2025 22:26 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D74681F0A0B6; Mon, 21 Apr 2025 15:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-ZM7LVGu11v; Mon, 21 Apr 2025 15:26:02 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B4E171F0A0AA; Mon, 21 Apr 2025 15:26:02 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 0E2EF21E81; Mon, 21 Apr 2025 15:26:02 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 0E2EF21E81
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1745274362; bh=p5n5voa8rLUsjCnoXw9P1JhD+IpzZsR5dZ3WtOiG8Ro=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=D27XSCqsSb/aknBBI74EvoZlK5rQ9ir4B2oG3qXUW+tfgvZS6sfBIPTVxHiHyxczH PaptJ6jc+uV5GaQACZXEcjAOBq79I91pAcTTEm9Wwgey2CvCRbiIKWbMsMaO9iB2fj pXKRRx6Q8Eoh3N/hLxBChdYCc/OkJZYh44D1gZh0=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Thomas Graf via Datatracker <noreply@ietf.org>
In-Reply-To: <174452482114.1087190.7524107463900913195@dt-datatracker-64c5c9b5f9-hz6qg> (Thomas Graf via Datatracker's message of "Sat, 12 Apr 2025 23:13:41 -0700")
References: <174452482114.1087190.7524107463900913195@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Mon, 21 Apr 2025 15:26:01 -0700
Message-ID: <yblv7qx883q.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: 5LK4FQJDRNDLYMHCZEMTCIZFK6YZFOTY
X-Message-ID-Hash: 5LK4FQJDRNDLYMHCZEMTCIZFK6YZFOTY
X-MailFrom: wjhns1@hardakers.net
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: ops-dir@ietf.org, Thomas Graf <thomas.graf@swisscom.com>, dnsop@ietf.org, draft-ietf-dnsop-must-not-sha1.all@ietf.org, last-call@ietf.org, iana-chairs@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Opsdir telechat review of draft-ietf-dnsop-must-not-sha1-06
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/B-82zPfHEk4OjlUCiFU_tdcYzow>
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>

Thomas Graf via Datatracker <noreply@ietf.org> writes:

Hi Thomas,

Thank you for the review.

> However there is a possible mismatch when comparing the text in the IANA
> consideration section of the document and the Delegation Signer (DS) Resource
> Record (RR) Type Digest Algorithms registry.

Yes, that's because the other document being progressed at the same time
creates the columns with the names that this document is then
immediately(ish) changing:

https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc8624-bis/

Thus, your suggested change would likely work for the existing table,
but our intent was the future table modified by the above draft.

-- 
Wes Hardaker
USC/ISI

v2.38.3 | Report a Bug | By Email | System Status