(roll over for info)
The working group is currently writing the document. This is a collaborative approach using Google Docs.
Goals and Objectives
Request TracingThe request tracing specification seeks to address observability gaps in the delivery of real-time streaming media experiences, over HTTP, across content providers and third party services. Request tracing spans the spectrum of HTTP requests made by client applications and other services on the client’s behalf. The specification takes into consideration modern streaming media delivery protocols and conventions in addition to complex request flows such as 304 redirects and CDN request collapsing. To this end, in contrast to other tracing specifications and conventions, this specification will organize information based on the set of requests required to fulfill a single intent (e.g. retrieval of a single media from one or more CDNs).
Content Creation and PropagationThe Content Creation and Propagation specification will seek to address observability gaps for the online and offline creation processes for both live and VOD scenarios. This includes ingest from live sources or mezzanine source files followed by various workflow stages such as encoding, transcoding to multiple bitrates, dynamic ad stitching (SSAI), encryption, etc. This specification is meant to work in tandem with the Request Tracing specification to provide both enhanced observability for the requesting of media objects and related data from media applications and the creation, propagation and staging of media objects in order to fulfill those requests either offline or in real time.
Trace Telemetry ExportWhile the two specifications above will seek to propagate data in-band, leveraging HTTP headers or querystrings, there are scenarios where trace data must be delivered from workflow sources to centralized storage and analysis services. For instance, if a media object request is made by a video player and that request times out only out-of-band logging to centralized services will support proper root cause analysis.The Trace Telemetry Export specification will seek to close this gap by defining the information useful to the identification of impediments.
Cross-cutting Support for Object Transformation TracingIn order to enable the tracing of media object defects (rather than impediments to the delivery of those objects) the three specifications listed above will seek to include data elements necessary to determine where, when and how each object is modified during creation, propagation, or delivery.
- Document a standard for transporting information useful to the identification of impediments to the delivery of streaming media in-band with HTTP requests and responses;
- Document a standard for transporting that same information out-of-band;
- Document a standard for transporting that same information in-band with streaming media that is driven by a push or broadcast model instead of a request–response model; and
- Ensure that documents have appropriate designations for public and private data so that entities can easily strip only the private data at their perimeters.
- The body of the media itself;
- Thumbnails, text descriptions, and imagery that serve to represent the media;
- DRM licenses required to display the media;
- Metadata that facilitates the transfer or identification of media; and
- Information that identifies the context around the request, like session or content identifiers.
- Timing information around all requests, responses, processing, and creation of media elements;
- Storage information that indicates how, where, why, and for how long media elements have been stored;
- Transformation information that documents how media elements have been modified; and Identity information for all entities that have participated in the delivery of media elements.
- Document standard APIs for programming language implementations;
- Document specific transports for out-of-band tracing carriage;
- Prescribe or proscribe particular actions as a consequence of data values;
- Document a standard for a request–response model that does not use HTTP; or
- Rely on technologies that are not defined by a standard specification document.
The following members have contributed to this project. Click on their name to visit their profile. If they have not published their profile, the link will redirect to their LinkedIn profile.
There are no additional references or other required readings need to participate in this project.