search

Dash-Industry-Forum / MPEG

Collects issues that need to be reported to MPEG
1 stars 0 forks source link

ContentProtection descriptor usage #18

Open lpiron opened 4 years ago

lpiron commented 4 years ago

See https://github.com/Dash-Industry-Forum/DASH-IF-IOP/issues/384 Answer to MPEG previous liaison letter with the expected action.

haudiobe commented 4 years ago

On the issue of signaling the content protection when the common encryption is used, we believe that the descriptor carrying DRM information may also include encryption information and therefore the inclusion of a separate descriptor is unnecessary. We would suggest DASH-IF to investigate such an approach. I believe this above comment from MPEG addresses this issue.

I propose next steps as:

No action in terms of changes to DASH-IF guidelines - we keep requiring the standard practice of mp4protection descriptor to signal Common Encryption scheme and optionally allow separate descriptors for DRM signaling. Request MPEG to adjust DASH so that a combination of "mp4protection + DRM-system-specific" descriptors is permitted for DRM system activation. Rationale: this is how it works today. And it works fine. Inertia will keep it working no matter what the standard says. It is more valuable to bring the standard in line with common implementation here, especially as it does not really sacrifice anything.

Agreed