-------- In message <[email protected]>, Rob Seaman writes: >On Jan 17, 2015, at 1:51 PM, Steffen Nurpmeso <[email protected]> wrote: > >> Maybe it would be sufficient to start at 2014, which would avoid counting >> months of 42 years > >However the data are encoded, stored or retrieved, there will be >a concept of operation that supports a variety of timekeeping / >calendar use cases. These surely include historical / retroactive >requirements.
If you need the historical information, you can afford the TCP connection to IERS. I'm focused on how NTP/PTP clients will be able to get/validate leapsecond information efficiently and reliably. >Unless there is an overriding value in efficient encoding, There is. getaddrinfo(3) is almost always available and works about as well as any protocol on the internet can work. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ LEAPSECS mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/leapsecs
