RFC 8877

Guidelines for Defining Packet Timestamps, September 2020

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
INFORMATIONAL
Authors:
T. Mizrahi
J. Fabini
A. Morton
Stream:
IETF
Source:
ntp (int)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8877

Discuss this RFC: Send questions or comments to the mailing list ntp@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8877


Abstract

Various network protocols make use of binary-encoded timestamps that are incorporated in the protocol packet format, referred to as "packet timestamps" for short. This document specifies guidelines for defining packet timestamp formats in networking protocols at various layers. It also presents three recommended timestamp formats. The target audience of this document includes network protocol designers. It is expected that a new network protocol that requires a packet timestamp will, in most cases, use one of the recommended timestamp formats. If none of the recommended formats fits the protocol requirements, the new protocol specification should specify the format of the packet timestamp according to the guidelines in this document.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search