Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 0029

Response to RFC 28

Pages: 1
Unclassified

ToP   noToC   RFC0029 - Page 1
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