> Someone should fork the NTP protocol to use TAI instead, and go from there (or at least provide tai offset). There's a draft of the next version of the NTP p

> Someone should fork the NTP protocol to use TAI instead, and go from there (or at least provide tai offset). There's a draft of the next version of the NTP protocol (NTPv5) at https://www.ietf.org/archive/id/draft-mlichvar-ntp-ntpv5-04.html https://www.ietf.org/archive/id/draft-mlichvar-ntp-ntpv5-04.... which not only has the option of working in TAI, but also has explicit support for "leap second smearing". It also has a field to explicitly provide the TAI offset.