<no hats/>
All,
(context: prompted by my question in TVR)
I see that in draft-ietf-netmod-schedule-yang Section 4 it advises:
* The second for date and time values MUST have the value "60" at
the end of months in which a leap second occurs.
but I fear this is not sufficient. A scheduling entity in a data center
taking its time from a leap smearing [1, 2] source would probably not know
that this needs to be done, and its notion of time would be
subtly different over a span of (typically) 24 hours prior to the leap
second.
Would it be possible to also include some time reference that doesn't have
to deal with leap seconds, like TAI [3, 4]?
-ek
[1] https://developers.google.com/time/smear
[2]
https://aws.amazon.com/blogs/aws/look-before-you-leap-the-coming-leap-second-and-aws/
[3] https://en.wikipedia.org/wiki/International_Atomic_Time
[4] https://maia.usno.navy.mil/ser7/tai-utc.dat
_______________________________________________
netmod mailing list -- netmod@ietf.org
To unsubscribe send an email to netmod-le...@ietf.org
