Open pusateri opened 5 years ago
While I understand the desire to make this look like existing things, sometimes it's better to move forward. gettimeofday() returns a 64 bit seconds and this requires no translation to compare and set timers for. Rather than just accept going backward to a more complicated wrapping scheme, I think we should wait for implementation experience to determine the best way forward. If after implementation experience, the 32-bit version is still desired, we can make the change at that time.
Tony Finch @fanf2 would like to see a different timestamp format.
Currently there is a 64-bit unix epoch timestamp in the TIMEOUT resource record. This is currently the recommended way to store timestamps and what is returned by gettimeofday() on all modern systems. However, this is not the customary way to store timestamps in the current DNS protocols which already have 4 different ways to represent time (RRSIG, SIG, TKEY, and TSIG).
One recommendation is to use a wrapping 32-bit timestamp as specified in [RFC4034] 3.1.5. Signature Expiration and Inception Fields