[dnsext] Re: [Editorial Errata Reported] RFC4035 (7972)
Rebecca VanRheenen <rvanrheenen@amsl.com> Fri, 07 June 2024 18:46 UTC
Return-Path: <rvanrheenen@amsl.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 D1DE1C14F6A2 for <dnsext@ietfa.amsl.com>; Fri, 7 Jun 2024 11:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 2Pa74qcrB3eD for <dnsext@ietfa.amsl.com>; Fri, 7 Jun 2024 11:46:54 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 43771C151534 for <dnsext@ietf.org>; Fri, 7 Jun 2024 11:46:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D7B11423462D; Fri, 7 Jun 2024 11:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CkpDJDRWL98b; Fri, 7 Jun 2024 11:46:18 -0700 (PDT)
Received: from [IPv6:2601:641:300:5fb0:1533:d705:d4ce:6de] (unknown [IPv6:2601:641:300:5fb0:1533:d705:d4ce:6de]) by c8a.amsl.com (Postfix) with ESMTPSA id AA919424B427; Fri, 7 Jun 2024 11:46:18 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <20240606023706.9A985C000063@rfcpa.rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F00DDFA-2EFC-41A2-92B5-EC9CA0193688@amsl.com>
References: <20240606023706.9A985C000063@rfcpa.rfc-editor.org>
To: Erik Kline <ek.ietf@gmail.com>, evyncke@cisco.com
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-MailFrom: rvanrheenen@amsl.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: 2IA5DC2INQWKH7CF7LMAKZAP3PLIRCZM
X-Message-ID-Hash: 2IA5DC2INQWKH7CF7LMAKZAP3PLIRCZM
X-Mailman-Approved-At: Sat, 08 Jun 2024 19:37:34 -0700
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, RFC Editor <rfc-editor@rfc-editor.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/LeVqcLl6wN_HXLVNHTfx4bBaj-M>
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>
Date: Fri, 07 Jun 2024 18:46:58 -0000
X-Original-Date: Fri, 7 Jun 2024 11:46:18 -0700
Hi Erik and Éric, We are unable to verify this erratum that the submitter marked as editorial, so we changed the Type to “Technical”. As Stream Approver, please review and set the Status and Type accordingly (see the definitions at https://www.rfc-editor.org/errata-definitions/) Note that there has been some discussion about this erratum. See https://mailarchive.ietf.org/arch/browse/dnsext/?q=7972. Also note that we are sending this to both of you as ADs of the Internet Area as the dnsext WG has concluded. You may review the report at: https://www.rfc-editor.org/errata/eid7972 Information on how to verify errata reports can be found at: https://www.rfc-editor.org/how-to-verify/ Further information on errata can be found at: https://www.rfc-editor.org/errata.php Thank you, RFC Editor/rv > On Jun 5, 2024, at 7:37 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > > The following errata report has been submitted for RFC4035, > "Protocol Modifications for the DNS Security Extensions". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7972 > > -------------------------------------- > 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. > > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it > will be removed shortly by the RFC Production Center.) Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC4035 (draft-ietf-dnsext-dnssec-protocol-09) > -------------------------------------- > Title : Protocol Modifications for the DNS Security Extensions > Publication Date : March 2005 > Author(s) : R. Arends, R. Austein, M. Larson, D. Massey, S. Rose > Category : PROPOSED STANDARD > Source : DNS Extensions > Stream : IETF > Verifying Party : IESG >
- [dnsext] [Editorial Errata Reported] RFC4035 (797… RFC Errata System
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Rob Austein
- [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 … Olafur Gudmundsson
- [dnsext] Re: [Editorial Errata Reported] RFC4035 … Rose, Scott W. (Fed)
- [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)