News

Network Time Protocol Updated for Improved Granularity, IPv6

Internet Engineer Task Force (IETF) engineers are sharpening the Network Time Protocol's (NTP) granularity of time measurements, as well as making the veritable time-synchronization standard compatible with version 6 of the Internet Protocol.

An IETF Internet Draft, "Network Time Protocol Version 4 Protocol and Algorithms Specification," which was posted last month, encapsulates the changes.

The NTP Working Group hopes to submit this draft for consideration as an IETF Request for Comments (RFC) within the next few weeks, according to working group co-chair Karen O'Donoghue, lead engineer for the Naval Sea Command's Surface Warfare Center. O'Donoghue led the working group discussion at the IETF 71st meeting being held in Philadelphia this week.

Once this update to NTP is published as a RFC, vendors can incorporate the changes into their own network software and hardware.

NTP is widely used to synchronize clocks across the Internet. Using NTP, local machines can query regional time servers, which in turn get the Universal Coordinated Time over the Internet from highly accurate reference clocks. Using algorithms to estimate the offset caused by transmission times, the current version of NTP can synchronize local time with a reference clock to within a few hundred milliseconds, an accuracy that may be maintained by checking the time server every 1,024 seconds.

This new NTP update includes algorithms that would bring the accuracy to within tens of milliseconds, and can maintain this accuracy up to 36 hours between checks with the time server. Such precision has become increasingly necessary for modern systems.

This draft also includes support for IPv6. It specifies the IPv6 address to be used for NTP multicast transmissions, as specified by Internet Assigned Numbers Authority. It also specified changes in the packet headers for IPv6 transmissions.

In addition to this draft, the NTP working group has a few others in the final stages of being readied for IETF submission. One is on using encrypting NTP packets through the Public Key Infrastructure. Another details how to use NTP with the Dynamic Host Control Protocol within IPv6. A third details metrics for monitoring components that use NTP.

The changes in this document will still fall under version 4 of NTP, although discussions are about to get underway to talk about future versions of the protocol, O'Donoghue said during the meeting.

About the Author

Joab Jackson is the chief technology editor of Government Computing News (GCN.com).

Featured

  • Secured-Core PCs Promise To Stop Malware at the Firmware Level

    Microsoft and its hardware partners recently described new "Secured-core" PCs, which add protections against firmware-based attacks.

  • How To Ransomware-Proof Your Backups: 4 Key Best Practices

    Backups are the only guaranteed way to save your data after a ransomware attack. Here's how to make sure your backup strategy has ransomware mitigation built right in.

  • Microsoft Buys Mover To Aid Microsoft 365 Shifts

    Microsoft announced on Monday that it bought Mover to help organizations migrate data and shift to using Microsoft 365 services.

  • Microsoft Explains Windows 7 Extended Security Updates Setup Process

    Microsoft this week described installation instructions for volume licensing users of Windows 7 Service Pack 1 to get Extended Security Updates (ESU) activated on PCs.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.