Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!mailrus!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!mstar!mstar.morningstar.com!bob
From: bob@MorningStar.Com (Bob Sutterfield)
Newsgroups: news.software.nntp
Subject: Re: When was last?
Message-ID: <BOB.89Dec7131357@volitans.MorningStar.Com>
Date: 7 Dec 89 18:13:57 GMT
References: <1989Dec7.050042.18935@ux1.cso.uiuc.edu>
Sender: news@MorningStar.COM (USENET Administrator)
Reply-To: bob@MorningStar.Com (Bob Sutterfield)
Organization: Morning Star Technologies
Lines: 11
In-reply-to: peltz@cerl.uiuc.edu's message of 7 Dec 89 05:00:42 GMT

NNTP is the wrong place to manage or communicate time if you intend to
use the time for something that matters to you.   If two machines each
care what time the other has, they should  use  NTP to coordinate with
each other, and themselves to an outside standard Real Time.  The news
software  should  only need  to  worry about whatever its  local clock
claims the time to be.

Are there any   existing or  projected  uses  of netnews that  require
sub-millisecond  time coordination between  two hosts?  If so, how  do
you  tell  whether  or not  you've  achieved  it  if  you're not using
something at least as good as NTP?