Re: EME insecure contexts

This was tracked as https://github.com/w3c/encrypted-media/issues/220,
which we fixed in June. The quoted text was removed from the ED at that
time.

The relevant PRs are https://github.com/w3c/encrypted-media/pull/271 and
https://github.com/w3c/encrypted-media/issues/289.

David

On Wed, Oct 26, 2016 at 5:44 PM, Paul Cotton <Paul.Cotton@microsoft.com>
wrote:

> The EME CR specification includes the following “at risk” feature:
>
> > Support for insecure contexts, including the Are insecure contexts
> allowed?
> <http://www.w3.org/TR/encrypted-media/#are-insecure-contexts-allowed---deprecated>
> algorithm and steps that call it.
>
> http://www.w3.org/TR/encrypted-media/#sotd
>
>
>
> What if anything should we do about this “at risk” feature?
>
>
>
> /paulc
>
>
>
> How do you recommend
>
> Paul Cotton, Microsoft Canada
>
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>
> Tel: (425) 705-9596 Fax: (425) 936-7329
>
>
>