RE: CfC: EME Candidate Recommendation "at risk" items

>I propose that this timeline be amended to include a discussion of a covenant, whose text we will determine as a group, to protect security researchers and implementers from legal aggression under DMCA 1201 and related international statutes.

Discussing such a proposed covenant is NOT in the scope of the current HTML Media Extensions WG charter [1].   If the W3C Director has wanted the HME WG to take on this task when the WG was re-chartered on March 31 I am sure he would have added this dependency to our charter.

Therefore I am NOT going to entertain your request for amending the current HME WG timeline [2].

/paulc
HTML Media Extensions WG Chair

[1] http://www.w3.org/2013/09/html-charter.html 
[2] https://lists.w3.org/Archives/Public/public-html-media/2016May/0029.html 

-----Original Message-----
From: Cory Doctorow [mailto:cory@eff.org] 
Sent: Monday, May 23, 2016 6:44 PM
To: Paul Cotton <Paul.Cotton@microsoft.com>; 'public-html-media@w3.org' <public-html-media@w3.org>
Subject: Re: CfC: EME Candidate Recommendation "at risk" items

I propose that this timeline be amended to include a discussion of a covenant, whose text we will determine as a group, to protect security researchers and implementers from legal aggression under DMCA 1201 and related international statutes.

On 05/23/2016 03:39 PM, Paul Cotton wrote:
> The MSE and EME timeline [1] indicates that we are to finalize the MSE and EME "substantive change" V1 issues by June 9 and then publish Candidate Recommendation drafts in early July.
> 
>        Thu Jun 9: Last "substantive change"s [3] to MSE and EME
>        Thu Jun 16: MSE Candidate Recommendation (CR) update; EME Working Draft update, CFC for EME and MSE CR (Jun 16-23)
>        Tue Jun 28: EME and MSE transition to CR request
>        Tue Jul  5: EME and MSE Candidate Recommendation publication
> 
> Currently there are 12 MSE V1 open issues [2]  and 13 EME V1 open issues [3].  In order to make as much progress as possible on these open V1 issues, the Editors are meeting F2F at the end of this week.  In addition, in order to help the Editors deliver by the June 9 date and to give the HTML Media Extensions (HME) WG the maximum time to deal with more controversial issues, I am proposing that we keep some items in the July Candidate Recommendations but that we mark these items as being "at risk".  Marking an item "at risk" means that the HME WG can decide to remove the item from our Proposed Recommendation without having to re-publish another Candidate Recommendation.
> 
> HTML Media Extensions WG is issuing a Call for Consensus to add the "secure release" [4] feature as an "at risk" feature when the EME Candidate Recommendation is published in early July.  This will permit discussion with the W3C TAG to continue on [4] before and during the Candidate Recommendation timeframe so that we can make the most informed decision on this feature.
> 
> Silence will be taken to mean there is no objection, but positive responses are encouraged.  If there are no objections by Monday May 30, this resolution will carry.
> 
> /paulc
> HTML Media Extensions WG Chair
> 
> [1] 
> https://lists.w3.org/Archives/Public/public-html-media/2016May/0029.ht

> ml [2] https://github.com/w3c/media-source/milestones/V1

> [3] https://github.com/w3c/encrypted-media/milestones/V1

> [4] https://github.com/w3c/encrypted-media/issues/85

> 
>

Received on Monday, 23 May 2016 23:19:25 UTC