Four timestamps
03Two local timestamps and two remote timestamps let a client separate server processing time from network travel.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 8 ↗
RFC 5905 · § 8EXAMPLE
3 / 3
03
Record client arrival.
The client measures T4 locally and now has the four timestamps needed for calculation.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Record each boundary with the correct clock.
- T1 and T4 are measured by the client; T2 and T3 by the server.
- The reply returns the original request timestamp along with the server receive and transmit timestamps.
- The destination timestamp is captured locally on receipt, rather than being trusted from the server.
The two lifelines show the client and server clocks; T1 through T4 mark send and receive events. Timestamp placement near packet transmission and reception reduces avoidable measurement error.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy