Packet switching affects time transfer, not time keeping. If your NTP server is clocked with a stable source, it should keep the correct time within the accuracy of your clock source. In the case of Rb, this is about one second in three thousand years. Or better than +/- 1 us/day. Using a better clock should not affect how closely sync'ed your NTP server is to another one.
Rb oscillators are $250-$500 (LPRO) on ebay, a good OCXO is <$50. cheers, glenn John C Nordlie wrote: >Yes John, I'd be interested. I'd also be curious how inexpensivly >this could be integrated with a TCXO or OCXO to stabilize a >network-only NTP server. That also begs the question if the jitter >caused by packet-switching would make such a network-only NTP server >worth the effort to stabilize to that degree. > >By 'network-only' I mean an NTP server that would get its time >information from a stratum-1 NTP server (no GPS, WWV, etc). > > > >>Date: Wed, 16 Aug 2006 16:49:22 -0400 >>From: John Ackermann N8UR <[EMAIL PROTECTED]> >>Subject: [time-nuts] Query: Interest in clock synthesizer module -- >> useful for stabilizing PC timekeeping (among other things) >> >>I'm working on a project for TAPR (http://www.tapr.org) that might be of >>interest to the timekeeping community. >> >> ><snip> > > >_______________________________________________ >time-nuts mailing list >time-nuts@febo.com >https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > _______________________________________________ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts