RE: Request transition of Encrypted Media Extensions (EME) to Proposed Recommendation

Microsoft supports the transition.

> On Tue, Nov 01, 2016 at 16:41:27, Paul Cotton wrote:
> Proposed Recommendation
> 
> In accordance with the W3C process's requirement to record the group's
> decision to request advancement [1], this is a Call for Consensus (CfC) to
> request transition to Proposed Recommendation for the following Encrypted
> Media Extensions (EME) document:
> 
> 
> 
> https://w3c.github.io/encrypted-media/
> 
> 
> 
> with the following additional changes:
> 
> 1.      Removal of the following material about "at risk" features from
> the Status of this Document,
> 
> "The following features are at risk and may be removed:
> 
> *        The "persistent-usage-record"
> <https://w3c.github.io/encrypted-media/#idl-def-MediaKeySessionType.pers
> istent-usage-record>  session type and the related MediaKeySession
> destroyed
> <https://w3c.github.io/encrypted-media/#media-key-session-destroyed>
> algorithm.
> 
> *        Setting the media element's readyState
> <https://www.w3.org/TR/html5/embedded-content-0.html#dom-media-readystat
> e>  value based on key availability in the Wait for Key
> <https://w3c.github.io/encrypted-media/#wait-for-key>  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?
> <http://www.w3.org/TR/2016/CR-encrypted-media-20160705/#are-insecure-con
> texts-allowed---deprecated>  algorithm and steps that call it.
> 
> 2.      Removal of the "persistent-usage-record" "at risk" feature as
> per ISSUE-353 [2].
> 
> Notes:
> 
> a)      The "at risk" feature on readyState will NOT be removed.  See
> ISSUE-336 [3].
> 
> b)     The "at risk" feature on insecure contexts was removed in July
> as per ISSUE-220 [4].
> 
> 
> 
> For your reference, there is list of recent commits to the EME
> specification:
> 
> https://github.com/w3c/encrypted-media/commits/gh-pages/encrypted-media
> -respec.html
> 
> 
> 
> The following is a breakdown of the issues processed since the EME issues
> were triaged in March 2016 [5] for the Candidate Recommendation specification
> [6]:
> 
> 53 V1 issues:
> https://github.com/w3c/encrypted-media/milestone/1?closed=1
> <https://github.com/w3c/encrypted-media/milestone/1?closed=1>
> 
> 59 V1Editorial issues:
> https://github.com/w3c/encrypted-media/milestone/4?closed=1
> <https://github.com/w3c/encrypted-media/milestone/4?closed=1>
> 
> 33 V1NonBlocking issues:
> https://github.com/w3c/encrypted-media/milestone/3?closed=1
> <https://github.com/w3c/encrypted-media/milestone/3?closed=1>
> 
> 
> 
> A list of all issues against EME is available at:
> 
> https://github.com/w3c/encrypted-media/issues?utf8=%E2%9C%93&q=is%3Aiss
> ue%20
> 
> and a list of issues NOT dealt with in this cycle and assigned to the VNext
> milestone is available at:
> 
> https://github.com/w3c/encrypted-media/milestone/2
> 
> 
> 
> Test results for this specification can be found at [7-9].  An updated
> analysis of the test results is available at [10].  Note that we plan to
> continue updating the EME test results until we present the draft Proposed
> Recommendation to the W3C Director.
> 
> 
> 
> Formal Objections against EME are recorded at:
> 
> https://dev.w3.org/html5/status/formal-objection-status.html
> 
> These formal objections will be reviewed when we present the Proposed
> Recommendation to the W3C Director.
> 
> 
> 
> Silence will be taken to mean there is no objection, but positive responses
> are encouraged. If there are no objections by Tuesday November 8, this
> resolution will carry.
> 
> 
> 
> Considerations to note:
> 
> 
> 
> - A request to advance indicates that the Working Group believes the
> specification is stable and appropriate for advancement to Recommendation
> status.
> 
> 
> 
> /paulc
> 
> HME WG Chair
> 
> 
> 
> [1] http://www.w3.org/2005/10/Process-20051014/tr.html#transition-reqs
> <http://www.w3.org/2005/10/Process-20051014/tr.html#transition-reqs>
> 
> [2] https://github.com/w3c/encrypted-media/issues/353
> <https://github.com/w3c/encrypted-media/issues/353>
> 
> [3] https://github.com/w3c/encrypted-media/issues/336
> <https://github.com/w3c/encrypted-media/issues/336>
> 
> [4] https://github.com/w3c/encrypted-media/issues/220
> <https://github.com/w3c/encrypted-media/issues/220>
> 
> [5]
> https://lists.w3.org/Archives/Public/public-html-media/2016Mar/0003.html
> 
> [6]  http://www.w3.org/TR/2016/CR-encrypted-media-20160705/
> 
> [7] http://w3c.github.io/test-results/encrypted-media/all.html
> <http://w3c.github.io/test-results/encrypted-media/all.html>
> 
> [8] https://w3c.github.io/test-results/encrypted-media/less-than-2.html
> <https://w3c.github.io/test-results/encrypted-media/less-than-2.html>
> 
> [9]
> https://w3c.github.io/test-results/encrypted-nedia/complete-fails.html
> <https://w3c.github.io/test-results/encrypted-nedia/complete-fails.html>
> [10]
> https://lists.w3.org/Archives/Public/public-html-media/2016Oct/0064.html
> <https://lists.w3.org/Archives/Public/public-html-media/2016Oct/0064.htm
> l>
> 
> 
> 
> Paul Cotton, Microsoft Canada
> 
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> 
> Tel: (425) 705-9596 Fax: (425) 936-7329
> 
>

Received on Thursday, 3 November 2016 18:50:27 UTC