Expand description
UTCTiming schemes and the client-measured clock sample.
ISO/IEC 23009-1 5.8.5.7 Table 35 names the schemes; the sampling rule
(midpoint of the request/response exchange, uncertainty = half the round
trip plus the time source’s own resolution) is
docs/dash-runtime/DESIGN.md 3.3. The caller measures sent_us and
received_us on its own monotonic clock; nothing here reads a clock.
Structs§
- Exchange
- The request/response pair the caller timed on its monotonic clock.
- UtcSample
- One clock measurement: at monotonic
mono_usthe UTC time wasutc_us(Unix microseconds), give or takeuncertainty_us.
Enums§
- UtcScheme
- A
UTCTimingscheme (Table 35).
Constants§
- DATE_
HEADER_ HALF_ SECOND_ US Datecarries whole seconds (RFC 9110 5.6.7): the sample is taken at the middle of the second and the half second is added to the uncertainty.- HTTP_
NTP_ RESOLUTION_ US - Resolution of an NTP timestamp read over HTTP, in microseconds.
- SCHEME_
DIRECT - 5.8.5.7:
urn:mpeg:dash:utc:direct:2014. - SCHEME_
HTTP_ HEAD - 5.8.5.7:
urn:mpeg:dash:utc:http-head:2014. - SCHEME_
HTTP_ ISO - 5.8.5.7:
urn:mpeg:dash:utc:http-iso:2014. - SCHEME_
HTTP_ NTP - 5.8.5.7:
urn:mpeg:dash:utc:http-ntp:2014. - SCHEME_
HTTP_ XSDATE - 5.8.5.7:
urn:mpeg:dash:utc:http-xsdate:2014. - SCHEME_
NTP - 5.8.5.7:
urn:mpeg:dash:utc:ntp:2014. - SCHEME_
SNTP - 5.8.5.7:
urn:mpeg:dash:utc:sntp:2014. - UTC_
BODY_ MAX_ BYTES - Largest UTC response body read (DESIGN risk R3).
Functions§
- sample_
from_ body - Sample from the body of an
http-xsdate,http-isoorhttp-ntpresponse. - sample_
from_ date_ header - Sample from the
Dateheader of anhttp-head(or any) response. - sample_
from_ direct - Sample from a
directscheme@value, taken at the midpoint of the MPD response exchange. - sample_
from_ exchange - Build a sample from a timed exchange and the server time it returned.