W3C home > Mailing lists > Public > public-html@w3.org > April 2012

[Bug 16748] New: Clarification of the "Process key" step, as well as xmlhttp.response handling.

From: <bugzilla@jessica.w3.org>
Date: Mon, 16 Apr 2012 14:58:23 +0000
To: public-html@w3.org
Message-ID: <bug-16748-2495@http.www.w3.org/Bugs/Public/>

           Summary: Clarification of the "Process key" step, as well as
                    xmlhttp.response handling.
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P3
         Component: Encrypted Media Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: Pat_Ladd2@cable.comcast.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

It is clear why the proposal does not specify key and license transferal
formats, but some informative text could avoid confusion.  For instance, if
HTTPS is used and a key is encrypted using some other system then double
encryption is taking place and that isn’t obvious in the proposal.  Suggest
adding informative text in the following places:
1.      In the addkey sequence, step 5.4.1, change “Process key” to something
like “Process key, may involve handler (CDM) specific decryption”.
2.      At appropriate places in the Javascript examples add a comment
indicating the xmlhttp.response may be encrypted in a CDM specific manner.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 18 April 2012 10:37:54 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:22 UTC