Response to RFC 28

[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]

UNKNOWN

Network Working Group                                   Robert Kahn
<a href="./rfc29">RFC-29</a>                                                  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:

<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">A</a>. Bhushan, MIT</span>
<span class="h2"><a class="selflink" id="appendix-S" href="#appendix-S">S</a>. Carr. Utah</span>
<span class="h2"><a class="selflink" id="appendix-G" href="#appendix-G">G</a>. Cole, SDS</span>
<span class="h2"><a class="selflink" id="appendix-S" href="#appendix-S">S</a>. Crocker, UCLA</span>
<span class="h2"><a class="selflink" id="appendix-K" href="#appendix-K">K</a>. Fry, MITRE</span>
<span class="h2"><a class="selflink" id="appendix-J" href="#appendix-J">J</a>. Heafner, RAND</span>
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">B</a>. Kahn, BBN</span>
<span class="h2"><a class="selflink" id="appendix-T" href="#appendix-T">T</a>. O'Sullivan, Raytheon</span>
<span class="h2"><a class="selflink" id="appendix-L" href="#appendix-L">L</a>. Roberts, ARPA</span>
<span class="h2"><a class="selflink" id="appendix-P" href="#appendix-P">P</a>. Rovner, LL</span>
<span class="h2"><a class="selflink" id="appendix-R" href="#appendix-R">R</a>. Stoughton, UCSB