W3C home > Mailing lists > Public > public-html-media@w3.org > January 2019

[encrypted-media] Tracking the lifecycle of a KeyId (#449)

From: Eric Stobbart via GitHub <sysbot+gh@w3.org>
Date: Fri, 25 Jan 2019 21:38:52 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-403342661-1548452331-sysbot+gh@w3.org>
estobbart has just created a new issue for https://github.com/w3c/encrypted-media:

== Tracking the lifecycle of a KeyId ==
`keystatuses` provide keyId's.. but there's no real way to track them earlier than when they appear in that status. In DASH they appear in the ContentProtection, and they're also in the initializationSegment either in the `pssh` or the `tenc`. But if the `pssh` isn't in the manifest it's difficult to use the `encrypted` `initData` to track the KeyId, unless the browser was responsible for upgrading v.0 pssh boxes to v.1 boxes with the `tenc` `default_KID`, or some other way to include a KeyID in the encrypted payload. This makes platforms with multiple CDM implementations difficult, because two encrypted event's could occur, each event with it's own systemId (that you have to parse from the initData) for the same keyId. Unless the requirement was that only one encrypted event occurred per keyId, and the initData was an array of array buffers.

Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/449 using your GitHub account
Received on Friday, 25 January 2019 21:38:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:49:23 UTC