EME insecure contexts from Paul Cotton on 2016-10-27 (public-hme-editors@w3.org from October 2016)

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Thu, 27 Oct 2016 00:44:59 +0000
To: "David Dorwin <ddorwin@google.com> (ddorwin@google.com)" <ddorwin@google.com>, Mark Watson <watsonm@netflix.com>, "Jerry Smith (WPT)" <jdsmith@microsoft.com>
CC: "public-hme-editors@w3.org" <public-hme-editors@w3.org>, "Philippe Le Hegaret (plh@w3.org)" <plh@w3.org>
Message-ID: <CY4PR03MB272820EF0C1D35F64D7290EFEAAA0@CY4PR03MB2728.namprd03.prod.outlook.com>

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

Received on Thursday, 27 October 2016 00:45:37 UTC