[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Time and Timing Servers
- Subject: Time and Timing Servers
- From: james.cutler at consultant.com (James R Cutler)
- Date: Thu, 11 Jul 2019 14:25:18 -0400
- In-reply-to: <1160193036.296.1562858615650.JavaMail.mhammett@ThunderFuck>
- References: <279130447.155.1562855203570.JavaMail.mhammett@ThunderFuck> <1438219743.162.1562855381650.JavaMail.mhammett@ThunderFuck> <[email protected]> <1160193036.296.1562858615650.JavaMail.mhammett@ThunderFuck>
> On Jul 11, 2019, at 11:23 AM, Mike Hammett <nanog at ics-il.net> wrote:
>
> I'll look into Meinberg.
>
> I recent thread mentioned high-sensitivity receivers often allow GPS to work inside. Obviously "inside" has a lot of definitions.
>
> I will need this facility for the TDM timing signals. It's a central office, not a datacenter.
>
> I don't know that Internet-based NTP would be accurate enough for the timing signals that I need. Maybe, maybe not.
>
My experience with Dave Mills NTP algorithm is that, giving sufficient diversity in higher stratum sources, GPS versus Internet sources makes no practical difference. This assumes that you are concerned with Time for event logging and scheduling and not concerned with frequency and phase for clocking data on TDM instances.
If you are worrying about backhoe fade â?? itâ??s consequences will most likely affect other things more strongly than Time differences.
James R. Cutler
James.cutler at consultant.com
GPG keys: hkps://hkps.pool.sks-keyservers.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190711/07bb7e3c/attachment.html>