12:50:56 RRSAgent has joined #webtv 12:50:56 logging to http://www.w3.org/2016/03/30-webtv-irc 12:52:03 Meeting: Web and TV IG: Cloud Browser TF call 12:52:34 Chair: Alexandra 12:53:55 rrsagent, draft minutes 12:53:55 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html yosuke 12:54:02 rrsagent, make logs public 12:54:13 rrsagent, make minutes 12:54:13 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html yosuke 12:58:39 colin has joined #webtv 13:00:35 NiloMitra has joined #webtv 13:01:04 alexandra_mikityuk has joined #webtv 13:01:12 hi there 13:01:13 agenda ? 13:02:30 zakim, who is here? 13:02:30 Present: (no one) 13:02:32 On IRC I see alexandra_mikityuk, NiloMitra, colin, RRSAgent, Zakim, yosuke, kaz, Karen, tobie, timeless, sangwhan, trackbot 13:02:42 Present+ Yosuke 13:02:49 present+ Alexandra 13:02:53 topic: introdiction 13:03:02 present+ Kaz 13:03:09 present+ Colin 13:03:14 present+ Nilo 13:03:21 present+ Bill 13:03:28 zakim, who is here? 13:03:28 Present: Yosuke, Alexandra, Kaz, Colin, Nilo, Bill 13:03:30 On IRC I see alexandra_mikityuk, NiloMitra, colin, RRSAgent, Zakim, yosuke, kaz, Karen, tobie, timeless, sangwhan, trackbot 13:04:10 rrsagent, draft minutes 13:04:10 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html yosuke 13:07:40 Alex: Hi everybody! 13:08:10 ... Now we got back to an stable time slot after the DST change 13:08:35 i/Hi everybody!/scribenick: yosuke/ 13:08:38 topic: introduction/ orga 13:08:51 i/Hi everybody!/Scribe: Yosuke/ 13:09:02 ... I wanted to talk about the introduction 13:09:04 rrsagent, make log public 13:09:08 rrsagent, draft minutes 13:09:08 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:09:12 ... And have a question to Yosuke and Kaz about NAB 13:09:28 ... Because I think it's a good time to have a meeting. 13:09:35 Bill_Rose has joined #webtv 13:09:58 ... June or July might be better 13:10:53 ... But if we can keep in tough with each other 13:11:09 ... at W3C booth or something at NABSHOW 13:11:23 Kaz: We need to check BuzDev and Comm team. 13:11:26 ALex: okay. 13:11:29 s/tough/touch 13:11:51 ... It might be good to have an f2f a couple of months later. 13:12:10 q? 13:12:13 q+ 13:12:15 Alex: We are gonna start requirement phase from July 13:12:21 ... That might be a good time. 13:12:35 Kaz: Do you have any image about the venue? 13:13:00 ... The W3C/Keio will have its 20th anniversary event 13:13:27 ... June @@@, we should avoid the date 13:13:54 ... The dates around it sounds good to me. 13:14:10 s/@@@/9th/ 13:14:19 Alex: My initial idea was holding it in Europe or Korea 13:14:33 s/the date/the date unless we want to have our meeting in Makuhari :)/ 13:14:37 ... But Japan can be another options. 13:15:09 :) 13:15:14 @person@: One day or half day, it matters because we need to justfy the travel cost. 13:15:43 s/The dates around it sounds good to me/having our meeting in Makuhari around the event might be a good idea/ 13:15:53 s/@person@/Nilo/ 13:15:59 rrsagent, draft minutes 13:15:59 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:16:04 ... One day is not long enought to justify the trip to Japan. 13:16:12 Alex: Make sense 13:16:19 ... I will think about it. 13:16:32 s/another options/another option/ 13:16:34 rrsagent, draft minutes 13:16:34 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:16:40 Alex: We had received an info from Yosukke 13:16:59 ... about the finalization of MSE/EME VA 13:17:03 s/VA/V1/ 13:17:20 s|introduction/ orga|Cloud Browser TF f2f meeting| 13:17:22 ... I spent most of the time to put together 13:17:35 s/check BusDev/check with BusDev/ 13:17:37 rrsagent, draft minutes 13:17:37 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:17:40 ... and write down requirements 13:17:58 ... this is not a formal process of the TF 13:18:19 ... But I think this is good to quickly draft something 13:18:35 ... that can be helpful for the TF work as well. 13:18:46 ... I will finish writing it by the end of the week. 13:19:04 ... Some of them would be easy to implement 13:19:15 ... Others might not. 13:19:28 s/check BuzDev/check with BizDev/ 13:19:33 ... We need to talk to MSE and EME experts on this topic 13:19:48 Present+ Harrison 13:19:50 s|s/check BusDev/check with BusDev/|| 13:19:52 rrsagent, draft minutes 13:19:52 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:20:15 Alex: Harrison, could you talk about your proposal on the ML? 13:20:57 Harrison: Sure. 13:21:15 [Harrison is using screen share on webex.] 13:22:33 ... Per the request from Alex and TF, 13:22:39 ... I created this doc 13:22:51 ... We have single and double streams approach 13:23:10 ... I beliive we need double streams appoach 13:23:50 ... in light of requirements for decode performance, latency, etc 13:24:08 s/... Per the/Harrison: Per the/ 13:24:36 ... @?# service is the key service for success 13:25:06 s/@?#/quality of/ 13:25:31 Most of network burden 13:25:42 ... should be centralized to IDC 13:26:09 i/Per the/[Harrison will send the slides out to the public group list after the call.] 13:26:15 ... Our proposal has two cases: 13:26:18 rrsagent, draft minutes 13:26:18 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:26:58 [Explaining Single Stream approach diagram] 13:28:20 [Explaining Double Stream approach diagram] 13:31:54 q+ 13:32:11 Kaz: My quesiont is 13:32:27 .. What do the colors of boxes in the diagra mean? 13:33:02 Harrison: Red means video from OTT services 13:33:21 ... Blue means anything else including our cloud browser UI. 13:33:54 ... The key feature of this blue player is GoD mode 13:34:06 ... It's great about latency. 13:34:16 q+ 13:34:20 ... Case #1 is better 13:34:29 ... Comcast is doing something like this 13:35:36 Kaz: Fiber connection or broadband connection should be used for the red line 13:35:54 Harrison: Not necessarily. 13:36:18 s/should be/could be/ 13:36:28 ... I'm assuming ordinary lines people use to view Netflix and such. 13:36:44 Alex: Thanks for the presentation 13:36:46 s/red line/red line between the Streaming Server and the Video Player/ 13:36:59 .... Case #2 13:37:16 q- 13:37:20 .... We need to terminate the MSE/EME things 13:37:28 ack k 13:37:28 ... at cloud browser 13:37:51 ... but adaptive-stream-wise 13:37:59 ... we need some adjustment here 13:38:34 s/Fiber connection/Optical fiber connection/ 13:38:41 ... If somebody would not allow parse a manifest 13:38:51 rrsagent, draft minutes 13:38:51 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:39:05 ... could you tell me something about it? 13:39:23 ... I launched a service like mobile YouTube 13:39:45 .... 20@@, Google provided us with Web Service API to enable it. 13:40:00 ... But they had a second thought after a few years. 13:40:26 ... They don't expose such URLs anymore 13:40:37 ... So, it depends on the policy of OTT services 13:40:45 ... Technically, it's easy. 13:41:05 Alex: We might need to use both of these cases 13:41:31 s/20@@/2006/ 13:41:35 ... because they each might ahve a different policy. 13:41:56 s/ahve/have/ 13:42:17 Harrison: Netflix situation is very different 13:42:39 q+ 13:42:43 ... We need to manage the issue case by case. 13:42:55 q? 13:43:10 Kaz: Case #1 13:43:34 ... We need to have some meta manager to hundle the content right for video streaming, right? 13:43:49 Harrison: I think so. 13:44:13 ... The VoD player was controled by OTT servicers 13:44:24 ... They can do anything they want. 13:45:32 ack k 13:45:38 Alex: My homework would be to put these casees to the architecture 13:45:46 ... on the wiki. 13:45:51 s/Case #1/Regarding Case #1/ 13:45:59 s/hundle/handle/ 13:46:49 ... I also put other points about MSE/EME together. 13:47:42 q? 13:48:11 Harrison: Any questions by emails are welcome. 13:48:27 q+ 13:48:51 i/We had received an info/topic: Cloud Browser Architecture/ 13:48:51 rrsagent, draft minutes 13:48:51 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html kaz 13:48:59 q? 13:50:31 ack y 13:50:38 q_ 13:50:44 s/q_// 13:50:45 q+ 13:51:37 ack k 13:53:07 yosuke: expresses some concerns about our putting EME/MSE within the Architecture discussion 13:53:30 q? 13:53:30 kaz: asks if it would be useful to add some note on the Architecture wiki at: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture 13:57:57 Yosuke: We need some explanation 13:58:07 ... about our choice of streaming tech 13:58:20 ... because we are still on early stages 13:58:34 ... to choose MSE and EME 13:58:55 ... as Harrison put into the diagram 13:59:22 kaz: in that case, it would be helpful if Harrison could add some explanation why he included MSE/EME in his slides (e.g., their cloud browsing module already handles MSE/EME) when he sends his slides to the group. Is that OK by you, Harrison? 13:59:30 Harrison: ok 14:00:08 Alex: I'll do my action item for the architecture. 14:00:49 ... I've done through the agenda item. 14:00:59 ... If you come to NABSHOW 14:01:08 ... please send me an email. 14:01:16 ... Let's talk about CB 14:01:21 q? 14:01:30 ... This is not an official f2f meeting 14:01:40 Alex: AOB 14:01:47 [Nothing] 14:02:11 [adjourned] 14:02:25 Thank you for scribing! 14:02:55 I have made the request to generate http://www.w3.org/2016/03/30-webtv-minutes.html yosuke 16:00:27 kaz has joined #webtv 16:11:47 Zakim has left #webtv