NTP Working Group @ IETF 125

Shenzhen, March 14 - 20, 2026
Tuesday, 17 March 2026
11:30 - 12:30 (UTC + 8 )
Auditorium

Agenda

1. Administrative

• Note well
• AD Transition: Erik Kline is stepping down as the Area Director (AD) after six years. Tommy Jensen will take over as the incoming AD for the NTP working group.

2. NTP WG Documents (beyond the working group)

• The NTP over PTP document is currently in the RFC Editor queue.
• The Roughtime document is nearing completion, with only one remaining IESG discuss to clear.

Working Group Documents

3. NTPv5 (https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5/)

draft-ietf-ntp-ntpv5 (Network Time Protocol Version 5):
* A recent update was published. Miroslav Lichvar identified four remaining issues on the mailing list.
* The chairs called for more reviews as the document matures.
* A virtual interim and a Vienna Hackathon project are planned to further this work.

4. NTS for PTP (https://datatracker.ietf.org/doc/draft-ietf-ntp-nts-for-ptp/)

draft-ietf-ntp-nts-for-ptp (Network Time Security for the Precision Time Protocol):
* Martin Langer reported the draft is nearly finished, with Security and IANA considerations still needing completion.
* The draft is being aligned with ongoing developments in the IEEE 1588 security subcommittee. Finalization is expected this year.
* The PoC implementation requires modification to align with the current version of the document.

5. NTS for NTP pools (https://datatracker.ietf.org/doc/draft-venhoek-nts-pool/)

• The working group has adopted this as an experimental RFC to document the current ongoing experiment.
• A new version must be submitted under the official working group name.

Individual Submissions

6. NTPv5 Algorithms (https://datatracker.ietf.org/doc/draft-grant-ntp-ntpv5-algorithms/)

It was decided to let this document expire for now and revisit it once the core NTPv5 protocol is further along.

7. Timestamp extension field (https://datatracker.ietf.org/doc/draft-tang-ntp-ntpv5-extension-field/)

• More discussion on the mailing list is required

8. NTP DNS Resource Record (https://datatracker.ietf.org/doc/draft-yuki-ntp-dns-record/)

• More discussion on the mailing list is required

9. Hardware-Rooted Attestation for Precision Time Protocol: Scalable Workload Identity and Phased PQC Readiness (https://datatracker.ietf.org/doc/draft-ramki-ptp-hardware-rooted-attestation)

• Presentation:
  Hardware-Rooted Attestation for PTP
  https://datatracker.ietf.org/doc/slides-125-ntp-hardware-rooted-attestation-for-ptp/

• Discussion

  • Diego Lopez presented a proposal to use hardware roots of trust (like TPMs) and Merkle trees to attest to the integrity and geographical location of PTP messages without impacting timing sensitivity.
  • The goal is to provide non-repudiation and prepare for Post-Quantum Cryptography (PQC).
  • Discussion ensued regarding whether this work belongs in the NTP WG or the RATS (Remote ATtestation ProcedureS) WG. Karen O'Donoghue and Erik Kline recommended engaging with Security ADs to determine the most appropriate working group for this work.
  • Karen O'Donoghue is interested in receiving feedback from the IEEE P1588 security subcommittee.

10. IEEE 1588 Update

• CSPTP (Client-Server PTP): Work is continuing, but currently blocked by an architectural decision regarding one-step versus two-step clocks. Once resolved, NTS for CSPTP will be integrated.
• NTS for PTP: Progress continues in the 1588 security subcommittee, with draft access available for reviewers upon request to the chairs.
• F2F meeting on June

AOB

• Virtual Interim: A virtual meeting will be scheduled between IETF 125 and IETF 126 (Vienna) to focus on draft-ietf-ntp-ntpv5.
• IETF 126 Hackathon: Planning to host hackathon projects for NTPv5 and NTS for PTP in Vienna.
• Security Coordination: Incoming AD Tommy Jensen will assist in socializing the hardware-rooted attestation proposal with the Security Area to determine the best path forward.
• Adjourned: 11:55

Decisions and Action Items

• NTPv5 Algorithms: Sarah Grant will let the current individual draft expire.
• NTS for NTP Pools: Authors to submit the next version as a working group document.
• NTPv5 Reviews: Working group members are encouraged to review the four issues identified by Miroslav Lichvar on the mailing list.