I suggest we add a Time Sync Standard Op to the Haystack protocol. We then would add this to nHaystack as well, so that we can sync Niagara or other Haystack servers.

Anythoughts?

If you wanted a client to query time from a Haystack server, you can just use the about op which already includes a serverTime field

We don't want to just read the time, we want to push the Time. Should we just do this in our own implementation of haystack, or should we standardize this. We could just add this to FIN Stack, and nHaystack and then worry about it later.

The goal would be that a 3rd party could sync a haystack device with their own time.

I doubt you want to implement your own time sync - you will need to deal with stuff like latency and drift. Why not just use something existing like ntp?

I like ntp too, but imagine there is a Inferstack server connected to 50 Inferstack devices, and 50 Jace Devices. Those devices don't have an internet connection but the server does, so the server would sync with ntp, but then it would push out the times to all the devices over haystack.

InferStack would be easy - because all IS devices support NTP out of the box. So you can just run ntpd on your server and have all devices pick up time up from there (or tunnel a public ntp server thru your server).