[Bug 27111] New: Separate "persistent" session type into persistent license and presistent key release

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27111

            Bug ID: 27111
           Summary: Separate "persistent" session type into persistent
                    license and presistent key release
           Product: HTML WG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Encrypted Media Extensions
          Assignee: adrianba@microsoft.com
          Reporter: ddorwin@google.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org,
                    watsonm@netflix.com

The "persistent" session type was added to differentiate the more complex
management of persistent sessions (and the application responsibilities that go
with it) from the simpler temporary session model and to provide the CDM with
an indication of the type of license request to generate.

However, this has led to some confusion between persistent sessions and
persistent licenses and to spec text that isn't as crisp as desired. Also, CDM
implementations do not know whether or not to generate a request for a
persistent license.

"persistent" was also general enough to cover any persistence needs without
modifying the spec, but any such uses should probably be explicitly specified
anyway.

I propose splitting "persistent" into "persistentlicense" and
"persistentkeyrelease". This will allow us to provide more specific
instructions to the CDM, clean up the spec text, hopefully eliminate related
confusion, and normatively specify more behavior (especially related to key
release, which has been unclear to some).

There are about six algorithms that need to be updated. I would also define the
term "persistable license type" for use where appropriate (instead of using
'"persistentlicense" or "persistentkeyrelease"').

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 20 October 2014 19:03:45 UTC