From 1d28a5a17882fb8e632dfdf0b34bfa47c6dd6490 Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Mon, 21 Oct 2024 15:52:19 +0100 Subject: [PATCH] Update draft-ietf-quic-qlog-main-schema.md Co-authored-by: Robin Marx --- draft-ietf-quic-qlog-main-schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-qlog-main-schema.md b/draft-ietf-quic-qlog-main-schema.md index f9e8e825..d844f356 100644 --- a/draft-ietf-quic-qlog-main-schema.md +++ b/draft-ietf-quic-qlog-main-schema.md @@ -648,7 +648,7 @@ Example qlog event: ## Timestamps {#time-based-fields} Each event MUST include a "time" field to indicate the timestamp that it -occurred. It is a duration measured from some point in time, in units of ???. +occurred. It is a duration measured from some point in time; its units depend on the type of clock chosen and system used. Typically however, a millisecond resolution is employed. There are several options for generating and logging timestamps, these are governed by the ReferenceTime type (optionally included in the "reference_time" field contained in a trace's "common_fields" ({{common-fields}})) and TimeFormat