The WG discussed this during an interim just now.  Andy, we believe this
should be Verified.

-MSK, chairin'

On Wed, Jun 10, 2026 at 11:19 AM <[email protected]> wrote:

> The following errata report has been submitted for RFC6376,
> "DomainKeys Identified Mail (DKIM) Signatures"
>
> --------------------------------------
> You may review the report below and at:
> https://errata.rfc-editor.org/eid8998/
>
> --------------------------------------
> Type: Technical
> Reported by: Roman Donchenko <[email protected]>
>
> Section 3.7 says:
>
> Original Text
> -------------
> data-hash:  is the output from using the hash-alg algorithm, to hash
>                the header including the DKIM-Signature header, and the
>                body hash.
>
> Corrected Text
> --------------
> data-hash:  is the output from using the hash-alg algorithm to hash
>                the headers including the DKIM-Signature header.
>
> Notes
> -----
> The body hash is already included in the DKIM-Signature header and is not
> added to the hash algorithm input separately. Erratum 5252 already corrects
> the pseudocode description of data-hash; this corrects the corresponding
> prose description. I also added a couple of grammatical fixes.
>
> 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.
>
> --------------------------------------
> RFC6376 (draft-ietf-dkim-rfc4871bis)
> --------------------------------------
> Title               : DomainKeys Identified Mail (DKIM) Signatures
> Publication Date    : September 2011
> Author(s)           : D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.
> Category            : Internet Standard
> Source              : dkim (art)
> Stream              : IETF
> Verifying Party     : IESG
>
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to