I hadn't run across NIST's leap seconds table before:

I'm finally beginning to catch up on NTP developments over the last
several years, and find that current xntpd code can use that table,
and transport leap second tables around using an "autokey" feature:


There is an IETF NTP working group now:


There was some discussion of leap seconds at the NTP working group
session of the Internet Engineering Task Force (IETF) meeting in
Vancouver in September:


It is unclear whether the current "autokey" security mechanism will
end up in an IETF standard, since it is rather different from other
standard internet security mechanisms.

That meeting also mentions IEEE 1588-2002 Standard for a Precision
Clock Synchronization Protocol for Networked Measurement and Control
Systems.  See

It seems that IEEE 1588 time bases are continuous from a defined
epoch, but I don't know much more about that.

There was also a note in the IETF meeting of possible leap second
issues in the RTP protocol.

There was later discussion on the NTP working group mail list
about sending in comments to the ITU.  Here is Steve Allen's
comment, cogent as always, and links to the rest:


I don't know if they ever sent in comments to ITU.

Neal McBurnett                 http://bcn.boulder.co.us/~neal/
Signed and/or sealed mail encouraged.  GPG/PGP Keyid: 2C9EBA60

Reply via email to