diff options
author | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
---|---|---|
committer | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
commit | 4bfd864f10b68b71482b35c818559068ef8d5797 (patch) | |
tree | e3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc29.txt | |
parent | ea76e11061bda059ae9f9ad130a9895cc85607db (diff) |
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc29.txt')
-rw-r--r-- | doc/rfc/rfc29.txt | 43 |
1 files changed, 43 insertions, 0 deletions
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 |