Skip to main content
  • IETF email infrastructure transition planned for 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) is scheduled for 11 September 2026 starting at 2200UTC, with message delivery delayed up to 60 minutes. Further updates will be provided closer to the transition.

    28 Aug 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026
  • Meet our new IETF NOC Lead

    Joe Clarke has been appointed as the new IETF NOC Lead and in this post Joe introduces himself and sets out his priorities for the IETF Network.

    10 Aug 2026
  • Secretariat restructuring and staffing update

    There have been a few changes in IETF Administration LLC staffing since January of this year (2026) including the recent insourcing of the Secretariat, which are summarised here to give an overall view of the staffing structure.

    30 Jul 2026

Filter by topic and date

Filter by topic and date

Time to update the Network Time Protocol

30 Sep 2022

The Network Time Protocol (NTP) is a foundational Internet standard that has provided clock synchronization between computer systems since the early 1980s. It was first standardized as RFC 958 in Sept 1984 with several revisions in the following years. Discussions have been ongoing in the NTP working group for a few years now about updating NTPv4 to NTPv5. This update is motivated by lessons learned, ongoing vulnerabilities, and emerging use cases.

Big Ben

While the NTP has been around since the early days of the Internet, work on the NTP has been ongoing in the working group (WG) since its formation in 2005. This includes the relatively recently published “Network Time Security for the Network Time Protocol” [RFC 8915]. At the moment, the working group is considering NTP version 5, as an update to the NTP version 4 [RFC 5905] published in 2010, to accommodate new and emerging use cases and networking environments. 

The “NTPv5 use cases and requirements” Internet-Draft has been adopted by the NTP WG to help discuss the use cases, requirements, and considerations that should be factored in the design of a protocol to supersede NTP version 4. For example, the I-D describes differing situations, such as data centers where network latency or power are unlikely to be constraints, thus offering the potential for higher levels of accuracy and precision. Conversely, local networks and public internet connections  may introduce packet loss, delay, and filtering, but NTP may nonetheless be able to provide enough information for both basic time information and synchronization.

Evolving existing standards to define new capabilities to take into account new use cases and a wider variety of networking environments is one of the strengths of the IETF, and we are looking forward to the discussion within the NTP working group. We also expect to gain a good deal of insight at the upcoming IETF Hackathon on 5-6 November, where we will develop and test preliminary implementations of NTPv5 to validate discussion from the working group. If you are interested in NTP and already planning to participate in IETF 115, we would welcome your participation. If you aren’t already planning to be at the IETF Hackathon or the IETF 115 meeting, there’s still time to register!


Share this page