[encrypted-media] Formally describe the generation of a license request in update() when another message was sent by generateRequest()

ddorwin has just created a new issue for 
https://github.com/w3c/encrypted-media:

== Formally describe the generation of a license request in update() 
when another message was sent by generateRequest() ==
The `generateRequest()` algorithm allows an implementation to send a 
message that is not the requested license request. See #31. The two 
concrete use cases are a) a request for a server certificate and b) 
`individualization-request` messages. In both cases, the actual 
license request will be generated in `update()`.

The resolution of #31 is to allow this and normatively require the 
request generation in `update()`. However, we did not address this in 
the algorithms. This issue tracks completion of the remaining work 
described in #31.

>From 
https://github.com/w3c/encrypted-media/issues/31#issuecomment-219592027:
>While the current #190 allows the second type, it does not provide 
any mechanism for later generating a `"license-request"` message based
 on the provided `initData` nor solve the larger issue outlined in the
 original comment. To fully address this issue, I believe we need to 
store some type of pending request state and check it in `update()` 
calls. We may also want to extract much of the CDM portion of the 
`generateRequest()` algorithm so it can be called from both places.

Please view or discuss this issue at 
https://github.com/w3c/encrypted-media/issues/207 using your GitHub 
account

Received on Friday, 27 May 2016 22:14:45 UTC