IETF MOQ WG: TImestamp Draft
Alan Frindell posted to the MOQ working group mailing list on October 6, 2026. Hi Cullen, Suhas pointed me at Tempo and I had my agent verify that my design was compatible. We should have listed it in the prior art, sor…
Message Snapshot
- List:
moq@ietf.org - Thread subject: TImestamp Draft
- Message subject: [Moq] Re: TImestamp Draft
- Author: Alan Frindell
- Published: 2026-10-06T19:09:39.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Alan Frindell posted to the MOQ working group mailing list on October 6, 2026. Hi Cullen, Suhas pointed me at Tempo and I had my agent verify that my design was compatible. We should have listed it in the prior art, sor…
Why It Matters
This message came from the public MOQ working group archive and captures active discussion, meeting coordination, or implementation feedback around Media over QUIC.
Message Excerpt
Hi Cullen, Suhas pointed me at Tempo and I had my agent verify that my design was compatible. We should have listed it in the prior art, sorry about that. Happy to add that in -01, see
Plain-Text Body
Hi Cullen, Suhas pointed me at Tempo and I had my agent verify that my design was compatible. We should have listed it in the prior art, sorry about that. Happy to add that in -01, see https://github.com/afrind/draft-frindell-moq-timestamp/issues/9.
The core concept here is factoring out the mechanism for conveying timestamps as properties, and drafts like Tempo can assign application semantics to those properties (synchronized playout), or define secondary/tertiary timestamps as relative offsets from the ones in this draft.
Thanks
-Alan