RFC 9748: Updating the NTP Registries
In plain English — editorial summary, not part of the RFC
The Network Time Protocol (NTP) and Network Time Security (NTS) documents define a number of registries, collectively called the NTP registries. Some registries are correct, but some include incorrect assignments and some don't follow common practice. For the sake of completeness, this document reviews all NTP and NTS registries, and corrects the registries where necessary. This document updates RFCs 5905, 5906, 7821, 7822, and 8573.
Document record
- Document ID
- RFC9748
- Published
- February 2025
- Authors
- R. Salz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9281Entities Involved in the IETF Standards ProcessCurrent
June 2022
- RFC 9769NTP Interleaved ModesCurrent
May 2025
- RFC 9523A Secure Selection and Filtering Mechanism for the Network Time Protocol with KhronosCurrent
February 2024
- RFC 9327Control Messages Protocol for Use with Network Time Protocol Version 4Current
November 2022
- RFC 9249A YANG Data Model for NTPCurrent
July 2022
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
- RFC 8633Network Time Protocol Best Current PracticesCurrent
July 2019
- RFC 8039Multipath Time SynchronizationCurrent
December 2016
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?