Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!LOUIE.UDEL.EDU!Mills%udel.edu
From: Mills%udel.edu@LOUIE.UDEL.EDU
Newsgroups: mod.protocols.tcp-ip
Subject: Re:  Ask not for whom the chimes tinkle
Message-ID: <8701090105.a017755@Huey.UDEL.EDU>
Date: Fri, 9-Jan-87 01:05:53 EST
Article-I.D.: Huey.8701090105.a017755
Posted: Fri Jan  9 01:05:53 1987
Date-Received: Fri, 9-Jan-87 06:16:53 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Approved: tcp-ip@sri-nic.arpa

Tom,

[expletive deleted]. From the DCN1 log, it appears some NTP peer came up
claiming to be an NTP primary radio clock, but one year off, argued with
DCN1 and won. I suspect it happened during the interval immediately
following reboot and when the radio clock direclty attached to DCN1
stabilized. Although the year is initialized from the file system during
reboot, until the local radio clock engages an broken NTP peer can
latch the wrong year. DCN1 has been rebooted maybe once every two weeks,
almost always to install software updates. The spoof window lasts maybe
a minute. What can I say? Yes, the window can probably be shut.

Independent, operational radio clocks are presently at DCN1 (128.4.0.1),
UMD1 (128.8.0.1) and FORD1 (128.5.0.1). The new NCAR clock is probably
best left alone until the NSFnet Backbone configuration changes have
completely stabilized. What these should do is provide up to six NTP
"servers" on various campus nets, all slaved to NCAR and will avoid
congestion on the network links serving NCAR itself.

Dave