Time
A Time message is sent whenever the source time for a unit passes over a second boundary. The Time field is the number of seconds relative to midnight Eastern Time. All subsequent time offset fields for the same unit will use the new Time value as the base until another Time message is received for the same unit. The Time message will also include the Epoch Time field, which is the current time represented as the number of whole seconds since the Epoch (midnight January 1, 1970).
A trading day may span multiple calendar days. Therefore, C1 options market data recipients must prepare for a crossing of the midnight ET boundary. At such time, a new Time Reference message will be sent and the Time field in subsequent Time messages will reset to reflect the number of seconds from the most recent midnight ET time.
| Field Name | Offset | Length | Type/(Value) | Description |
|---|---|---|---|---|
| Length | 0 | 1 | Binary | Length of this message including this field |
| Message Type | 1 | 1 | 0x20 | Time Message |
| Time | 2 | 4 | Binary | Number of whole seconds elapsed since the start of the current Eastern Time calendar day, derived by converting the current Eastern wall clock time (HH:MM:SS) to seconds. On Daylight Saving Time transition days, Time reflects wall clock seconds and does not adjust for the UTC offset change. On a DST spring-forward day, the maximum value will be 82,799 (23 hours). On a DST fall-back day, values between 3,600 and 7,199 will appear twice. Recipients requiring unambiguous absolute timestamps should use Epoch Time (where available) or Midnight Reference in the Time Reference message. |
| Epoch Time | 6 | 4 | Binary | Number of whole seconds since the Epoch (midnight January 1, 1970 UTC). |
| Total Length = 10 bytes | ||||