Additional Common Media Client Data (CMCD) support.

[wilaw]

Is your feature request related to a problem? Please describe.

CMCD is a spec developed by the Consumer Technology Association. It is free for use and download. CMCD is a new standard that allows player clients to exchange mutually beneficial data with the CDN to allow the CDN to improve delivery performance and the publisher to retrieve real-time data about the health of their player population. It uses the media requests as the vehicle for transmitting the data. A working implementation by dash.js is available, as well as hls.js (thanks to RealEyes). A presentation on CMCD is available.

Describe the solution you'd like

The request is for hls.js to enable CMCD as a core capability, with the following features:

• Have CMCD be default off
• Be able to activate it easily through single API call. This activation would turn on all available keys.
• Be able to apply a separate filter list to explicitly enable certain keys. Only keys whitelisted by the filter would be sent.
• Have an API method to enable setting the ContentID value and the RTP value, both as a fixed threshold and also as a multiple of encoded bitrate.
• Custom keys - accepting both a key, value & target header arguments

Additional context

If you have questions or would like more information about which publishers are interested in deploying this and are gated by the lack of a player implementation, please don't hesitate to contact me.

Cheers
Will Law
Chair - CTA WAVE and CMCD Spec Editor

[littlespex]

I have a draft PR for this feature. There are a few open questions around where to find the necessary data to fulfill all the CMCD fields. Would it be possible to set up a meeting to discuss the questions raised in #4346?

[tjenkinson]

Reopening given there are still some features that aren't implemented yet, and will come later.

[itsjamie]

@littlespex or @tjenkinson could you list what features from the above are not implemented in #4346 so if someone wants to implement it, they could more easily see on the issue?

[littlespex]

There are a few fields that haven't been implemented:

• nor
• nrr
• rtp
• dl

Additionally, there are some API level features that were not included:

• Be able to apply a separate filter list to explicitly enable certain keys. Only keys whitelisted by the filter would be sent.
• Custom keys - accepting both a key, value & target header arguments

[littlespex]

Moving the remaining work to separate issues:

• Implement CMCD next object request (nor) property #6088
• Implement CMCD next range request (nrr) property #6089
• Implement CMCD requested maximum throughput (rpt) property #6090

[littlespex]

@itsjamie @robwalch This issue can be closed.

[robwalch]

Thanks @littlespex!

Closing in favor of tracking separate issues:

• Implement CMCD next object request (nor) property #6088
• Implement CMCD next range request (nrr) property #6089
• Implement CMCD requested maximum throughput (rpt) property #6090

[avelad]

@littlespex The issue for dl would be missing, right?

[littlespex]

@avelad Thanks, I missed that one.

#6100