RFC 7821: UDP Checksum Complement in the Network Time Protocol (NTP)
In plain English — editorial summary, not part of the RFC
The Network Time Protocol (NTP) allows clients to synchronize to a time server using timestamped protocol messages. To facilitate accurate timestamping, some implementations use hardware-based timestamping engines that integrate the accurate transmission time into every outgoing NTP packet during transmission. Since these packets are transported over UDP, the UDP Checksum field is then updated to reflect this modification. This document proposes an extension field that includes a 2-octet Checksum Complement, allowing timestamping engines to reflect the checksum modification in the last 2 octets of the packet rather than in the UDP Checksum field. The behavior defined in this document is interoperable with existing NTP implementations.
Document record
- Document ID
- RFC7821
- Published
- March 2016
- Authors
- T. Mizrahi
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 14
- Also known as
- —
- Updated by:
- RFC 9748
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7820UDP Checksum Complement in the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)Current
March 2016
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 7822Network Time Protocol Version 4 (NTPv4) Extension FieldsUpdated
March 2016
- RFC 8039Multipath Time SynchronizationCurrent
December 2016
- RFC 7384Security Requirements of Time Protocols in Packet Switched NetworksCurrent
October 2014
- RFC 8573Message Authentication Code for the Network Time ProtocolUpdated
June 2019
- RFC 8633Network Time Protocol Best Current PracticesCurrent
July 2019
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 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?