metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 8573: Message Authentication Code for the Network Time Protocol

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 (NTP), as described in RFC 5905, states that NTP packets should be authenticated by appending NTP data to a 128-bit key and hashing the result with MD5 to obtain a 128-bit tag. This document deprecates MD5-based authentication, which is considered too weak, and recommends the use of AES-CMAC as described in RFC 4493 as a replacement.

Document record

Document ID
RFC8573
Published
June 2019
Authors
A. Malhotra; S. Goldberg
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
5
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/8573-message-authentication-code-for-the-network-time-protocol