[dnsext] Re: [Editorial Errata Reported] RFC4035 (7972)

Olafur Gudmundsson <ogud@ogud.com> Thu, 06 June 2024 13:41 UTC

Return-Path: <ogud@ogud.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32D80C14F6AA for <dnsext@ietfa.amsl.com>; Thu, 6 Jun 2024 06:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 47JgPRRV5K3Z for <dnsext@ietfa.amsl.com>; Thu, 6 Jun 2024 06:41:19 -0700 (PDT)
Received: from smtp101.ord1d.emailsrvr.com (smtp101.ord1d.emailsrvr.com [184.106.54.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3758EC14F68B for <dnsext@ietf.org>; Thu, 6 Jun 2024 06:41:19 -0700 (PDT)
X-Auth-ID: ogud@ogud.com
Received: by smtp13.relay.ord1d.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id ABDF4C01E9; Thu, 6 Jun 2024 09:41:17 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <20240606030200.293F557A1964@orthanc.hactrn.net>
Date: Thu, 06 Jun 2024 09:41:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <16A2B59E-C1DD-4DEB-A7DF-F507634FE657@ogud.com>
References: <20240606023706.9A985C000063@rfcpa.rfc-editor.org> <20240606030200.293F557A1964@orthanc.hactrn.net>
To: Rob Austein <sra@hactrn.net>
X-Mailer: Apple Mail (2.3774.600.62)
X-Classification-ID: ed29b28a-d548-4757-b5d6-2add080f1ce9-1-1
X-MailFrom: ogud@ogud.com
X-Mailman-Rule-Hits: max-recipients
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-size; news-moderation; no-subject; digests; suspicious-header
Message-ID-Hash: GWRUJTDCASU3IWOAB3Z7HFQ3U3NTK26G
X-Message-ID-Hash: GWRUJTDCASU3IWOAB3Z7HFQ3U3NTK26G
X-Mailman-Approved-At: Thu, 06 Jun 2024 09:41:29 -0700
CC: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, nate@natechoe.dev, roy.arends@telin.nl, Rob Austein <sra@isc.org>, Matt Larson <mlarson@verisign.com>, Daniel Massey <massey@cs.colostate.edu>, Scott Rose <scott.rose@nist.gov>, dnsext@ietf.org, Matt Larson <matt.larson@icann.org>, Roy Arends <roy.arends@icann.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [dnsext] Re: [Editorial Errata Reported] RFC4035 (7972)
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/0ezHMquR32ueiLWQNCefqGLh9BE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Owner: <mailto:dnsext-owner@ietf.org>
List-Post: <mailto:dnsext@ietf.org>
List-Subscribe: <mailto:dnsext-join@ietf.org>
List-Unsubscribe: <mailto:dnsext-leave@ietf.org>

Added upto date addresses for Roy and Matt

> On Jun 5, 2024, at 11:02 PM, Rob Austein <sra@hactrn.net> wrote:
> 
>> Type: Editorial
>> Reported by: Nate Choe <nate@natechoe.dev>
>> 
>> Section: 4.2
>> 
>> Original Text
>> -------------
>>   Security-aware resolvers MAY query for missing security RRs in an
>>   attempt to perform validation; implementations that choose to do so
>>   must be aware that the answers received may not be sufficient to
>>   validate the original response.  For example, a zone update may have
>>   changed (or deleted) the desired information between the original and
>>   follow-up queries.
>> 
>> Corrected Text
>> --------------
>>   Security-aware resolvers MAY query for missing security RRs in an
>>   attempt to perform validation; implementations that choose to do so
>>   MUST be aware that the answers received may not be sufficient to
>>   validate the original response.  For example, a zone update may have
>>   changed (or deleted) the desired information between the original and
>>   follow-up queries.
>> 
>> Notes
>> -----
>> "MUST" is a key word according to RFC 2119/BCP 14 and should be capitalized.
> 
> Well, it's been nearly twenty years, and I don't feel terribly
> strongly about this, but since Nate raised the point:
> 
> I think I disagree.  "MUST" is keyword, "must" is not.  It probably
> would have been advisable to avoid the non-keyword "must" due to the
> risk of this confusion, but "MUST be aware" does not seem actionable
> to me, nor does it seem likely to be what the author of the original
> text (who may or may not have been me) intended.
> 
> So I would reject this erratum, but as noted above, I don't feel
> strongly about this, and will not stand in the way if the (long
> disbanded) WG or my co-editors (most of whose contact information has
> probably changed by now) agree with Nate.
> 

I agree with Rob this is unfortunate use of the word must, I recall that this was reported to soon after the RFC was published and the chairs decided not to take an action at that time. 
After that I started scanning all LC working group documents for 2119 words in lower case and asking editors to confirm each one as impossible to replace or upper case. 

Olafur