[dnsext] Re: [Editorial Errata Reported] RFC4035 (7972 )
S Moonesamy <sm+ietf@elandsys.com> Thu, 06 June 2024 10:30 UTC
Return-Path: <sm@elandsys.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 C089CC1D6FC6 for <dnsext@ietfa.amsl.com>; Thu, 6 Jun 2024 03:30:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 B4w8PeOGahln for <dnsext@ietfa.amsl.com>; Thu, 6 Jun 2024 03:30:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B77C15107F for <dnsext@ietf.org>; Thu, 6 Jun 2024 03:30:02 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.225.122.213]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 4568nOQE021879 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jun 2024 01:50:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1717663828; x=1717750228; i=@elandsys.com; bh=QS1p2GiAws7v8NwB2jquLKssLIWAct0ctihKgEyDS7k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mSJcW0nzDvBtADHp6PQWWOlfzePgTHJ4vX5rz7I34DB3HR+wZFJ89zlc0/QMMTAKt 4v47ePlLJ9Dbsf0eRp5b87nqMTm2NVA4LeW5OGzZWbPj0S363Jk5Jxwn3zFsFw2SNb bwo45FxVu2eHJOdT+yvQy59q65S0/Qod+cdb3rcM=
Message-Id: <6.2.5.6.2.20240606013520.17b259c8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 06 Jun 2024 01:48:34 -0700
To: Rob Austein <sra@hactrn.net>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <20240606030200.293F557A1964@orthanc.hactrn.net>
References: <20240606023706.9A985C000063@rfcpa.rfc-editor.org> <20240606030200.293F557A1964@orthanc.hactrn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: ENTWUSE2NPX6532NZ5KWC7WQ4672QHCM
X-Message-ID-Hash: ENTWUSE2NPX6532NZ5KWC7WQ4672QHCM
X-MailFrom: sm@elandsys.com
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-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: nate@natechoe.dev, roy.arends@telin.nl, sra@isc.org, mlarson@verisign.com, massey@cs.colostate.edu, scott.rose@nist.gov, dnsext@ietf.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/JaI9WyYkqGeGch2LOsPb-l0DMB8>
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>
Hi Rob, At 08:02 PM 05-06-2024, Rob Austein wrote: >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. With hindsight I might say that the text could have been written differently. The proposed change is not an editorial change given that it would change what was intended at the time the RFC was published. I suggest that the erratum be marked as "rejected". Regards, S. Moonesamy
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Rob Austein
- [dnsext] [Editorial Errata Reported] RFC4035 (797… RFC Errata System
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Ted Hardie
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … S Moonesamy
- [dnsext] Re: dnsext[Editorial Errata Reported] RF… Wes Hardaker
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Rose, Scott W. (Fed)
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Olafur Gudmundsson
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Rebecca VanRheenen
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Eric Vyncke (evyncke)
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Eric Vyncke (evyncke)
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Rob Austein
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Eric Vyncke (evyncke)