Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!tcp-ip From: tcp-ip@ucbvax.ARPA Newsgroups: fa.tcp-ip Subject: Re: Plea for ICMP Timestamp support Message-ID: <8890@ucbvax.ARPA> Date: Tue, 9-Jul-85 00:58:11 EDT Article-I.D.: ucbvax.8890 Posted: Tue Jul 9 00:58:11 1985 Date-Received: Thu, 11-Jul-85 00:22:42 EDT Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 19 From: mills@dcn6.arpa Tracy, Several years ago we chatted up the timestamp issues and ended up with a number of proposals (see old RFCs). One of the conclusions was that simple, grumpy gateways could participate with only the barest bones of code and with only minimal protocolmanship. We could recook those conclusions handily (an x.409 IP option?!), but not without shaking the dust off the ICMP spec. Notwithstanding the above, the experience with our local-net algorithms suggests a much more important issue is the sender's estimate of the intrinsic accuracy of his clock, whether derived from power mains, local radio clock or second-hand from a UPS with a free-running 59.8-Hz oscillator. Dave -------