Using the Network Time Protocol (NTP) to transmit International Atomic Time (TAI)

Abstract : Although Coordinated Universal Time (UTC) is the time scale that is transmitted by almost all time services, this scale is awkward to use in the vicinity of a leap second. Many computer systems cannot represent the epoch corresponding to a positive leap second (23:59:60), and remain synchronized to UTC by stopping the clock at 23:59:59 for 1 extra second whenever a leap second is to be added. This makes it impossible to assign unambiguous ante tags to events that happen during this period. In addition, computing the length of a time interval that includes a leap second of either sign is difficult because simply subtracting the two UTC time stamps at die end-points of the interval does not account for the time interval occupied by the leap second itself. To address these issues, we have augmented the Network Time Protocol to allow a client system to reconstruct TAI from UTC and a table of leap seconds. This time scale has no discontinuity during the leap second. Intervals computed using TAI are unaffected by the additional time occupied by the UTC leap second, and the TAI time scale provides an unambiguous time tag to any event -- even one that happens during a UTC leap second. Although our solution is unique to servers that support the Network Time Protocol, it could be adapted to other time services and formats. Such systems could support time tags using either UTC or TAI, and would significantly reduce the problems that result from using UTC alone.