RFC 3830, "MIKEY: Multimedia Internet KEYing", August 2004

Note: This RFC has been updated by RFC 4738, RFC 6309

Errata ID: 4638
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Christopher Dearlove
Date Reported: 2016-03-15
Rejected by: Stephen Farrell
Date Rejected: 2016-03-15

Section 4.2.8 says:

   The timestamp is as defined in NTP [NTP], i.e., a 64-bit number in
   seconds relative to 0h on 1 January 1900.  An implementation MUST be
   aware of (and take into account) the fact that the counter will
   overflow approximately every 136th year.  It is RECOMMENDED that the
   time always be specified in UTC.

It should say:

   The timestamp is as defined in NTP [NTP], i.e., a 64-bit number in
   seconds relative to 0h on 1 January 1900.  It is RECOMMENDED that the
   time always be specified in UTC.

Notes:

A 32-bt number of seconds overflows in about 136.1 years. A 64-bit number of seconds will, for all practical purposes, not overflow.

(The use in Section 4.2.3 is of a 64 bit number, not a 32 bit number, so 64 bits is correct.)
--VERIFIER NOTES--
Only 32 bits of the 64 count seconds. That's clear from the referenced NTP spec.

Report New Errata