>> About time the NTP told the user what time is being served?
>Yes.
> It should got into an extension block.
It seems like a wild goose chase to me. We should focus on distributing UTC.
> It should got into an extension block.
> Two, one for time base, one for PPS source. ...
The PPS idea is
>
> About time the NTP told the user what time is being served?
>
Yes.
It should got into an extension block.
Two, one for time base, one for PPS source. What is the natural length of
an extension block? My preference is a US-ASCII string or a UTF8 string,
instead of a binary enum. "UTC", "U
Gary said:
> Currently I am playing with a Javad GPS that lets you set your PPS to GPS,
> SBAS, GLONASS, GALILEO, BeiDou, QZSS, IRNSS, UTC(USNO), UTC(SU), UTC(SBAS),
> UTC(GALILEO), UTC(BeiDou), UTC(QZZSS) or UTC(IRNSS)
What is the theoretical spread on all those different flavors of time? How
Yo All!
The email below is from the time-nuts mailing list, forwarded to there
from Dr. Levine. I think he works for NIST, or similar.
The discussion is about an NTP server set to UT1, not UTC. So now
we have UTC, UT1, and several varieties of leap smear being served over
NTP.
Currently I am p
