Publish acquired source time stamp in the HTTP header format
Encoder publish the acquired source time stamp in the HTTP headers listed in the following table.
Encoders should publish HTTP headers at the beginning of every segment. The capture and publish time-stamp should be relevant for the first frame of the segment.
All segments should start with an IDR frame (key frame).
HTTP headers are in epoch time and not in milliseconds.
||Encoders publish source time-stamp associated with the acquired content in this HTTP header.|
||Encoders publish the time-stamp associated with the publishing content in this HTTP header. This is the time when the HTTP segment upload is initiated by the encoder application. This time-stamp is refreshed for all retries done by the encode application. The receiving system uses this time-stamp to verify NTP synchronization status.|
||Encoders publish the typical fixed end-to-end delay time of the encoding system in this HTTP header.|
This system of time stamps are needed to flag any timing issues due to NTP synchronization failures.
(AKAM-ENC-EXPECTED-PIPE-DELAY - (AKAM-ENC-CONTENT-PUB-TIME -
AKAM-ENC-CONTENT-CAP-TIME)) can indicate if the upload is a long retry or the first