RFC 8573
Message Authentication Code for the Network Time Protocol, June 2019
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 5905
- Authors:
- A. Malhotra
S. Goldberg - Stream:
- IETF
- Source:
- ntp (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8573
Discuss this RFC: Send questions or comments to the mailing list ntp@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8573
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.