[ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ]

Alternate Formats: rfc29.txt | rfc29.txt.pdf

RFC 29 - Response to RFC 28


    Search the Archives
Display RFC by number
    


RFC29 - Response to RFC 28

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

 

Previous: RFC 0028 - Time Standards

 

Next: RFC 0030 - Documentation Conventions

 


[ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ]

© 2008 FAQS.ORG. All rights reserved.