Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uwm.edu!bionet!agate!ucbvax!SAYSHELL.UMD.EDU!louie
From: louie@SAYSHELL.UMD.EDU ("Louis A. Mamakos")
Newsgroups: comp.protocols.time.ntp
Subject: Re: Running NTP at Verdix.Com
Message-ID: <9103192032.AA09380@sayshell.umd.edu>
Date: 19 Mar 91 20:32:39 GMT
Article-I.D.: sayshell.9103192032.AA09380
References: <9103192021.AA17181@Verdix.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 13


Sounds reasonable to me.  Since UUNET is synchronized to UMD1
directly, you might just want to synchronize with them only and not
increase the already heavy load on UMD1 any further.

Unless you are going to redistrubute time to a large number of other
hosts, you should pick a few normally stratum-2 servers, like UUNET
and one or two other stratum-2 machines to peer with.  That will
reduce the load on the stratum-1 servers which are already
over-burdened with too many peers.  The sychronization paths are too
heavily concentrated at the stratum-1 servers.

louie