[DNSOP] Re: Ketan Talaulikar's No Objection on draft-ietf-dnsop-must-not-ecc-gost-04: (with COMMENT)

Wes Hardaker <wes@hardakers.net> Fri, 16 May 2025 21:13 UTC

Return-Path: <wes@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 B42A3298DCA5; Fri, 16 May 2025 14:13:31 -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=ham 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 NRpXMML9KmP2; Fri, 16 May 2025 14:13:31 -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 EFA68298DC99; Fri, 16 May 2025 14:13:30 -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 CA211239AE; Fri, 16 May 2025 14:13:29 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net CA211239AE
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1747430009; bh=u61vKse5JB7/vgx9e9Kow9dj2js2b1lhQWWFsAmoZJo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Y7b1D2TCRIXnF/UT4e+AvbmwWdYc0c/Yco4o8e0ciCFVTjiwQMUVZUEuuiY1IYIZB VtJIdVO5HuukzRRuaHaFs1hu7CQ/NRy/uvkqoKLQrHIa4obB3L+ajKILzflMPYQQsZ xiOmSM3MfDf+6D95VMf9I8xk2eRyiY0BVlVLLCUs=
From: Wes Hardaker <wes@hardakers.net>
To: Ketan Talaulikar via Datatracker <noreply@ietf.org>
In-Reply-To: <174740090355.320.5485754233370914457@dt-datatracker-59b84fc74f-84jsl> (Ketan Talaulikar via Datatracker's message of "Fri, 16 May 2025 06:08:23 -0700")
References: <174740090355.320.5485754233370914457@dt-datatracker-59b84fc74f-84jsl>
Date: Fri, 16 May 2025 14:13:29 -0700
Message-ID: <yblwmaguume.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: U7NUFDP5YSMMCQJFEHESN6E653LG24NZ
X-Message-ID-Hash: U7NUFDP5YSMMCQJFEHESN6E653LG24NZ
X-MailFrom: wes@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: The IESG <iesg@ietf.org>, Ketan Talaulikar <ketant.ietf@gmail.com>, draft-ietf-dnsop-must-not-ecc-gost@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Ketan Talaulikar's No Objection on draft-ietf-dnsop-must-not-ecc-gost-04: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0CE3sZnN-wlx-2aMQrt5GZMdHNg>
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>

Ketan Talaulikar via Datatracker <noreply@ietf.org> writes:

Thanks for the comments Ketan.  Some things inline:

> 1) It seems odd (even wrong?) to update an RFC that has been marked historic. I
> would suggest to not do that please.

Well, now I'm stuck as others have wanted that done.  Wheeee.

What you're saying makes sense, so I think this might be a good topic
for the telechat to see what the entire IESG thinks is right here?

> 2) Instead this document could update RFC 9364 which is the BCP for
> DNSsec.

We've talked about whether or not the BCP should be updated as well, but
the general consensus was not to touch that as it should have it's own
update path that was agreed to by the WG.

> 3) The IANA marking part could be done in the parallelly progressing document
> draft-ietf-dnsop-rfc8624-bis with a reference to this document. I am assuming
> that doing just this step is not sufficient as we want additional text/color
> about this obsolesce?

I actually just did this at the request of IANA as well, so thank you.
For this one everyone agrees :-)
-- 
Wes Hardaker                                     
My Games:          https://frostedaxe.com/
My Pictures:       http://photos.capturedonearth.com/