[Context is "simple NTP broadcast client"]
> The primary target audience is IoT devices. Expect nothing impressive in
> terms of timekeeping precision.
I like the idea of a small/simple implementation.
There are 2 parts to a ntp client. One is getting the time right. The other
is calibrating
dfoxfra...@gmail.com said:
> >> The diag dump "nameless horror" shall be removed from NTPsec.
>> What is that? I don't recognize the term.
> Support for the ntpq saveconfig command. The term is a joke from the meeting
> because it took five minutes before any of us could remember what it was
> ca
Resent copying the list this time.
On 5/3/16, Hal Murray wrote:
>
>> A from-scratch proven and verified C implementation of "simple NTP
>> broadcast
>> client" will be written. Lead on that project will be Daniel.
>
> Could you say a bit more? How "simple"? What does "verified" mean?
For the
> A from-scratch proven and verified C implementation of "simple NTP broadcast
> client" will be written. Lead on that project will be Daniel.
Could you say a bit more? How "simple"? What does "verified" mean?
What are you expecting in the way of timekeeping accuracy and/or glitch
avoidance
