W3C home > Mailing lists > Public > public-html@w3.org > February 2013

Re: Technical Review of EME (DRM in HTML5)

From: Nicholas Doty <npdoty@w3.org>
Date: Sun, 3 Feb 2013 18:07:56 -0800
Cc: Manu Sporny <msporny@digitalbazaar.com>, public-html@w3.org, "public-privacy (W3C mailing list)" <public-privacy@w3.org>
Message-Id: <02B98900-BF0A-476A-A8B3-EEE2249840B6@w3.org>
To: Mark Watson <watsonm@netflix.com>
(BCC public-tracking and CC public-privacy.)

While part of this request explicitly mentions the Tracking Preference Expression, I think the general request about thinking through the privacy implications is more relevant to the Privacy Interest Group than the Tracking Protection Working Group.

On Jan 29, 2013, at 8:33 PM, Manu Sporny <msporny@digitalbazaar.com> wrote:

> +CC: Tracking Protection WG (search for 'privacy')

> I don't see anything about the privacy implications that the EME
> specification raises. The HTML Media WG should work with the TPWG to
> make sure all privacy matters are dealt with by folks that seem to care
> more about privacy than you seem to.


On Feb 3, 2013, at 12:58 PM, Mark Watson <watsonm@netflix.com> wrote:

> On Feb 3, 2013, at 9:36 AM, "Manu Sporny" <msporny@digitalbazaar.com> wrote:
> 
>> On 01/30/2013 02:19 AM, Mark Watson wrote:
>> 
>>>> How does the spec ensure that it works with the Tracking
>>>> Preference Expression specifications?
>>> 
>>> I think this is up to browsers to determine. If a CDM includes 
>>> capabilities that enable any given kind of tracking then that CDM 
>>> should obviously be rendered inoperable by user preference settings 
>>> that prohibit such tracking.
>> 
>> How will the browser have any idea that the CDM is engaging in this
>> activity?
> 
> As I said, I would expect browsers
> To be quite particular about the CDMs they support, including requiring quite detailed information about the CDM so that they can properly asses the privacy risks etc.

We have discussed functionality for the Tracking Preference Expression spec to potentially be exposed to a browser's plugin architecture. As I'm not intimately familiar with the EME spec, perhaps Manu or others could help explain the potential privacy impacts so we'd be better able to organize a privacy review.

Thanks,
Nick
Received on Monday, 4 February 2013 02:08:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:37 UTC