Skip to main content

Message Authentication Code for the Network Time Protocol
RFC 8573

Revision differences

Document history

Date By Action
2019-10-18
Bernie Volz Closed request for Early review by INTDIR with state 'Overtaken by Events'
2019-10-18
Bernie Volz Assignment of request for Early review by INTDIR to Hui Deng was marked no-response
2019-08-19
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2019-08-19
Gunter Van de Velde Assignment of request for Last Call review by OPSDIR to Tim Wicinski was marked no-response
2019-06-23
(System)
Received changes through RFC Editor sync (created alias RFC 8573, changed abstract to 'The Network Time Protocol (NTP), as described in RFC 5905, …
Received changes through RFC Editor sync (created alias RFC 8573, changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-06-23, changed IESG state to RFC Published, created updates relation between draft-ietf-ntp-mac and RFC 5905)
2019-06-23
(System) RFC published