Please consider the needs of space use of QUIC, as discussed in the Tiptop working group.
In particular it would be good if both very long RTTs and asymmetric one way delays could be supported. Regards Marshall Eubanks On Thu, Jul 10, 2025 at 10:11 PM Garrett McCollum (gmccollu) <[email protected]> wrote: > > Hi All, > > > > I’m exploring an idea for a modern, secure replacement for NTP built on top > of QUIC, tentatively called TSQ (Time Sync over QUIC). > > > > The idea is to use QUIC streams for timestamp exchange, leveraging its > built-in encryption, NAT traversal, and multiplexing benefits. It would avoid > the fragility of legacy NTP (UDP/123, no auth, clock jumps), and provide a > better time sync layer for modern networks. > > > > A rough sketch: > > > > - QUIC stream carries a nonce → timestamp request > > - Server replies with signed timestamp, receive/send timing > > - Client calculates offset + RTT > > - Security, clock discipline, and trust model simplified > > > > Is anyone aware of prior efforts like this? Would the QUIC WG be a good > venue to discuss it further or explore a draft? > > > > I’d be happy to share a more detailed draft or early prototype if there’s > interest. > > > > Thanks, > > > > Garrett McCollum > >
