On Feb 11, 2015, at 7:08 AM, Rob Seaman <sea...@noao.edu> wrote: > For my current encoding, PHK's CRC keeps the final octet out of harm's way: > > 255.255.255.47 -> OK 2142 8 127 -1 (1, 1) > > As shown, the first three 255s would require a negative leap second at the > end of July 2142 with a specific prior offset. It might be a bit pedantic to > worry about this explicitly ;-) Other encodings might be more likely but we > can choose a CRC/SHA that avoids it.
More pedantically yet, the required prior offset (128 sec) is out of range so you can't get there in the first place. _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com https://pairlist6.pair.net/mailman/listinfo/leapsecs
