Verified.

The corrected text fixes two inconsistencies:

192.0.2.2 now agrees with the report's Source-IP.

Mon, 18 Jul 2022 22:57:48 -0700 is equivalent to Tue, 19 Jul 2022 00:57:48 -0500, the receipt time stated in the report.


Best
Ale

On Mon, 02 Nov 2026 22:19:06 -0000, [email protected] wrote:
The following errata report has been submitted for RFC9991,
"Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure 
Reporting"

--------------------------------------
You may review the report below and at:
https://errata.rfc-editor.org/eid9258/

--------------------------------------
Type: Technical
Reported by: Rifat Jumagulov <[email protected]>

Section Appendix A says:

Original Text
-------------
Received: from mail.forwarder.example
   (mail.forwarder.example [IPv6:2001:db8::23ac])
   by mail.gen.example (Postfix) with ESMTP id 5E8B0C159826
   for <[email protected]>; Sun, 14 Aug 2022 07:58:29 -0700 (PDT)

Corrected Text
--------------
Received: from mail.forwarder.example
   (mail.forwarder.example [192.0.2.2])
   by mail.gen.example (Postfix) with ESMTP id 5E8B0C159826
   for <[email protected]>; Mon, 18 Jul 2022 22:57:48 -0700 (PDT)

Notes
-----
The report says "received from IP 192.0.2.2 on Tue, 19 Jul 2022 00:57:48 -0500" and has 
"Source-IP: 192.0.2.2". This Received field gives another address and a date in August, 
after the report. The receiving hop should agree with the receipt time and source address stated in 
the report. The proposed values make the example internally consistent: 05:57:48 UTC, four seconds 
after the previous hop.

Changing the report to the IPv6 address is also possible, but it needs more 
changes.

AI tools assisted with drafting and review. I take responsibility for this 
report.

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.

--------------------------------------
RFC9991 (draft-ietf-dmarc-failure-reporting)
--------------------------------------
Title               : Domain-Based Message Authentication, Reporting, and 
Conformance (DMARC) Failure Reporting
Publication Date    : May 2026
Author(s)           : S. Jones, Ed., A. Vesely, Ed.
Category            : Proposed Standard
Source              : dmarc (art)
Stream              : IETF
Verifying Party     : IESG
_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to