> Maybe an iterated DKIMv1 needs this clarification.

Or maybe not, and it certainly isn't a technical point.

AD: I recommend marking this Rejected.

Barry

On Fri, Jul 24, 2026 at 12:13 PM <[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/eid9038/
>
> --------------------------------------
> Type: Technical
> Reported by: Steffen <[email protected]>
>
> Section 3.5 says:
>
> Original Text
> -------------
> t= Signature Timestamp (plain-text unsigned decimal integer;
>       RECOMMENDED, default is an unknown creation time).  The time that
>       this signature was created.  The format is the number of seconds
>       since 00:00:00 on January 1, 1970 in the UTC time zone.  The value
>       is expressed as an unsigned integer in decimal ASCII.  This value
>       is not constrained to fit into a 31- or 32-bit integer.
>       Implementations SHOULD be prepared to handle values up to at least
>       10^12 (until approximately AD 200,000; this fits into 40 bits).
>
> Corrected Text
> --------------
> Ditto, but 10^12 a.k.a. 40 bits is not AD 200,000.
> (Unless this goes in line with Paul McCartney's "three thousand or fouurr 
> thouuuusand" in the Cavern Club appearance in 1999, the first after his wife 
> died.)
>
> It rather is
>
> $ xa '  10**12  / 60 / 60 / 24 / 365'
> 0b 00000000 00000000 00000000 00000000 00000000 00000000 01111011 11011101
> 075735 | 0x7BDD | 31709
>
> (with 40 bits really being
> $ xa '  ((2**40) - 1)  / 60 / 60 / 24 / 365'
> 0b 00000000 00000000 00000000 00000000 00000000 00000000 10001000 00110001
> 0104061 | 0x8831 | 34865)
>
> So "approximately AD 32000".
>
> Notes
> -----
> Maybe an iterated DKIMv1 needs this clarification.
>
> 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