Clarify monotonicity requirement on timestamp begin

[ctf.git] / common-trace-format-specification.md

diff --git a/common-trace-format-specification.md b/common-trace-format-specification.md
index fd49e593742b443e59dad592d5d8f83e7f5e8b26..372285c23f461e163ab20e092e493f9210fd09df 100644 (file)
--- a/common-trace-format-specification.md
+++ b/common-trace-format-specification.md
@@ -464,6 +464,9 @@ enum {
 }
 ~~~
 
+An enumeration field can have an integral value for which the associated
+enumeration type does not map to a string.
+
 ### 4.2 Compound types
 
 Compound are aggregation of type declarations. Compound types include
@@ -833,10 +836,12 @@ TSDL metadata):
     range between these timestamps should include all event timestamps
     assigned to events contained within the packet. The timestamp at the
     beginning of an event packet is guaranteed to be below or equal the
-    timestamp at the end of that event packet. The timestamp at the end
-    of an event packet is guaranteed to be below or equal the
-    timestamps at the end of any following packet within the same stream.
-    See [Clocks](#spec8) for more detail.
+    timestamp at the end of that event packet. The timestamp at the
+    beginning of an event packet is guaranteed to be above or equal the
+    timestamps at the beginning of any prior packet within the same
+    stream. The timestamp at the end of an event packet is guaranteed to
+    be below or equal the timestamps at the end of any following packet
+    within the same stream. See [Clocks](#spec8) for more detail.
   * **Events discarded count**. Snapshot of a per-stream
     free-running counter, counting the number of events discarded that
     were supposed to be written in the stream after the last event in