I was under the impression that NTP updated small time differences using the 'slew' method. I honestly expected the leap second would slowly propagate via stratum after stratum of clock slewing...
Posted Jul 2, 2012 16:30 UTC (Mon) by dgm (subscriber, #49227)
[Link]
A time difference is not the same as a leap second. The former comes from a clock running out of sync with the reference one, while the later means some minutes are 61 seconds long on all clocks, even the reference one.
Kernel prepatch 3.5-rc5
Posted Jul 2, 2012 16:33 UTC (Mon) by mikemol (subscriber, #83507)
[Link]
My expectation was that the leap second would be *communicated* as a time difference. I.e. have the stratum N time sources appear to themselves to have gotten 1 second behind their stratum N-1 time sources, and slew back to resync.
Leap seconds
Posted Jul 2, 2012 20:11 UTC (Mon) by midg3t (subscriber, #30998)
[Link]
Impending leap seconds are explicitly signaled in NTP payloads on the day of the leap second. Search for "Leap Indicator" in RFC 2030.