|
RFC Home |
Full RFC Index |
Recent RFCs |
RFC Standards |
Best Current Practice |
RFC Errata |
1 April RFC |
|
||||||
|
IETF RFC 29
Response to RFC 28 Last modified on Friday, May 11th, 2001 Permanent link to RFC 29 Search GitHub Wiki for RFC 29 Show other RFCs mentioning RFC 29 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 Response to RFC 28 RFC TOTAL SIZE: 912 bytes PUBLICATION DATE: Friday, May 11th, 2001 LEGAL RIGHTS: The IETF Trust (see BCP 78) |