Guidelines for Defining Packet Timestamps
RFC 8877, “Guidelines for Defining Packet Timestamps”, is an Informational document published in September 2020 by T. Mizrahi, J. Fabini, A. Morton. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8877 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8876 Non-interactive Emergency Calls
- RFC 8875 Working Group GitHub Administration
- RFC 8879 TLS Certificate Compression
- RFC 8874 Working Group GitHub Usage Guidance
- RFC 8880 Special Use Domain Name 'ipv4only.arpa'
- RFC 8881 Network File System Version 4 Minor Version 1 Protocol
- RFC 8882 DNS-Based Service Discovery Privacy and Security Requirements
- RFC 8883 ICMPv6 Errors for Discarding Packets Due to Processing Limits