[DNSOP] Re: Mahesh Jethanandani's No Objection on draft-ietf-dnsop-rfc8624-bis-09: (with COMMENT)
Wes Hardaker <wjhns1@hardakers.net> Tue, 20 May 2025 22:19 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 EFF082AE7F3E; Tue, 20 May 2025 15:19:42 -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 kFDhboIkKFMt; Tue, 20 May 2025 15:19:42 -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 E41722AE7F2E; Tue, 20 May 2025 15:19:41 -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 44E8A2412A; Tue, 20 May 2025 15:19:41 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 44E8A2412A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1747779581; bh=2ep+wMebrPLijMj7vGYsfn9T+oVt+mmCEllxSNl2Y0o=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=AXfMSB4O78Oex1ZvdxsiFVMKBYDsvc0W1lCnw62uMd2xQVm/rPOmF/wB04g1YgYWj caKB3GAdbPnPZcOYbeUg5KyIJ5q7saq2z3WVb3RjZF5Jr4ual4GnCmmfs/7NeLriE8 mDAmEswv++dAatkUO1SyE2RWcq+HONGrDdUGqDuo=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Mahesh Jethanandani via Datatracker <noreply@ietf.org>
In-Reply-To: <174759774554.308216.3236452853303790377@dt-datatracker-59b84fc74f-84jsl> (Mahesh Jethanandani via Datatracker's message of "Sun, 18 May 2025 12:49:05 -0700")
References: <174759774554.308216.3236452853303790377@dt-datatracker-59b84fc74f-84jsl>
Date: Tue, 20 May 2025 15:19:41 -0700
Message-ID: <yblzff7c4ci.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: VQPDTH6VJXB7M5Y4CNTKGWLRHQNCSEYG
X-Message-ID-Hash: VQPDTH6VJXB7M5Y4CNTKGWLRHQNCSEYG
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>, Mahesh Jethanandani <mjethanandani@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: Mahesh Jethanandani'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/7sqdc2kJt9TLmAo9FlwKmgzYSZs>
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>
Thanks for the comments Mahesh, Responses inline: Mahesh Jethanandani via Datatracker <noreply@ietf.org> writes: > Section 7.2, paragraph 10 > > * Update the registration policy for the [DS-IANA] registry to match > > the text describing update requirements above. > > > > * Mark values 128 - 252 as "Reserved" > > > > * Mark values 253 and 254 as "Reserved for Private Use" > > > > * Delete the (now superfluous) column "Status" from the registry > > > > Additionally, the registration policy for the [DS-IANA] registry > > should match the text describing the requirements in this document. > > I think the two statements on "registration policy for the [DS-IANA] registry > are confusing. Can we get rid of one of them? Dropped the second. > "Abstract", paragraph 2 > > the status (MUST, MAY, RECOMMENDED, etc) of any of the algorithms listed in > > ^^^ > In American English, abbreviations like "etc." require a period. fixed > "Abstract", paragraph 2 > > tus (MUST, MAY, RECOMMENDED, etc) of any of the algorithms listed in RFC8624; > > ^^^^^^^^^ > Consider simply using "of" instead. fixed > Section 1.1, paragraph 4 > > less of implementation status. In general it is expected that deployment of > > ^^^^^^^ > A comma is probably missing here. fixed > > Section 1.2, paragraph 2 > > thms to become used less and less over time. Once an algorithm has reached a > > ^^^^^^^^^ > Did you mean "overtime" (=time someone works beyond normal working > hours)? It should be with a space (https://writingexplained.org/over-time-vs-overtime-difference) > Section 1.2, paragraph 3 > > C2119] considers the term SHOULD equivalent to RECOMMENDED, and SHOULD NOT eq > > ^^^^^^^^^^ > The word "equivalent" is a noun or an adjective. A verb is missing or > misspelled, or maybe a comma is missing. "to be" was missing, thanks. -- Wes Hardaker USC/ISI
- [DNSOP] Mahesh Jethanandani's No Objection on dra… Mahesh Jethanandani via Datatracker
- [DNSOP] Re: Mahesh Jethanandani's No Objection on… Wes Hardaker