[DNSOP] Re: Ketan Talaulikar's No Objection on draft-ietf-dnsop-rfc8624-bis-09: (with COMMENT)

Wes Hardaker <wjhns1@hardakers.net> Tue, 20 May 2025 20:47 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 7147B2AE334F; Tue, 20 May 2025 13:47:13 -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 k5c5DWdqnP_l; Tue, 20 May 2025 13:47:13 -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 CC0E72AE334A; Tue, 20 May 2025 13:47:12 -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 003F52412A; Tue, 20 May 2025 13:47:12 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 003F52412A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1747774032; bh=UM5uET7nyRx7ZXunvSqGKc5STxZvNRaYyO9xYHKBHYI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=iFRcpQwlOkWEPInds8RfuRrVQO6JjhHk8gRoFKE8IV3AD8pR2iVupXOFvzjtyWKQ0 FAaphYGbp40GhqAykGwyM+wYF8R8CL7hwkapEpoMyfadUydDgcsQo1CsXnBde4R3pR UttQyAyUeOLD6+ZtZNjhyejG8RjwzzuZ4m5zX/F0=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Ketan Talaulikar via Datatracker <noreply@ietf.org>
In-Reply-To: <174740246732.302.1496629496693602972@dt-datatracker-59b84fc74f-84jsl> (Ketan Talaulikar via Datatracker's message of "Fri, 16 May 2025 06:34:27 -0700")
References: <174740246732.302.1496629496693602972@dt-datatracker-59b84fc74f-84jsl>
Date: Tue, 20 May 2025 13:47:11 -0700
Message-ID: <ybly0urf1rk.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: KXJWGPV7YLICWRC5H4GP6ZN7GT6Y3QMB
X-Message-ID-Hash: KXJWGPV7YLICWRC5H4GP6ZN7GT6Y3QMB
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: The IESG <iesg@ietf.org>, Ketan Talaulikar <ketant.ietf@gmail.com>, draft-ietf-dnsop-rfc8624-bis@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-rfc8624-bis-09: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tz9DAqcUDhNqzsR0iLJ1IimQn9w>
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:

Hi Ketan,

Thanks for the feedback!  Comment inline:

> Also, do consider using this document as a complete replacement for 8624 (since
> things are being moved from that doc into IANA?) and 9157 (since it is about
> IANA). If this document continues to just "update" them, then we have a
> trifecta of documents (or may be there are more?). Do see if things could be
> further simplified for the community that is going to use this work.

We can't obsolete 9157 since it contains guidance beyond updating 8624.
But we can update it.


-- 
Wes Hardaker                                     
USC/ISI