From 4bfd864f10b68b71482b35c818559068ef8d5797 Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Wed, 27 Nov 2024 20:54:24 +0100 Subject: doc: Add RFC documents --- doc/rfc/rfc29.txt | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 doc/rfc/rfc29.txt (limited to 'doc/rfc/rfc29.txt') diff --git a/doc/rfc/rfc29.txt b/doc/rfc/rfc29.txt new file mode 100644 index 0000000..1c5779b --- /dev/null +++ b/doc/rfc/rfc29.txt @@ -0,0 +1,43 @@ +Network Working Group Robert Kahn +RFC-29 BBN + 19 January 1970 + + + + + +This note is in response to Bill English's Request for Comments: 28. + +A "millisecond" clock should be satisfactory for most network measurements. +Round-trip message transit times typically should be at least on the +order of tens to hundreds of milliseconds. The IMP contains a 16-bit +hardware clock which is incremented every 100 microseconds to allow for +timing of internal events within the IMP, as for example, during tracing. +However, most measurements are made using a 25.6 ms. software clock. + + + + + + + + + + + + + + +DISTRIBUTION: + +A. Bhushan, MIT +S. Carr. Utah +G. Cole, SDS +S. Crocker, UCLA +K. Fry, MITRE +J. Heafner, RAND +B. Kahn, BBN +T. O'Sullivan, Raytheon +L. Roberts, ARPA +P. Rovner, LL +R. Stoughton, UCSB \ No newline at end of file -- cgit v1.2.3