From: druck@.afit.af.mil  (Dennis W. Ruck)
Subject: Re: A site for syncing my nettime (timed)
Reply-To: druck@afit.af.mil (Dennis W. Ruck)
Organization: Air Force Institute of Technology
Date: Thu, 19 Nov 1992 17:43:10 GMT

masud cader writes
>Is there a site on the Internet which keeps time.  I would like to sync my  
>master timekeeper with something reliable on the net (Atomic clock anyone?).
>
>Thanks.  Please reply to mcader@worldbank.org

Here is the header portion of a file (clock.txt) I downloaded from somewhere. I  
think it was louie.udel.edu. The list of time servers is too large to post  
(IMHO). You should contact your site administrator. They may already be syncing  
to other time servers in which case you can sync off of a local machine.

========================================================================
= Information on NTP Time Servers and Radio Timecode Receivers         =
= This update 6 July 1992, last update 29 May 1992                     =
========================================================================

General Information

This file is provided for information purposes only and represents the
best information available at the date posted above. It does not
represent a commitment to provide connectivity or time service on the
part of the operators involved. Further information of a technical
nature can be obtained from the ntp@trantor.umd.edu list. To subscribe
to this list, contact ntp-request@trantor.umd.edu (Louie Mamakos).
Alternatively, if possible, please subscribe to the USENET newsgroup
comp.protocols.time.ntp which is gatewayed to the mailing list.

Time Servers

As the load on the hosts supporting NTP primary time (stratum 1) service
is heavy and always increasing, clients should avoid using the primary
servers whenever possible. In most cases the accuracy of the secondary
servers is only slightly degraded relative to the primary servers and,
as a group, the secondary servers may be just as reliable. As a general
rule, a client should use a primary server only under the following
conditions:

1.   The server provides synchronization to a sizable population of
     clients on the order of 100 or more.

2.   The server operates with at least two and preferably three other
     servers in a common synchronization subnet designed to provide
     reliable service even if some servers or the lines connecting them
     fail.

3.   The administration(s) that operates the subnet coordinates other
     clients within the region service is provided in order to reduce
     the resources required outside that region. Note that at least some
     interregional resources are required in order to ensure reliable
     service.

In order to ensure reliability, clients should spread their use over
many different servers. As a general rule, no more than two clients per
network should use the same server on another network; however, in order
to simplify management of host configuration tables, many hosts on the
same network may use the same (redundant) servers on the same network.
Further information on client configuration can be found in the file
pub/ntp/doc/ntpinfo.Z and in the documentation in the NTP Unix daemon
distributions ntp.3.4 and xntp in the pub/ntp directory on
louie.udel.edu.

Following is a list of NTP primary and secondary time servers known to
be connected to the Internet and may be available for external access.
Each entry gives the host name, Internet address, approximate location
and geographic coordinates if available, synchronization source
(stratum, type of radio or satellite receiver and host type), suggested
service area, access policy (as notified) and contact name and e-mail
address. It is always wise to consult the DNS to verify host addresses,
which are changed from time to time. When more than one address is
given, preference should given to each in order. All servers are
equipped with uncompensated crystal-stabilized timebases, unless
indicated otherwise.

The contact person should always be notified upon establishment of
regular operations with servers listed as open access. Please respect
the access policy as stated by the contact person. Servers listed as
closed access should NOT be used without prior permission, since this
may disrupt ongoing research in which these servers are involved.


--
Dennis W. Ruck               Air Force Institute of Technology
druck@afit.af.mil            Wright-Patterson AFB, Ohio
                             (NeXTmail Welcome)
Newsgroups: comp.sys.next.sysadmin