[LEAPSECS] stale leap second information

Hal Murray hmurray at megapathdsl.net
Tue Jan 20 00:07:07 EST 2015

> If you are only broadcasting the next or just recently occurred leap second,
> you can perhaps leave out the year and just give a month number, which is
> understood to be in a -2 .. +10 window around the current month. e.g. if I
> read a month number of 12 now I would understand that to mean there was a
> leap second at the end of last year, but if I read the same value in March I
> would understand there is a leap second at the end of this year. 

I don't think -2..10 is good enough.  What if none is scheduled and the last 
one was a year ago?

If nothing else, you need to reserve one code point for "none scheduled".

These are my opinions.  I hate spam.

More information about the LEAPSECS mailing list