Session ID is currently optional in all cases. Should we require it to always be implemented? The main advantage is more consistency for applications, and it seems pretty easy to implement something (i.e. incrementing counter). Are there reasons that a user agent/CDM would not want to implement an ID?
Bug 16613 proposes representing sessions as objects, which could reduce the number of sessionId parameters and attributes. The ID would likely still need to be exposed somehow, meaning this question would still need to be answered.
Bug 16739 relates to the format of Session ID.
With the object-oriented API (bug 16613), the application does not need to use or pass in a session ID if it does not want use it. The CDM must simply create an ID when the session is created. This seems like a minimal burden on CDM implementors while ensuring consistency in implementations.
Agreed. We will make session ID be mandatory (for CDMs that don't already support session ID this adds the requirement, say, for an incrementing integer). Assigned to Adrian.
This decision is pending a decision on key release (bug 17199).
My above comment (#3) may have been related to the degree of uniqueness, but as discussed in the July 2nd telecon, we can make session ID mandatory as described in Comments #1 and #2.
Changeset -> https://dvcs.w3.org/hg/html-media/rev/b0f59ea8c850