RE: EME At Risk Features

I suggest the first two items be combined as "The "persistent-usage-record"<https://w3c.github.io/encrypted-media/#idl-def-MediaKeySessionType.persistent-usage-record> session type and the related MediaKeySession destroyed<https://w3c.github.io/encrypted-media/#media-key-session-destroyed> algorithm."

/paulc

From: Jerry Smith (WPT)
Sent: Tuesday, June 7, 2016 4:49 PM
To: Paul Cotton <Paul.Cotton@microsoft.com>
Cc: David Dorwin <ddorwin@google.com>; Mark Watson (watsonm@netflix.com) <watsonm@netflix.com>; Matt Wolenetz <wolenetz@google.com>
Subject: EME At Risk Features

The EME At Risk PR has been completed and merge.  It's in the latest editor's draft:

https://w3c.github.io/encrypted-media/

The following features are at risk and may be removed:

*        The "persistent-usage-record"<https://w3c.github.io/encrypted-media/#idl-def-MediaKeySessionType.persistent-usage-record> session type.

*        The MediaKeySession destroyed<https://w3c.github.io/encrypted-media/#media-key-session-destroyed> algorithm.

*        Setting the media element's readyState<http://www.w3.org/TR/html5/embedded-content-0.html#dom-media-readystate> value based on key availability in the Queue a "waitingforkey" Event<https://w3c.github.io/encrypted-media/#queue-waitingforkey> and Attempt to Resume Playback If Necessary<https://w3c.github.io/encrypted-media/#resume-playback> algorithms.

*        Support for insecure contexts, including the Are insecure contexts allowed?<https://w3c.github.io/encrypted-media/#are-insecure-contexts-allowed---deprecated> algorithm and steps that call it.
The first two of these are secure release.

Jerry