Contact emails
Spec
Latest editor’s draft of EME spec: https://w3c.github.io/encrypted-media/
The feature to ship is described at: https://w3c.github.io/encrypted-media/#dom-mediakeysessiontype-persistent-usage-record
Tag review: This feature was discussed extensively during the previous Tag review https://github.com/w3ctag/design-reviews/issues/73, which was closed without concerns (“... we no longer have a concern with persistent usage record”).
Summary
Support a new MediaKeySessionType “persistent-usage-record session”, for which the license and key(s) are not persisted and for which a record of key usage is persisted when the keys available within the session are destroyed. See the spec for more details.
Link to “Intent to Prototype” blink-dev discussion
https://groups.google.com/a/chromium.org/g/blink-dev/c/UcOYfks9jbY/m/zdXzKECzDgAJ
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
This is an optional feature in the spec. The EME API around persistent-usage-record session will be enabled on all platforms. The actual support by CDMs will vary by platform and by key system supported.
Risks
Interoperability and Compatibility
Interoperability risk: Low. We have received a lot of public support:
Edge: Supported by previous Microsoft EME spec editor. It is supported by the current owner of the Edge team and the whole flow is already working behind the flag. The equivalent feature is also supported natively by Windows Media Foundation.
Firefox: No signals
Safari: Shipped
Web developers:
No signals from other web developers
Compatibility risk is the likelihood that a change will break existing web content loaded in Chromium. Since this feature adds a new session type to the Encrypted Media Extensions spec that nobody is currently using, there should be no compatibility risks. Use of this API is entirely optional, so there is no impact on existing applications.
Ergonomics
N/A
Activation
The APIs will be easy to use by developers immediately. However, as most EME features, the license server needs to be updated to support this feature.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
https://wpt.fyi/results/encrypted-media, search for persistent-usage-record
In Chromium, the Clear Key key system doesn’t not support persistent-usage-record session directly, so it’s not possible to fully test it via web-platform-tests. However, there are Chromium browser tests covering the feature using an “External Clear Key” key system which is only used for testing.
Entry on the feature dashboard
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAF1j9YOhQaSkvS1cLZVvpLw7rXcayJTg2%2BPDoYfKAQPmwV%2BOFg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7ebba63f-409d-af6b-4cdd-d557d5ad63f6%40gmail.com.
Spec
Latest editor’s draft of EME spec: https://w3c.github.io/encrypted-media/
The feature to ship is described at: https://w3c.github.io/encrypted-media/#dom-mediakeysessiontype-persistent-usage-record
Tag review:
This feature was discussed extensively during the previous Tag review https://github.com/w3ctag/design-reviews/issues/73, which was closed without concerns (“... we no longer have a concern with persistent usage record”).
Summary
Support a new MediaKeySessionType “persistent-usage-record session”, for which the license and key(s) are not persisted and for which a record of key usage is persisted when the keys available within the session are destroyed. See the spec for more details.
Link to “Intent to Prototype” blink-dev discussion
https://groups.google.com/a/chromium.org/g/blink-dev/c/UcOYfks9jbY/m/zdXzKECzDgAJ
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
This is an optional feature in the spec. The EME API around persistent-usage-record session will be enabled on all platforms. The actual support by CDMs will vary by platform and by key system supported.
Risks
Interoperability and Compatibility
Interoperability risk: Low.
Signals from other implementations (Gecko, WebKit):
Gecko: No Signal (https://www.w3.org/2020/05/12-mediawg-minutes.html#t07)
WebKit: Shipped/Shipping (https://webkit.org/blog/10024/release-notes-for-safari-technology-preview-100/)
Web / Framework developers:
The equivalent feature is also supported natively by Windows Media Foundation.
Compatibility risk is the likelihood that a change will break existing web content loaded in Chromium. Since this feature adds a new session type to the Encrypted Media Extensions spec that nobody is currently using, there should be no compatibility risks. Use of this API is entirely optional, so there is no impact on existing applications.
Ergonomics
N/A
Activation
The APIs will be easy to use by developers immediately. However, as most EME features, the license server needs to be updated to support this feature.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
https://wpt.fyi/results/encrypted-media, search for persistent-usage-record
In Chromium, the Clear Key key system doesn’t not support persistent-usage-record session directly, so it’s not possible to fully test it via web-platform-tests. However, there are Chromium browser tests covering the feature using an “External Clear Key” key system which is only used for testing.
Entry on the feature dashboard
Thanks for the comments!Rego: TAG review template filled as requested: https://github.com/w3ctag/design-reviews/issues/73#issuecomment-663210837Daniel/Chris: I updated the intent-to-ship with the link to the Explainer doc and new "Signals from other implementations" section.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAF1j9YMgEq5%2B5iKXRXKHAj93nSXAj49BggtNKJc75iPJv8N_qA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEhsGGfpPOyhKvM0%3DN3SqPezv9gz8VCd64NGggj8LFJhuA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAF1j9YPP-JbRzLVx_Cn4S%3D%2BZ9SnasdG5r74uWP-vy8SM%2BBjE1Q%40mail.gmail.com.