[ntpwg] Comments on NTP draft -06

[M. Warner Losh]

In message: <46841C64.5090504 at udel.edu>
            "David L. Mills" <mills at udel.edu> writes:
: A small number of issues remain, such as what to do about expired 
: leapsecond files, what to do if the leapsecond information is downloaded 
: from a crypto server, etc. The paint ain't quite dry yet.

Funny you should mention the 'what to do if the leapsecond information
is expired' cased.  I'm looking into a bug in that area.  Last
summer's leap second tables have expired today, leading to some
unexpected bugs in the code that I maintain...  We have a need to know
leap information in our application, so we use the NIST format to
store the data...

I noticed that the NIST leapsecond.list file was updated in early May
to expire in june 2008, several weeks before bulletin C34 came out
making it official that there's no leap second this December.  I can
only assume that the folks at NIST have an inside track on information
about future leaps :-)

Thanks for the update on the code.  I've read the leap second part of
the udel ntpd code far too many times over the past 8 years, but I've
managed to escape that chore for about two years now...

Warner