|
|
|
|
|
by nickelpro
214 days ago
|
|
The reference implementation, while historically important, has largely been displaced by more secure/performant implementations (ntpsec, chrony), or by in-house implementations (Amazon, Google). Notably NTPd doesn't support leap-smear, which means those who absolutely must have monotonic time can't use it at all. |
|
It should be noted that there currently exists no standard, technical or statutory, for how to do leap smearing. If an event happens and you need to tie your timestamped event logs to the 'greater reality' in some legally binding way there's (AIUI) no way to do that.
A few years ago there was a draft on the idea:
* https://datatracker.ietf.org/doc/draft-stenn-ntp-leap-smear-...
And the currently-draft NTPv5 has something about:
* https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5/
Though the flag simply says that the timescale is smeared and not (AFAICT) how it is being done.
See also perhaps RFC 8633 § 2.7.1:
* https://datatracker.ietf.org/doc/rfc8633/