RFC 8877: Guidelines for Defining Packet Timestamps

Various network protocols make use of binary-encoded timestamps that are incorporated in the protocol packet format, referred to as "packet timestamps" for…

Read RFC 8877 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Informative reference — RFC 3550: RTP: A Transport Protocol for Real-Time Applications
Informative reference — RFC 5905: Network Time Protocol Version 4: Protocol and Algorithms Specification
Informative reference — RFC 3339: Date and Time on the Internet: Timestamps
Informative reference — RFC 6991: Common YANG Data Types
Informative reference — RFC 5646: Tags for Identifying Languages
Informative reference — RFC 7011: Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information
Informative reference — RFC 5357: A Two-Way Active Measurement Protocol (TWAMP)
Informative reference — RFC 4656: A One-way Active Measurement Protocol (OWAMP)
Informative reference — RFC 6374: Packet Loss and Delay Measurement for MPLS Networks
Informative reference — RFC 7323: TCP Extensions for High Performance
Informative reference — RFC 7493: The I-JSON Message Format
Informative reference — RFC 7384: Security Requirements of Time Protocols in Packet Switched Networks
Informative reference — RFC 6019: BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
Informative reference — RFC 7456: Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)
Informative reference — RFC 8186: Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol (TWAMP)

Incoming relationships (3 related RFCs)

Normatively referenced by — RFC 9192: Network Service Header (NSH) Fixed-Length Context Header Allocation
Normatively referenced by — RFC 9578: Privacy Pass Issuance Protocols
Informatively referenced by — RFC 9145: Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context Headers