A profile of David Mills, who created the Network Time Protocol in the 1980s, as about two dozen Internet Engineering Task Force contributors work toward NTPv5
An obscure software system synchronizes the network's clocks. Who will keep it running? — In 1977, David Mills … Tweets: @hkanji , @nicolasnova , @yminsky , @hannahseidlitz , @uhoelzle , and @rlove Tweets: Hussein Kanji / @hkanji : A contest for influence over how clocks are kept in synch across the Internet has begun https://www.newyorker.com/... @nicolasnova : Such a fascinating topic, especially for people into Science and Technology Studies/Anthropology: The Thorny Problem of Keeping the Internet's Time | The New Yorker https://www.newyorker.com/... @yminsky : This was an interesting and sad story about David Mills and the evolution of NTP. It highlights the sometimes odd histories and personalities around the fundamental technologies of the Internet. https://www.newyorker.com/... @hannahseidlitz : fact-checking this piece I got to talk to like, ten of the reclusive octogenarian dudes who invented the internet and beg them to explain computer science to me like I'm a five-year-old. it was awesome. time is nuts, the earth is speeding up, @NDHopper is brilliant; worth reading https://twitter.com/... @uhoelzle : Great weekend reading: the history of NTP, keeping clocks synchronized across the internet. https://www.newyorker.com/... Robert Love / @rlove : The history of NTP — and its future https://www.newyorker.com/...
Context & Ripple Effects
This profile lands at a hinge moment for a piece of plumbing almost nobody thinks about: the Network Time Protocol, which David Mills built in the 1980s and which still synchronizes clocks across the Internet. The reporting follows about two dozen IETF contributors drafting NTPv5 — the first serious attempt at a successor in decades — and asks the question the coverage has been circling since [[a:827334|2015 reporting showed the widely-used open source project resting on one overworked maintainer]].
The stakes became literal after the profile ran: Mills died in January 2024 at age 85, leaving the protocol's future entirely to the community around it. Meanwhile the biggest clock consumers aren't waiting — Meta, Google, Microsoft, and Amazon have already lined up behind NIST's push to scrap the leap second, signaling that hyperscale operators now treat timekeeping as infrastructure they need to steer.
First-order effects
- The roughly two dozen IETF contributors working on NTPv5 get a rare spotlight, along with the governance question the profile forces into the open: a protocol running the world's clocks has no clear institutional owner.
- Mills, elderly and no longer able to carry the project, sees his life's work become a case study in succession risk for foundational software.
Second-order effects
- Hyperscalers with acute time-sync needs — the same four pushing leap-second abolition — face pressure to fund or formally adopt NTP's maintenance rather than depend on volunteer labor, the way they've moved on other shared dependencies.
- Any NTPv5 standardization fight now doubles as an influence contest over how Internet time is kept, drawing vendors and cloud operators into the IETF process.
Third-order effects
- If the pattern holds, critical Internet protocols age out of their creators' hands and migrate toward institutionalized stewardship — foundations, funded working groups, corporate sponsorship — because 'one overworked maintainer' is no longer an acceptable failure mode for global infrastructure.
- Timekeeping itself consolidates as a strategic layer: whoever controls clock distribution controls certificate validity, log ordering, and coordination for everything built above it.
The trend: Foundational Internet protocols are shifting from lone-volunteer stewardship toward institutionalized, corporate-adjacent maintenance as their original maintainers age out.