RFC Errata
Found 2 records.
Status: Held for Document Update (2)
RFC 8460, "SMTP TLS Reporting", September 2018
Source of RFC: uta (sec)
Errata ID: 5889
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Scott Kitterman
Date Reported: 2019-10-31
Held for Document Update by: Alexey Melnikov
Date Held: 2020-03-25
Section 6.7 says:
Item is missing entirely
It should say:
6.7 DKIM Service Type This document registers a new DKIM Service Type in the DomainKeys Identified Mail (DKIM) Parameters registry: Service Type name: tlsrpt Reference: RFC 8460 Status Active
Notes:
The new service type is discussed in Section 3, so it should have been added to the registry. It's an IETF Review required registry, not Specification Required, so this can (and should) be addressed in terms at least of the registry now.
Alexey: Murray wrote:
I would guess we can't rectify this oversight via the errata system. What got IETF Review was the need for the registration, but not the registration itself.
I imagine this should either be done through DISPATCH (which is chartered to do minor housekeeping things like this) or through an AD-sponsored document that contains only the registration.
Errata ID: 6241
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Kristian Klausen
Date Reported: 2020-07-27
Held for Document Update by: Barry Leiba
Date Held: 2020-07-29
Section Appendix B. says:
Appendix B. Example JSON Report ... "policies": [{ "policy": { ... "mx-host": "*.mail.company-y.example" }, ...
It should say:
Appendix B. Example JSON Report ... "policies": [{ "policy": { ... "mx-host": ["*.mail.company-y.example"] }, ...
Notes:
"mx-host-pattern" is defined as a JSON array
========== Verifier notes ==========
This is right on the edge of "Verified": the reporter is correct about the error, but the existing implementations don't comply with the proposed fix. So this really needs to be dealt with in a document update, rather than through an errata report.