Path: utzoo!utgpu!watserv1!watmath!att!att!linac!uwm.edu!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: roeber@cithe2.cithep.caltech.edu (Frederick Roeber)
Newsgroups: comp.dcom.telecom
Subject: Time Protocol, was Re: AT&T ISDN Set Question
Message-ID: <14292@accuvax.nwu.edu>
Date: 3 Nov 90 19:37:03 GMT
Sender: news@accuvax.nwu.edu
Organization: California Institute of Technology, Pasadena
Lines: 17
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 787, Message 8 of 12


In article <14267@accuvax.nwu.edu>, coffland@roxanne (Doug Coffland)
writes:

> Another shortfall is that the time provided across a packet network
> whether it originates from a peripheral applications processor or from
> the ISDN itself is subject to error equal to packet delay across the
> network.

RFC-1059 "Network Time Protocol (NTP)" describes (or at least points
to the paper describing) the algorithm used to solve this problem in
the IP network time protocol.  Last I checked, RFC's can be ftp'd
from nic.ddn.mil.


Frederick G. M. Roeber | e-mail: roeber@caltech.edu or roeber@vxcern.cern.ch
r-mail: CERN/SL-CO, 1211 Geneva 23, Switzerland | telephone: +41 22 767 5373