metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 7822: Network Time Protocol Version 4 (NTPv4) Extension Fields

Still current, but amended. Parts of this document are changed or extended by RFC 9748. Read both.

In plain English — editorial summary, not part of the RFC

The Network Time Protocol version 4 (NTPv4) defines the optional usage of extension fields. An extension field, as defined in RFC 5905, is an optional field that resides at the end of the NTP header and that can be used to add optional capabilities or additional information that is not conveyed in the standard NTP header. This document updates RFC 5905 by clarifying some points regarding NTP extension fields and their usage with Message Authentication Codes (MACs).

Document record

Document ID
RFC7822
Published
March 2016
Authors
T. Mizrahi; D. Mayer
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
8
Also known as
—
Updates:
RFC 5905
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.

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?

canonical URL: /rfc/7822-network-time-protocol-version-4-ntpv4-extension-fields