RFC 8877: Guidelines for Defining Packet Timestamps
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8877
- Published
- September 2020
- Authors
- T. Mizrahi; J. Fabini; A. Morton
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7323TCP Extensions for High PerformanceCurrent
September 2014
- RFC 3522The Eifel Detection Algorithm for TCPCurrent
April 2003
- RFC 3339Date and Time on the Internet: TimestampsUpdated
July 2002
- RFC 8882DNS-Based Service Discovery (DNS-SD) Privacy and Security RequirementsCurrent
September 2020
- RFC 8883ICMPv6 Errors for Discarding Packets Due to Processing LimitsCurrent
September 2020
- RFC 8885Proxy Mobile IPv6 Extensions for Distributed Mobility ManagementCurrent
October 2020
- RFC 8900IP Fragmentation Considered FragileCurrent
September 2020
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?