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
Context & Ripple Effects
The New Yorker profile lands at a hinge moment for one of the internet's oldest load-bearing protocols. David Mills wrote NTP in the 1980s and kept it running for decades, but [[a:827334|2015 reporting flagged how much of the open-source implementation rested on one overworked project lead]] — the classic bus-factor problem for infrastructure everyone depends on and few pay attention to.
The counterweight is institutional: about two dozen IETF contributors are now working toward NTPv5, moving stewardship from a single author toward the standards process. Later coverage of Mills's death in January 2024 makes the handoff concrete — the protocol's future no longer runs through its creator.
First-order effects
- The roughly two dozen IETF contributors on NTPv5 take over design authority for time synchronization from Mills, converting a personal project into a committee-owned standard.
Second-order effects
- Distributing maintenance across the IETF answers the single-maintainer fragility documented in 2015, reducing the risk that a critical internet function stalls on one volunteer's availability.
Third-order effects
- If the pattern holds, the internet's founding protocols will complete a generational transfer from creator-maintained code to community governance — the same arc visible in Vint Cerf's work on delay-tolerant networking for space, where the original TCP/IP generation is extending its protocols rather than merely defending them.
The trend: The internet's foundational protocols are shifting from the stewardship of their original authors to institutional, community-maintained standards as that founding generation ages out.