Time Synchronization over QUIC

Abstract

This document proposes a modern, secure, and extensible time synchronization protocol designed to operate over the QUIC transport protocol. Known as TSQ (Time Synchronization over QUIC), this protocol aims to address the limitations of traditional NTP by leveraging QUIC's encryption, widespread UDP/443 acceptance, and multiplexed stream capabilities. TSQ is designed for contemporary deployment environments, including enterprise networks, cloud-native systems, containers, and mobile devices, where traditional UDP-based NTP struggles with security, scalability, or operational reliability.¶

1. Introduction

Time synchronization is foundational to modern computing. It underpins authentication systems, log correlation, distributed transactions, and more. NTP, the current standard, was designed in a different era and brings challenges related to security, deployment compatibility, and extensibility. TSQ is proposed as a new protocol built directly on top of QUIC, leveraging its modern transport features to provide secure, authenticated, and operationally-friendly time synchronization.¶

2. Scope and Goals

TSQ is intended to:¶

• Provide secure and authenticated time synchronization¶

• Support modern deployment scenarios¶

• Operate in environments where UDP/123 is blocked¶

• Be extensible and future-proof¶

• Scale for enterprise and cloud¶

TSQ is not intended to:¶

• Replace NTP in ultra-precise or constrained devices¶

• Replace public NTP infrastructure without optimization¶

3. Protocol Overview

TSQ uses QUIC as its transport, establishing secure, short-lived connections. A typical exchange:¶

1. Client opens a QUIC connection to the TSQ server (UDP/443).¶

2. Client sends a TSQ Request with nonce and timestamp request.¶

3. Server replies with timestamps, echoed nonce, and metadata.¶

4. Client calculates RTT and adjusts clock accordingly.¶

4. Security and Threat Model

TSQ relies on QUIC’s handshake for mutual authentication, confidentiality, and replay protection. Optional Ed25519 or HMAC signatures can be added if auditability is required. By default, QUIC session integrity suffices.¶

5. Scalability Considerations

Short-lived connections, session resumption, and optional stateless design support scalability. TSQ is suitable for enterprise and cloud deployments.¶

6. Message Format (TLV)

TSQ Request¶

• Type: 0x01¶

• Nonce (16 bytes)¶

• Optional extensions¶

TSQ Response¶

• Type: 0x02¶

• Echoed Nonce¶

• Server Time¶

• Receive Timestamp¶

• Send Timestamp¶

• Optional metadata and signature¶

7. Use Cases

• Cloud/container infrastructure¶

• Mobile clients¶

• Firewalled enterprise networks¶

• High-precision timing visibility¶

9. Next Steps

• Solicit feedback on sync behavior and design¶

• Improve trust and crypto model¶

• Implement prototype in QUIC¶

• Submit official Internet-Draft if interest grows¶

10. Acknowledgments

Thanks to contributors from the QUIC and NTP working groups for input on timing accuracy and protocol design.¶

11. References

[RFC8915]

Franke, D., Sibold, D., Teichel, K., Dansarie, M., and R. Sundblad, "Network Time Security for the Network Time Protocol", RFC 8915, <https://datatracker.ietf.org/doc/html/rfc8915>.

[RFC7384]

Mizrahi, T., "Security Requirements of Time Protocols in Packet Switched Networks", RFC 7384, <https://datatracker.ietf.org/doc/html/rfc7384>.

[RFC9000]

Iyengar, J. and M. Thomson, "QUIC: A UDP‑Based Multiplexed and Secure Transport", RFC 9000, <https://datatracker.ietf.org/doc/html/rfc9000>.

[RFC9221]

Pauly, T., Kinnear, E., and D. Schinazi, "An Unreliable Datagram Extension to QUIC", RFC 9221, <https://datatracker.ietf.org/doc/html/rfc9221>.

[RFC9308]

Kühlewind, M. and B. Trammell, "Applicability of the QUIC Transport Protocol", RFC 9308, <https://datatracker.ietf.org/doc/html/rfc9308>.

Appendix A. IANA Considerations

This document has no IANA actions.¶