Network Time Protocols (ntp) working group - September, 17th 2024 Virtual Interim

Notes: https://notes.ietf.org/0WrKqZwTTpGbwpg864G34w

Draft Agenda

1. Administrative and Agenda Bashing (Chairs)

2. NTP/TICTOC WG Document Status Review/Update (Chairs)

https://datatracker.ietf.org/doc/draft-ietf-ntp-update-registries/
Karen: An issue that come up during IESG review has been resolved. It is now with the AD to move it forward.
Rich: Want to kown if anything is to do
Karen: that depends on Erik

https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-enterprise-profile/
It has gone through IETF LC. After that some issues still need to be resolved.

https://datatracker.ietf.org/doc/draft-ietf-ntp-over-ptp/
Waits for shephered writeup.

https://datatracker.ietf.org/doc/draft-ietf-ntp-interleaved-modes/
Has been updated and is moving forward.

3. Update from IEEE 1588 activities

Information about current activity
- 1588 par for a Client-Server PTP mode has been approved
- Possible that some of the work for PTP over NTP and NTS can be used for this purpose
- Joined meeting between security subcommittee and NTP. A further meeting shall be scheduled at the end of September or early October.
- The 1588 community is looking at some of the vulnerabilities that were identified by the NTP community and some PTP developer for the NTS for PTP draft.
- The 1588 security subcommittee is is meeting again, roughly monthly. It will try to address some of the issues that have been identified. We are attempting to have more coordination between the two groups so that we can reuse some of the materials between each group.

4. NTPv5 Requirements

https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5-requirements/
- Karen: It is not clear if this is going to be published. We want to have an additional editor for this document.
- David: What are the open points of these document.
- Karen: There are some comments which are not addressed properly.
- James: Main comments have been addressed. Will move the document to the NTP wg Github page.
- Karen: an additional editor may not necessary if we can do another round

5. NTPv5 Protocol Specification

https://datatracker.ietf.org/doc/draft-ietf-ntp-ntpv5/

• Miroslav: Issue with identification for reference clocks (ID's are not defined)
• Karen: Next f2f meeting will be in Dublin. A hackathon would be helpful.
• Miroslav: Interoperability with David is already achieved
• David: will be in Dublin for a hackathon
• David: maybe the ntpsec people are interested in making an implementation?

6. Roughtime

https://datatracker.ietf.org/doc/draft-ietf-ntp-roughtime/
https://datatracker.ietf.org/doc/draft-ietf-ntp-roughtime-ecosystem/

• Watson: Document is moved to NTP Github organisation.
• Watson: A next revision in the next couple of weeks. Hope this will be ready for WGLC
• Marcus: Regarding Kristof's helpful comments. These will be considered.
• Marcus: There are nine implementations of Roughtime, a handful of which are actively developed. Netnod is keen to do work on Roughtime and would join a hackathon in Dublin.
• David: Send some comments that are not yet addressed (re how grease is implemented by servers)
• Watson: Will provide more details and explanation in the document.

7. NTS for PTP

https://datatracker.ietf.org/doc/draft-langer-ntp-nts-for-ptp/

• Martin: No further updates. Discussed the open issues with replay protection etc with the 1588 security subcommittee.
• Karen: Update on implementation status
• Martin: Key management is nearly finished; some problems with the TLV.

Issues with Chrony in the Exporter function of NTS

• Miroslav: Shall the wg be involved in fixing this? Has it to be fixed?
• Karen: Wondering if we want to discuss it here or continue to discuss it on the mailing list.

8. AOB and Way Forward

• David: Roughtime (grease); adding cipher negotiation to NTS
• Marcus: Never heard about grease until work on Roughtime. Would like to hear about experience with using grease.
• David: Implementation side: implemented by our ntpv5 implementations
• Rich: would be great if the NTP wg grease anything. It is used heavily in TLS and QUIC.
• James: RFC 8701 covers TLS's experience with implementing grease.
• David: will make initial suggestion how to go forward
• Karen: We will plan a hackathon for Dublin. If appropriate an additional interim before Dublin.