16:01:16 RRSAgent has joined #webtv 16:01:16 logging to http://www.w3.org/2012/01/12-webtv-irc 16:01:19 R_Berkoff has joined #webtv 16:01:29 zakim, call kazuyuki-617 16:01:39 Zakim has joined #webtv 16:01:44 zakim, call kazuyuki-617 16:02:03 zakim, call kazuyuki-617 16:02:13 sorry, kaz, I don't know what conference this is 16:02:16 zakim, this will be webtv 16:02:31 sorry, kaz, I don't know what conference this is 16:02:37 zakim, call kazuyuki-617 16:02:39 zakim, this is webtv 16:02:43 ok, kaz, I see UW_WebTVIG()11:00AM already started 16:02:54 zakim, who is on the phone 16:02:55 zakim, who is here? 16:03:07 ok, kaz; the call is being made 16:03:09 +Kazuyuki 16:03:15 glenn, this was already UW_WebTVIG()11:00AM 16:03:17 ok, glenn; that matches UW_WebTVIG()11:00AM 16:03:31 I don't understand 'who is on the phone', Clarke 16:03:31 Zakim, call Mike 16:03:35 On the phone I see +1.408.475.aaaa, +1.765.413.aabb (muted), +1.720.934.aacc, GlennAdams, Kazuyuki 16:03:45 +[Microsoft] 16:03:52 present: john, clarke, kaz 16:03:58 zakim, 934.aacc is me 16:04:03 present+ duncan 16:04:09 present+ russel 16:04:09 ok, Mike5; the call is being made 16:04:11 +Mike 16:04:15 On IRC I see R_Berkoff, RRSAgent, JanL, glenn, duncanr, Clarke, Mike5, kaz, masao, trackbot 16:04:17 zakim, who is here? 16:04:25 present+ mike 16:04:27 +Duncan 16:04:35 sorry, Clarke, I do not recognize a party named '934.aacc' 16:04:43 +Franck? 16:04:53 On the phone I see +1.408.475.aaaa, +1.765.413.aabb, +1.720.934.aacc, GlennAdams, Kazuyuki, [Microsoft], Mike, Duncan, Franck? 16:05:00 present+ bob 16:05:00 +Jan_Lindquist 16:05:02 +??P44 16:05:02 present+ jan 16:05:14 Johnsim has joined #webtv 16:05:17 On IRC I see R_Berkoff, RRSAgent, JanL, glenn, duncanr, Clarke, Mike5, kaz, masao, trackbot 16:06:03 + +1.206.664.aadd 16:06:14 zakim, aadd is jason 16:06:17 present+ jason 16:06:25 +jason; got it 16:06:31 rrsagent, make log public 16:06:39 rrsagent,, draft minutes 16:06:39 I'm logging. I don't understand ', draft minutes', kaz. Try /msg RRSAgent help 16:06:43 franck has joined #webtv 16:06:44 rrsagent, draft minutes 16:06:44 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 16:06:48 jasonlewis has joined #webtv 16:06:53 present+ franck 16:07:23 + +358.405.81aaee 16:07:42 Juhani has joined #webtv 16:07:47 +Mark_Vickers 16:07:52 kaz has joined #webtv 16:07:59 +Johnsim 16:08:07 Las Vegas 16:08:11 Yamini has joined #webtv 16:08:59 Clarke: deadline Jan 14TH need to be escalated in order not to be dropped... any clarification on that? 16:09:35 agenda: http://www.w3.org/2011/webtv/wiki/MPTF/Agenda_Telco_12th_January_2012 16:09:47 i don't believe it means they will be dropped if not escalated; rather, they (bugs) are subject to resolution by the editor 16:09:55 JanL: add discussion on adaptive streaming emails 16:10:44 Kaz: announcement from paul cotton yesterday - talk with Mike Smith - how to deal with comments 16:10:51 Mike will explained details on this call 16:11:18 present+ juhani 16:11:38 Mike5: Paste in a URL 16:11:41 http://dev.w3.org/html5/decision-policy/decision-policy-v2.html 16:11:55 BobLund has joined #webtv 16:11:56 http://dev.w3.org/html5/decision-policy/decision-policy-v2.html#basic 16:11:57 Mike5: current decision policy in the working group 16:12:29 Mike5: two points - the flowchart - step raise bug, editors response, this is how it was envisioned 16:12:46 i/Clarke: deadline/topic: Discuss escalation of bugs to tracker issues/ 16:12:54 mike5: after response - review response and then decide if you are satisfied or not - if satisfied, close the bug - if not, then "escalate" 16:12:55 rrsagent, draft minutes 16:12:55 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 16:13:05 Meeting: MPTF call 16:13:13 mav has joined #webtv 16:13:18 Chair: Clarke 16:13:31 i/Clarke: deadline/scribe: johnsim/ 16:13:36 Mike5: right to take that issue to next level of appeal - in this case, you have different people who are responsible for resolution at diff points in the process 16:13:37 rrsagent, draft minutes 16:13:37 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 16:14:12 bugs in Mozilla, editor of the spec is responsible, --- if you disagree - chairs are the "court of appeals" 16:14:29 s/Mozilla/Bugzilla/ 16:14:30 Mike5: meant to kickin when you have reached a point of disagreement that is otherwise unresolvable 16:14:40 thanyou 16:15:34 Mike5: as part of the timeline that the chair announced, they said if editor had not resolved by 31st, you have an option of escalating them automatically regardless of whether you had received a resolution 16:16:04 Mike5: it is an option, not a requirement. and another thing - no bug is ever dropped - will be resolved regardless 16:16:11 present+ mav 16:16:59 Mike5: remains in the same state that it is in now - waiting for further review by editor - or waiting for the editor to ask questions of bug commenter 16:17:07 zakim, aaee is Juhani_Huttunen 16:17:07 +Juhani_Huttunen; got it 16:18:01 mike5: in my assessment, none have reached an point of impass with hixie 16:18:22 present+ Yamini 16:18:26 +Narm_Gadiraju 16:18:34 present+ Narm 16:19:00 narm has joined #webtv 16:19:01 Mike5: Hixie - can be three weeks before he can get around to commenting - in some things we have offloaded - but he is working on a lot of stuff 16:19:23 Mike5: do not think it is the case that he has ignored bugs - proceeding naturally or normally - 16:19:46 Mike5: risk of escalating bugs - if you take a bug and ask it into a working group issue, you are asking Hixie to stop working on those bugs 16:20:10 Mike5: suggest that is not the best thing to happen at this particular point in time 16:21:00 Mike5: another thing to keep in mind, what we are trying to do is not necessarily get stuff into the spec, it is to get stuff implemented in browsers - 16:21:33 Mike5: get browser mfg working on the use cases and some indication that they are not completely opposed to implementing a particular proposed feature 16:21:57 Mike5: escalating means additional 2 months process - to getting resolved 16:22:51 Mike5: numerous steps 2-3-4 weeks with time to review - and at a minimum that is 2 months of work from escalating to when you have a chance of getting a decision from the working group 16:22:58 escalating (making a bug a wg issue) is best done only after editor has resolved the bug in a manner not acceptable by the submitter; note that a closed bug may be reopened, so one may go through multiple rounds with the editor before choosing to escalate to issue; 16:23:16 clarke: sonds like you are suggesting not escalating - but consequences - this has been characterized as a deadline 16:23:49 q+ 16:24:07 Mike5: not suggesting what you do... you do still have - if you decide to - to escalate - if you think that will help resolve sooner rather than later 16:24:39 BobLund: question - any bug there is still discussion with editor - bug is still considered open - it will stay and be worked on 16:24:44 Mike5: absolutely 16:24:46 + +1.415.867.aaff 16:25:01 Mike5: using bugzilla as last call counter 16:25:29 Mike5: no comment every submitted in bug tracker ever gets dropped on the floor 16:26:14 zakim, aaff is Mark_Watson 16:26:14 +Mark_Watson; got it 16:26:14 Mike5: all registered bugs (in bugzilla) will eventually be resolved 16:26:26 present+ markW 16:26:32 Mike5: value proposition for escalation, working group - must fix during next last call round - cannot go to CR without these bugs being resolved 16:26:37 q? 16:26:37 q? 16:26:43 ack mav 16:27:08 Mark Vickers: good advise, personally pleased with feedback and handling, don't want to short circuit 16:27:25 January 14th date - make sure we do the things we are supposed to do 16:28:12 Clarke: objective of this group is to get the bugs addressed, and not escalating will perhaps get this done more efficiently 16:28:50 Clarke: we should look at each bug, but for those awaiting response from editor, we should let them follow their natural process and not escalate 16:29:13 q+ to say thanks for having me on and gotta drop off for another call and please contact me by e-mail if you have other specific questions 16:29:18 Clarke: hearing nothing, that is the recomendation - suggest you each look at the bugs and see if that is the case 16:29:39 ack M 16:29:39 Mike, you wanted to say thanks for having me on and gotta drop off for another call and please contact me by e-mail if you have other specific questions 16:29:48 mike@w3.org 16:30:02 Mike5: contact me by email if you have additional questions 16:30:04 -Narm_Gadiraju 16:30:09 -Mike 16:30:23 Clarke: next agenda - updated charter statement 16:30:59 q+ 16:31:10 Any comments or wait until next week when we have a statement to discuss 16:31:19 +narm 16:31:38 q- 16:31:58 http://www.w3.org/2011/webtv/wiki/MPTF/ADR_Minimal_Control_Model_Proposal 16:32:21 JanL: post link on draft we are working on - touch on - see if there is a conclusion 16:32:25 i/http/topic: adaptive streaming/ 16:33:04 mark has joined #webtv 16:33:36 RRSAgent, make minutes 16:33:36 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html Mike5 16:33:52 JanL: first to touch on, feedback from Jason (Disney), question usability from a - not talking - SD HD, not using the minimum bandwidth to control the profile 16:34:09 mav has joined #webtv 16:34:34 Jason: maximum more important than minimum, quality tied to minimum 16:34:52 JanL: go into the quality aspect, the use cases, CP1 sets a specific target 16:34:57 CT1 16:35:14 CT2, we are not talking about bandwidth, we are talking about reprsentation 16:35:23 s/CP1/CT1/ 16:35:46 JanL: higher lower quality should be addressing CT2 16:36:39 q+ 16:36:54 ack Clarke 16:37:05 Clarke: i think - you point Jan - in case of max bandwidth, obvious the appropriate response is to send less data 16:37:28 Clarke: in case of minimum, we need to be more specific in suggested response 16:37:42 Clarke: what is the expected action? 16:38:19 JanL: I am not clear - and touches on another area - diff application - maximum and minimum i expect my application to use - which is another issue 16:39:03 BobLund: so in response, Clarke, it is adaptive bitrate, it is the user agent decision, so the answer is you exceed the maximum, signal to the user agent to only select from a lower bitrate 16:39:11 Even if resources sugest higher 16:39:39 s/sugest/suggest/ 16:39:44 if we specify a min, resource has no recourse except to treat as a network error - max makes sense to me, min not so much 16:39:53 Mark Watson: happy for minimum to be removed 16:39:58 s/Even if/... Even if/ 16:40:09 s/if we specify/... if we specify/ 16:40:30 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 16:41:03 s/Mark Watson:/Mark_Watson:/ 16:41:14 JanL: haven't identified who in the task force "i need it, and for this purpose" --- no one has pointed to a "i need it for this purpose" 16:41:34 Clarke: give people a week, and if no one responses by then, we drop it 16:41:43 Clarke: do this from the minutes 16:42:13 JanL: CT1 requirement states overall bandwidth usage - what does that mean? adaptive only or whole browser? 16:42:32 JanL: my impression we were speaking only of adaptive streaming, so suggest reword to clarify 16:42:52 JanL: architecture for overall bandwidth managemetn is much more complex 16:43:07 s/managemetn/management/ 16:43:12 Jason: i agree, and focus on version 1, a "hint" of what the maximum should be 16:43:39 JanL: TCP/IP socket, clear means of managing the socket 16:44:02 Jason: is intent to limit the bandwidth to that cap, or suggest which bandwidth it should be picking 16:44:04 ? 16:44:17 s/picking/picking?/ 16:44:29 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 16:44:52 s/?// 16:44:55 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 16:45:07 Jason: does it need to be more explicit - to describe - to be clear it is either the set of bitrates or the bandwidth of the tcp connection? 16:45:35 Clarke: more the level, a hint to the user agent on the bandwidth - between you and Jan propose some language 16:45:57 JanL: suggestion limit adaptive bitrate streaming bandwidth 16:46:16 Jason: rephrase in the control parameters - 16:46:24 JanL: you do this? 16:46:27 Jason: okay 16:47:02 JanL: one more 16:47:25 JanL: puzzled with CT2 - want a means of selecting only HD level, but don't see control parameters fo rthat use case 16:47:57 s/fo rthat/for that/ 16:48:04 JanL: remove CT2 or add controls - old discussion - but to have this use case, we need to specify the control parameter 16:48:12 Clarke: touches on your first point 16:48:53 Clarke: 1) parameter that allows us to specify that and then the response wouldbe what bob suggested, if you can meet this, return error message "i can't maintain level you required" 16:49:44 JanL: HD level, HLS, MPEG DASH, there is a reprsentation for HD, not bandwidth, it is a representation, convey to UA an HD level quality 16:50:06 Clarke: do we believe in the requirements, CT2 - people support,and then how do we convey that requirement 16:50:19 JanL: I vote leave it (CT2) and we address it 16:50:41 Jason: HD Level is combination of bitrate and resolution - 16:51:17 Jason: trying to capture HD as a bandwidth thing does not directly correlate - bitrate quality and resolution quality give you the "HD Feel" 16:51:33 s/support,and/support, and/ 16:52:23 JanL: HD for me is a representation, not a matrix of bandwidth - i understand different resolution, different factors, but a means of conveying to the UA I want an HD representation 16:53:34 JanL: we have resprseentation changes call back - we have errors with manifest not being able to parse - all i am missing is how the represenation is being selected 16:53:55 s/respreseentation/representation/ 16:54:41 s/represenation/representation/ 16:54:47 JanL: Hugh, you are questioning CT2 16:55:14 Hugh: that kind of control to the web page, language independent of the manifest 16:55:43 or if under the covers by the UA, giving the user control, something the UA should be responsible for - two approaches to handle CT2 in model 1 16:55:52 JanL: what is the second model, 16:56:06 Hugh: language for constraint to be expressed independent of manifest 16:56:35 Hugh (?): user agent that knows what is available, so should give the user what is available - 16:57:14 janl: list from UA representations in their own language, and then i can set - maximum quality using this representation 16:57:32 Hugh: manifest independent language for quality levels 16:57:57 Hugh: UA exposes in a non-browser/adaptive streaming specific manner 16:58:28 s/Hugh/Mark Watson/ 16:58:37 s/Hugh/Mark_Watson/g 16:58:38 q? 16:58:48 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 16:59:52 Mark: haven't investigating media queries - different choices in source elements 17:00:21 is this the media querias? 17:00:25 http://www.w3.org/TR/css3-mediaqueries/ 17:00:51 s/Mark Watson:/Mark_Watson:/ 17:00:57 Bob Lund: expressing preferences - not media queries - constraints to the UA - independent of each other - i think 17:01:20 Clarke: we can continue this on the reflector and have it as an item for the agenda next week 17:01:26 -GlennAdams 17:01:35 JanL: buffer size question - but defer to thenext phone conference 17:01:35 glenn has left #webtv 17:01:37 -??P44 17:01:44 -jason 17:01:48 -Jan_Lindquist 17:01:49 -Mark_Vickers 17:01:49 -Mark_Watson 17:01:50 -Duncan 17:01:51 -Juhani_Huttunen 17:01:52 Mike5 has left #webtv 17:01:53 - +1.765.413.aabb 17:01:55 - +1.720.934.aacc 17:01:56 - +1.408.475.aaaa 17:01:57 -[Microsoft] 17:01:57 -narm 17:01:59 duncanr has left #webtv 17:01:59 -Kazuyuki 17:02:08 Thanks for scribing, John 17:02:35 s/Bob Lund:/Bob_Lund:/ 17:02:42 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 17:03:48 -Franck? 17:03:49 UW_WebTVIG()11:00AM has ended 17:03:51 Attendees were +1.408.475.aaaa, +1.765.413.aabb, +1.720.934.aacc, GlennAdams, Kazuyuki, [Microsoft], Mike, Duncan, Franck?, Jan_Lindquist, +1.206.664.aadd, jason, +358.405.81aaee, 17:03:54 ... Mark_Vickers, Juhani_Huttunen, Narm_Gadiraju, +1.415.867.aaff, Mark_Watson, narm 17:12:52 Present: Russell_Berkoff, Clarke_Stevens, Bob_Lund, Glenn_Adams, Kaz_Ashimura, John_simmons, Mike_Smith, Duncan_Rowden, Franck_Denoual, Jan_Lindquist, Yamini_Nimmagadda, Jason_Lewis, Juhani_Huttunen, Mark_Vickers, Narm_Gadiraju, Mark_Watson 17:12:55 I have made the request to generate http://www.w3.org/2012/01/12-webtv-minutes.html kaz 17:55:48 mav has joined #webtv 18:20:40 mav has joined #webtv 19:33:34 Zakim has left #webtv