[dmarc-ietf] [Editorial Errata Reported] RFC9989 (9150)
rfc-editor@rfc-editor.org Mon, 31 August 2026 15:14 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: dmarc@ietf.org
Delivered-To: dmarc@mail2.ietf.org
Received: from errata-celery-6f84c7996-wb2x7 (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 3FD3E13248026; Mon, 31 Aug 2026 08:14:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788189261; bh=DIOuj9hIq87iVMwYjipStb1r/7mhWIoJm430eKV8QpQ=; h=Subject:From:To:Cc:Date; b=QEPN1BYARMQzpkcoaH2KFkX1XvVSpjwVYvTPcsdSlgLEP3IQV595oumhKW3auL4vt bqXG5WiBHTz550EdWM5RbQoCWeZfNHgtm9iTxVFwVCTZG46Es4rUrsefRNH/Vb9bXV ZEXzKSaTEPI6gfoFW8tlxPzJn5uPLo6jffSZuRpk=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: rfc-editor@rfc-editor.org
Date: Mon, 31 Aug 2026 15:14:21 -0000
message-id: <178818926107.17.380456463655872813@rfc-editor.org>
Message-ID-Hash: TUO4S5Q2TZIUJ2B7AIXQPCFRGY6MN3W6
X-Message-ID-Hash: TUO4S5Q2TZIUJ2B7AIXQPCFRGY6MN3W6
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dmarc.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ietf@johnlevine.com, hello@humerly.com, rfc-editor@rfc-editor.org, dmarc@ietf.org, todd@someguyinva.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmarc-ietf] [Editorial Errata Reported] RFC9989 (9150)
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EK0Td-mPIT8IpFPkXAg0bJqvW4Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Owner: <mailto:dmarc-owner@ietf.org>
List-Post: <mailto:dmarc@ietf.org>
List-Subscribe: <mailto:dmarc-join@ietf.org>
List-Unsubscribe: <mailto:dmarc-leave@ietf.org>
The following errata report has been submitted for RFC9989, "Domain-Based Message Authentication, Reporting, and Conformance (DMARC)" -------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid9150/ -------------------------------------- Type: Editorial Reported by: VENKAT NOOKALA <hello@humerly.com> Section 11.6 (also Appendix B.2.3, B.2.4) says: Original Text ------------- Section 11.6: To avoid abuse by bad actors, reporting addresses generally have to be inside the domains about which reports are requested. To accommodate special cases, such as a need to get reports about domains that cannot actually receive mail, Section 3 of [RFC9990] describes a DNS-based mechanism for validating approved external reporting. Appendix B.2.3: Because the address used in the "ruf" tag is outside the Organizational Domain in which this record is published, conforming Mail Receivers MUST implement additional checks as described in Section 3 of [RFC9990]. Appendix B.2.4: Intermediaries and other third parties should refer to Section 3 of [RFC9990] for the full details of this mechanism. Corrected Text -------------- Section 11.6: ... Section 4 of [RFC9990] describes a DNS-based mechanism for validating approved external reporting. Appendix B.2.3: ... conforming Mail Receivers MUST implement additional checks as described in Section 4 of [RFC9990]. Appendix B.2.4: Intermediaries and other third parties should refer to Section 4 of [RFC9990] for the full details of this mechanism. Notes ----- In RFC 9990, Section 3 is "DMARC Feedback" (report format and delivery). The DNS-based verification mechanism for external reporting addresses is Section 4, "Verifying External Destinations". All three cross-references intend the verification mechanism, so each should read "Section 4 of [RFC9990]". The reference in Appendix B.2.3 is normative (MUST), so the incorrect pointer misdirects implementers. Instructions: ------------- This erratum is currently posted as "Reported". 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. -------------------------------------- RFC9989 (draft-ietf-dmarc-dmarcbis) -------------------------------------- Title : Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Publication Date : May 2026 Author(s) : T. Herr, Ed., J. Levine, Ed. Category : Proposed Standard Source : dmarc (art) Stream : IETF Verifying Party : IESG
- [dmarc-ietf] [Editorial Errata Reported] RFC9989 … rfc-editor
- [dmarc-ietf] Re: [Editorial Errata Reported] RFC9… John R Levine