15:00:45 RRSAgent has joined #html-media 15:00:45 logging to http://www.w3.org/2015/09/22-html-media-irc 15:00:47 RRSAgent, make logs public 15:00:47 Zakim has joined #html-media 15:00:49 Zakim, this will be 63342 15:00:49 I do not see a conference matching that name scheduled within the next hour, trackbot 15:00:50 Meeting: HTML Media Task Force Teleconference 15:00:50 Date: 22 September 2015 15:01:14 BobLund has joined #html-media 15:01:40 agenda+ Discussion on ISSUE-85 with TAG members 15:01:53 jdsmith has joined #html-media 15:01:58 agenda+ Media Task Force F2F meeting 15:02:09 agenda+ MSE and EME heartbeat publications 15:02:17 agenda+ ISSUE-41, ISSUE-52 and ISSUE-53 15:02:22 Present+ Plh 15:02:26 Present+ MarkWatson 15:02:27 present+ markw 15:02:30 davide has joined #html-media 15:02:31 present+ jdsmith 15:02:42 present+ davide 15:04:09 present+ ddorwin 15:06:10 Present+ BobLund 15:06:25 Present+ AlexRussell 15:07:03 Present+ TravisLeithead 15:07:11 slightlyoff has joined #html-media 15:07:22 I only have 30-ish minutes 15:08:13 Agenda: https://lists.w3.org/Archives/Public/public-html-media/2015Sep/0021.html 15:08:40 Travis has joined #html-media 15:09:11 First topic: https://github.com/w3c/encrypted-media/issues/85 15:09:25 zakim, move to next agendum 15:09:25 agendum 1. "Discussion on ISSUE-85 with TAG members" taken up [from plh] 15:09:54 davide has briefed TAG last week on topic. 15:10:12 not me jdsmith 15:10:22 s/davide/ddorwin/ 15:11:12 markw: Don't believe this is an architectural issue, but implementation options. Takes place entirely within the UA. 15:11:27 is this something that's going to be an interop hazard? 15:11:40 markw: Can understand some browsers may not want to implement, and it's optional for that reason. 15:12:09 Travis: The choice to do some extra cleanup outside the browser session seems strange to TAG. 15:12:16 Travis: 15:13:26 markw: It's understood that there will be cases where messages are lost. Experience has shown with current implementations that it can be reliable enough. 15:14:07 markw: Closed systems like TVs can write as they go and there's no issue with writing data as they go. 15:15:55 markw: On PCs, some implementations may not be able to sufficiently protect stored data and for them writing data on session close may be more appropriate. 15:16:17 I'd like to understand what % of failure is being experienced and is seen as acceptable 15:16:40 ddorwin: Two options: Have secure storage, can write periodically. If not, write the data at the end of session. 15:17:35 slightlyoff: Would like to know more about what level of robustness is secure enough? 15:18:48 markw: Robustness is distinct from frequency of success. If you have protections against alteration, but not rollback, then write as you go isn't robust enough. 15:19:33 Travis: Is there a way the user agent can regularly ping the server to report that playback is ongoing? 15:19:51 markw: That's been a topic of discussion, and license renewal is one way to implement that. 15:20:33 markw: Have for a long time had a goal that playback will continue with loss of server connectivity. 15:20:59 markw: Secure release is designed to do that. 15:21:47 Travis: I was asking about a heartbeat that would indicate ongoing playback, but would still work with loss of connectivity. 15:21:59 markw: Use those now. 15:24:30 slightlyoff It seems that ping suppression could be detected, if it was commonly detected from specific accounts. 15:25:12 markw: We don't believe that pattern would be significantly different from normal users playing content for short duration. 15:26:02 slightlyoff: What's the enforcement mechanism you would use on accounts that show mis-use? 15:27:08 q+ 15:27:38 Travis: I'd like to ask about client robustness requirements again. 15:28:17 Travis: Secure tamper proof storage for keys seems necessary in some scenarios. 15:28:21 q? 15:29:03 I was dropped 15:29:05 dialing back in 15:29:11 markw: We don't have offline scenarios that might require this. Robustness requirements depend greatly on the features provided by the particular DRM. 15:29:50 q+ to answer offline question 15:30:05 markw: If licenses are stored, then it needs to be protected. 15:30:35 I have to go, but I'd like to understand why this feature would be "optional"? 15:30:53 markw: Rollback protection could be important for limited duration licenses. 15:31:02 ack Bob 15:31:14 thanks BobLund 15:31:28 ack dd 15:31:28 ddorwin, you wanted to answer offline question 15:31:29 BobLund: There are cable companies that also want this features. 15:32:06 slightlyoff: This feature was mentioned earlier as optional. Why would it be optional? 15:32:18 thanks markw 15:32:37 markw: There are some members that believe implementation is difficult. 15:34:02 markw: Circumstances would determine what we might do in response, and license renewal would perhaps be considered. 15:34:55 joesteele has joined #html-media 15:35:07 ddorwin: There is an offline option that requires key and state storage. Secure release also requires secure storarge that should be tamperproof or tamper evident. 15:35:50 plh: If the feature is optional, you might consider other means. Are these other means inadequate? 15:36:08 markw: There are no other means that we feel are sufficient. 15:37:02 markw: There are insecure alternatives (e.g. page JS reporting activity). What we are interested in here is having a solution that brings some of the robustness from the DRM component to the problem. 15:37:57 Travis: It sounds like you want secure release to be spec'd and available on implementations somewhere. 15:38:12 Travis: I'm a little dubious of optional features based on past descriptions. 15:38:18 q+ 15:39:19 ack jds 15:39:24 jdsmith: Would prefer not optional, but we've not resolved implementation issues. 15:39:47 Travis: Is the ask of TAG to make architectural decision on the secure release feature? 15:40:04 ddorwin: Yes. 15:40:43 Travis: If the spec requires data storage on shutdown, that would be a stretch. That may not be decisive here, since there are options for implementation. 15:42:20 markw: If writing data on session close is an issue, we should probably spend some more time discussing it. Clearly code is executed when browsers are closed today, and it's not clear how this is different. 15:43:06 Travis: Some native app models have no guarantees about shutdown, and are required to incrementally save state. It is correct that some app models run code on shutdown. 15:44:27 zakim, move to next agendum 15:44:27 agendum 2. "Media Task Force F2F meeting" taken up [from plh] 15:46:43 q+ 15:46:53 ack Bob 15:47:58 q+ 15:48:07 ack joe 15:49:15 zakim, move to next agendum 15:49:15 agendum 3. "MSE and EME heartbeat publications" taken up [from plh] 15:50:52 +1 15:51:09 jdsmith: Want to confirm that we want to publish on every commit (auto publish). 15:51:10 +1 15:51:13 +1 15:51:41 plh: A PR is ready that will turn this on. 15:51:47 zakim, move to next agendum 15:51:47 agendum 4. "ISSUE-41, ISSUE-52 and ISSUE-53" taken up [from plh] 15:51:51 jdsmith: I will approve it today. 15:52:33 https://github.com/w3c/encrypted-media/pull/88 15:52:39 https://github.com/w3c/encrypted-media/pull/92 15:53:28 jdsmith: I'd like to review these today. 15:53:40 zakim, move to next agendum 15:53:40 I do not see any more non-closed or non-skipped agenda items, plh 15:53:54 Topic: Recent EME issues with outstanding pull requests 15:53:56 plh: ddorwin, if you don't hear from jdsmith today, consider it approved. 15:54:01 https://github.com/w3c/encrypted-media/pull/87 15:54:41 Topic: Issue-63 15:54:49 https://github.com/w3c/encrypted-media/pull/66 15:56:21 Topic: ISSUE-17 - Replace "fire a simple event" with "fire an event" for non-simple Events 15:57:26 https://github.com/w3c/encrypted-media/issues/17 15:57:35 Looks good to me 15:58:06 Topic: ISSUE-71 - Be explicit about aborting steps when resolving a promise early 15:58:07 jdsmith: I'll proceed with implementation. 15:58:43 https://github.com/w3c/encrypted-media/issues/71#issuecomment-136507577 16:00:20 rrsagent, generate minutes 16:00:20 I have made the request to generate http://www.w3.org/2015/09/22-html-media-minutes.html joesteele 16:01:13 davide has left #html-media 16:01:15 present : joesteele 16:01:25 rrsagent, generate minutes 16:01:25 I have made the request to generate http://www.w3.org/2015/09/22-html-media-minutes.html joesteele 16:02:33 present: BobLund jdsmith davide ddorwin mawatson jdsmith plh 16:02:39 rrsagent, generate minutes 16:02:39 I have made the request to generate http://www.w3.org/2015/09/22-html-media-minutes.html joesteele 16:04:11 chair: plh 16:04:54 s/slightlyoff It seems/slightlyoff: It seems/ 16:05:01 rrsagent, generate minutes 16:05:02 I have made the request to generate http://www.w3.org/2015/09/22-html-media-minutes.html joesteele 16:05:37 present: joesteele BobLund jdsmith davide ddorwin markw jdsmith plh slightlyoff cwilso robink Travis adrianba 16:05:43 rrsagent, generate minutes 16:05:43 I have made the request to generate http://www.w3.org/2015/09/22-html-media-minutes.html joesteele 16:08:33 rrsagent, bye 16:08:33 I see no action items